Click on a thumbnail to go to Google Books.
Loading... Scrum: The Art of Doing Twice the Work in Half the Time (edition 2014)by Jeff Sutherland (Author), J.J. Sutherland (Author)Read after "Team of Teams." This was more 'how to.' Bonus: education application which led me to these websites: http://eduscrum.nl/en/ http://www.agileineducation.org/ http://www.agileclassrooms.com/ and this link to a detailed guide: Purpose of the eduScrum Guide eduscrum.nl/file/CKFiles/The_eduScrum_Guide_EN_December_2013_1.0.pdf The eduScrum Guide. “The rules of the Game”. Developed by the eduScrum team. December 2013. Written by Arno Delhij and Rini van Solingen. Reviewed by ... The Scrum method sounds like a superior way to handle large projects, but it's a hard term to define. It's less 'centralized planning' and more 'in-the-field adaptation.' It does not subscribe to Gantt charts, which is a project scheduling tool. In fact, it suggests doing away with them. Scrum teams tend to be smaller than traditional teams. In short, there's a system here but it's hard to pin down other than to see if it works for you and your team based on how quickly the results are achieved for a given timeframe. And then near the middle of the book the overall tone shifts. What began as an exploration of Scrum and how to implement it devolved into a litany of generic workplace admonishments that no one seriously disagrees with. Things like "don't multitask because you're bad at it" or "don't work long hours just because it's the culture" or "don't be an asshole or tolerate anyone else being one." It's the health equivalent of saying if you're out of shape and overweight, just start exercising more and eating better and you'll see significant improvements. It's advice that conveniently forgets the human part of the equation as to why these processes frequently fail. Always looking for a strategy to increase productivity, I was extremely pleased to get my hands on Jeff Sutherland’s book, Scrum: The Art of Doing Twice the Work in Half the Time. I have already started to apply the concepts into my day to day operations because we tend to work with a lot of projects. This book has also been an invaluable supporting reference as I teach an advanced instructional design class for the University of Wyoming. As part of the class, I introduced them to the Scrum model as an alternative to the traditional ADDIE model typically taught. Read More This is not a Scrum how-to book. Rather, the story of its making and its philosophy. The concepts are highly adaptable to not just software, business, but everyday life as well. He talks of how to increase productivity of teams by improving communication, eliminating waste, and continuous improvement. I especially liked the idea is that team happiness is the greatest predictor of success. I enjoyed the conversational style and the positive, inclusive attitude. There are surely better SCRUM books to buy. The author, CEO of Scrum, Inc. (it's his story, co-authored with his son), is a bit self-congratulatory, and his cheerleading for SCRUM often comes across like he's plugging a miracle weight loss regimen. That said, it did get me excited about some scrummy ideas, and inspire me to try to put some into practice. Scrum pioneer Jeff Sutherland responded to the suggestion his son, J.J. Sutherland did to collaborate on a book on the truly remarkable journey Scrum has taken them on since 1993. The shippable product, Scrum: The Art of Doing Twice the Work in Half the Time is challenging critics and cynics alike. More can be done faster and cheaper. Other than presenting just another text book on Scrum, Sutherland's narrative emphasizes the backgrounds and reasons for assembling what we now know as Scrum. From Toyota Production System, Lean Manufacturing, professors Takeuchi and Nonaka, the first endeavors of Sutherland and co-creator Ken Schwaber to Deming's Plan-Do-Check-Act cycle and the problems with Gannt charts. It's good to know the origins and the initial stages of implementation. Scrum nowadays not only is used for software development. The book highlights great examples of eduScrum at Dutch schools (makes me proud as Dutch reviewer), micro credit enterprises in Uganda, as well as churches (thanks to Jeff's wife Arline) and journalism in the Middle-East (J.J. Sutherland). Scrum is not wishing for a better world, or surrendering to the existing. It's a actionable way to implement change. Change or die. Since humans want to be great, not only pursuit happiness, but be successful, Scrum is provided as efficient way to get things done faster and cheaper than using waterfall, gate-phased approaches, or having specialists working in silos. You'll learn why Japanese cars are built more efficiently than German cars. Sutherland draws from his own 30+ years experience as a West Point-educated fighter pilot, robotics, engineering, and martial arts to contemporary companies like Valve and his own Scrum Inc. From Toyota Prius to wedding planners. And of course, all elements of Scrum are woven into the story line. Too good to be true? Still not convinced? Read first this book, reflect on your current production process and figure out what you're missing. |
Current DiscussionsNonePopular covers
Google Books — Loading... GenresMelvil Decimal System (DDC)658.4Technology Management and auxiliary services Management ExecutiveLC ClassificationRatingAverage:
Is this you?Become a LibraryThing Author. |
And then near the middle of the book the overall tone shifts. What began as an exploration of Scrum and how to implement it devolved into a litany of generic workplace admonishments that no one seriously disagrees with. Things like "don't multitask because you're bad at it" or "don't work long hours just because it's the culture" or "don't be an asshole or tolerate anyone else being one." It's the health equivalent of saying if you're out of shape and overweight, just start exercising more and eating better and you'll see significant improvements. It's advice that conveniently forgets the human part of the equation as to why these processes frequently fail. ( )