Scrum summary. accessible at and also described in summary form at By utilizing this Scrum Guide you acknowledge and agree that you have read and agree to be bound by the terms of the Attribution Share-Alike license of Creative.

Scrum summary

Role overview Agile Coach/ScrumMaster (EN)

Scrum summary. In his latest blog entry, Jeff Sutherland introduces an exceptionally concise overview of the Scrum development process, which may be useful for communicating with management, courtesy of Swedish consulting firm Softhouse.

Scrum summary

Just finished Scrum, The art of doing twice the work in half the time from Jeff Sutherland, co creator of Scrum. Sutherland gives you many anecdotes of his personal experiences as a fighter pilot in Vietnam or as biometrics expert, innovator of ATM technology, problem solver, trainer, investigator or coach and what he has done with that in relation to Scrum or the development of Scrum.

The way the world works is broken gives the success story of applying scrum within the FBI to bring a big project back on track, a project that was using a traditional project life cycle. Blindly following plans is stupid, inspect and adapt, change or die, and fail fast so you can fix early. The origins of Scrum give some insight in the work of two Japanese business professors, Hirotaka Takeuchi and Ikujiro Nonaka. Teams explains the impact of the size of the team, the role of the scrum master, and what does it mean or what do you need to be an excellent team.

Pull the right lever, transcendence, autonomy, cross-functional, small wins and blame is stupid. Have a look at a video from all black rugby team Haka to motivate your team and let the opponent shiver:.

Time is about the sprint and daily stand-up and his experience at Wikispeed. Treat it that way, demo or die, throw away your business cards, everybody knows everything and one meeting a day. Taichi Ohno talked about three different types of waste. Muri , waste through unreasonableness; Mura , waste through inconsistency and Muda , waste through outcomes. Happiness is success, quantify it, make it visible, and use a scrum board, deliver happiness.

What can you implement, what can you sell, what can you be passionate about. You have to focus on all three to be successful. Use a backlog to know what to do when. Chapter nine, the last one: The book gives a lot of background information and will help you to get a much better understanding of the philosophy behind Scrum. As stated it is not a learning book about Scrum, but on the other hand to learn Scrum you have to bring it into practice and practice and practice… So from that perspective this book is a good starting point.

You could learn a lot from them too. If I am correct Google developers gave this as their main root course for the failure of Google glass at least at this moment. Or he mentioned a story where he successfully implemented Scrum at PatientKeeper. When he left, new management decided to stop with Scrum. Could be interesting to know why? I always hear the success stories of organizations building a software product but if you build the product for yourself, e.

Do we have success stories where Scrum is used for those kinds of transformations? What about organizations that have to build or update many applications with have interfaces with each other. They could have many scrum teams, but how are they working together. Spotify using Tribes, Squads, Chapters and Guilds but this is again about developing a product for the end customer and not about embedding the output in an organization.

Scrum, The art of doing twice the work in half the time. Bestellen van de Nederlandse vertaling: Scrum, Tweemaal zoveel doen in de helft van de tijd. Robert, in my blog you can find a few books. Book reviews in Henny Portman's Blog. How to understand the forest of Agile methods, and frameworks?

How can we see the wood for the trees? You are commenting using your WordPress. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email. The book is divided in nine different chapters and each chapter ends with takeaways. The next six chapters highlight a specific aspect of Scrum.

Have a look at a video from all black rugby team Haka to motivate your team and let the opponent shiver: Scrum, The art of doing twice the work in half the time Bestellen van de Nederlandse vertaling: This entry was posted in Uncategorized and tagged Agile , recensie , review , Scrum.

Robert Pragai April 16, at Appreciate any insight, Robert Pragai. Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in: Email required Address never made public. Follow Blog via Email Enter your email address to follow this blog and receive notifications of new posts by email. Join other followers Search for: Create a free website or blog at WordPress. Post was not sent - check your email addresses! Sorry, your blog cannot share posts by email.


1402 1403 1404 1405 1406