In the end, seven teams ended up giving a demo and each one hit it out of the park. So there was actually about 15 hours of work done instead of 24 hours, but for 2 days of work, all I can say is. We started coding at 2:00PM on Thursday, and the coding stopped at 3:00PM on Friday, so it was technically two calendar days, and not many folks actually coded past 10:00PM. It was an incredible success, and the votes are still being tallied. And that makes me happy.Well, the first ever Digital Reasoning ShipIt Day is in the books, and all I can say is that I'm sure there will be more in the future. Also, I know we have a continuing rhythm meeting to crack difficult problems every sixth month. We worked hard from Friday afternoon until we didn’t have any energy left Sunday, but we also made food together, shared stories, played Uno and BezzerWezzer as well as exploring the unfamiliar territory (we rented a cabin in Sweden this time).įor me personally, there’s also other great bonuses of having Ship-It weekends: I’m getting so much energy from being with people I like – meaning I’ll have extra energy a week after, and a bigger enthusiasm and motivation when thinking about work. They’re a lot of fun and strengthen our social connections which in itself has many advantages such as: increasing commitment between us, helping us to self-organize and keeping our safe space safe.They increase knowledge sharing and experience as we’re sharing different perspective on the problem, aspects of the problem as well as experience from similar or totally different situations.Notice that we’re not doing a case we’re solving our problems whether it being our website crashing or us pondering how to crack the code of digital learning. They stimulate creativity and at the same time solving an actual problem.The collective list of effects by having a Ship-It weekend: And so, we did.īut is it really that effectful you ask? Yes. Then the light hit us after our first successful Ship-It weekend: Let’s make a Ship-It weekend about digital learning. And for about 1,5 year (on and off) we would brainstorm what it could be, talking about different concepts, adding it to our strategic backlog, and then removing it again because it seemed impossible. I think, we’ve been talking about creating digital learning (in some form) for a long time. This second Ship-It weekend was planned and luring behind a corner for a long time. If you want the story about our web site and how we used 48 hours on creating a new site, read my reflections in my LinkedIn Post here. It was in fact by accident our Ship-It weekend was thematized fir first time around our website was about to slowly crash, and it was great, because we now had the opportunity to save it. Leaders, Project Managers, Change Agents, and many others can use the concept as well, and they can use it with clear benefits (which I’ll get back to further down). It doesn’t have to be only Developers using concepts like Ship-It. We’ve come to love them, because they’ve shown to be very useful. We have now held two, one in January and now in August, and are already planning the next one. Twice a year, we have our own ship-it weekend, using 48 hours on a problem we wish to get closer to or solve. It’s not only in software ship-it days are useful
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |