5 responses to “Scrum in a 100 words or less”

1. Tobias Mayer 10/01/09 11:22

   

   Interesting how this one differs from Peter’s. Both are good, but this one is more team-centric. I like that. Better if it was also able to identify the two other roles though. Challenging in 100 words!

2. Carlton 10/01/09 11:32

   

   I thought about highlighting the roles by name in the description and then I remembered the confines of the challenge – 100 words or less AND remove the jargon. The terms “Product Owner” and “ScrumMaster” still rely on the usage of jargon, so I eliminated them.

   Also, if the Team is the center of Scrum, do these roles need to be identified? I would say no since in a 100 word or less description of Scrum, I feel the ScrumMaster and Product Owner are just supporting roles. Now, in a 200 hundred word description of Scrum, I would promote them to headlining co-stars, but that was not the challenge.

   Let’s see what someone else can come up with…

3. Francois Bachmann 10/01/16 01:44

   

   Carlton, I like your team-centered version too.

   To me, the part “While there are two roles to help the Team remain concentrated on their objectives” is the one with the lowest information/word-count ratio.

   Maybe Tobias’ challenge “refine the two other roles” can be reformulated: answer the question “why two?”. IMHO, both ensure accountability, one for process, one for committed objectives…

   Anyway, kudos for a very readable 100 word definition!

4. Carlton 10/01/16 07:42

   

   @Francois I like your perspective on accountability because I often explain Scrum is framework for visibility AND accountability.

5. Mohan Arun 11/06/05 20:57

   

   Readers may find this resource useful: Scrum cheat sheet
   http://www.scribd.com/doc/2370861/Scrum-Cheat-Sheet
   My attempt at “Scrum in 100 words or less”
   Scrum uses sprint cycles of up to 30 days for developing or enhancing software. The Product Owner (PO) and the Scrum Master (PO) define and guide the team whose roles are loosely defined and frequently overlap. Scrum Master schedules daily meetings of up to 15 minutes to keep pulse on development progress. Scrum is a form of agile and it uses stories to visualize software features.