I have made a mind map that makes the Scrum Guide a little more visual for those of us who's brains navigate space better than letters: Click here for a full screen version This is a derivative work by Dennis Mansell based on The Scrum Guide. No endorsement is made by either Jeff Sutherland, Ken Schwaber, or any of their related commercial entities. The original Scrum Guide is offered for license under the Attribution Share-Alike license of Creative Commons, accessible at http://creativecommons.org/licenses/by-sa/4.0/legalcode and also described in summary form at http://creativecommons.org/licenses/by-sa/4.0/ . By utilizing this you acknowledge and agree that you have read and agree to be bound by the terms of the Attribution ShareAlike license of Creative Commons.
Popular posts from this blog
After a day's sailing, we've dropped anchor, cleaned the boat and poured ourselves a drink. “So - what is it you do again?” “I’m a Scrum Master. It’s like the Master of Sail on tall ships.” “What - like the second-in-command?” “No, I don’t have a position in the hierarchy. I just make sure the boat and crew are fit for purpose and help the sailors and staff understand what is going on.” “Why would an organisation need that?” “Many organisations approach products as if it were an industrial process like transport. They load the cargo containers as full as they can get - calling it ‘scope’, then they plan very exactly how to drive from A to B to predict the costs and how long it will take to deliver. “For my clients, their product doesn’t actually match this industrial process very well. I get them to think of it as if they were explorers trying to reach some distant shore. “They should pack very light and get great at teamwork so that they can travel
The second instalment of why Scrum, why Agile? What to say to a CEO... “What do you want?” “I have an idea that could be valuable to the company.” “You have 60 seconds” “We have a lot of people working on the product, but [enter employee survey here] shows that they are unhappy. They are also very clever, yet [some percentage of projects - usually ½ to ⅔] of our projects are failing - costing us a lot of money and frustration. Moreover [some big competitor] are moving faster than we are. Many of our people don't know who they create value for or why. “This is caused by our big plans and need to control the process. “We could take a small, self-organizing team, with all the necessary skills and permissions, and start releasing customer value early and often. It’s called Scrum - I’ve seen it work at a start-up but it also saved [some competitor] from going under.” “What’s in it for us? Sounds like we would lose control” “Scrum would at least show up