Scrum Methodology
Learn the Scrum Methodology
The Scrum methodology of agile software development marks a dramatic departure from waterfall management. In fact, Scrum and other agile processes were inspired by its shortcomings. The Scrum methodology emphasizes communication and collaboration, functioning software, and the flexibility to adapt to emerging business realities — all attributes that suffer in the rigidly ordered waterfall paradigm.
5th
SEP
Scrum Backlog Grooming
Posted by admin under Scrum Basics
Backlog grooming (also called maintenance) is not a formal component of the Scrum process, Ken Schwaber, who founded Scrum, advises teams to dedicate five percent of every sprint to this activity. (As with Scrum’s other meetings, the grooming should take place at the same time and place and for the same duration each sprint.)
Everyone attends the backlog grooming meeting: the team, the Product Owner, and the ScrumMaster. During the maintenance meeting, everyone helps prepare the scrum backlog for the sprint planning meeting. This usually includes adding new stories and epics, extracting stories from existing epics, and estimating effort for existing stories. Why is this helpful? Because a groomed backlog will help streamline sprint planning meetings; otherwise, they can stretch on for hours. When product backlog items contain clearly defined acceptance criteria and are estimated by the appropriate team members, the planning process does not have to be tense or overly long. By dedicating a time to backlog maintenance, the team ensures that this preliminary planning always occurs prior to the sprint planning meeting.
posted by: scrum methodology
Comments Feed Reader's Comments
Leave a Reply
Newsletter Sign Up:
Recent Posts
- Can CSMs and PMPs Get Along?
- Orlando Scrum Gathering in March 2010
- Free Scrum Webinars
- ScrumMaster as Impediment
- Advice for Agile Adoption
- Share Your Story
- Free Agile Resources
- Advice for Extending the Sprint
- Danube’s New Scrum Video Blogs
- What Happens at Scrum Training?
- The CSM Exam Saga Continues…
- The CSM Exam
- Back to Scrum Basics: Product Backlog Items vs. Tasks
- Value Versus Velocity
- Scrum and the Enterprise
Categories
- Agile and Scrum (16)
- Scrum Basics (31)
- Scrum Discussion (20)
- Scrum Transitions (8)
- Uncategorized (5)
Archives
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
Blogroll
- Agile Methodology
- Agile Programming
- Agile Project Management
- Eric Brown
- Free Project Management Software
- IT Today
- PM Student
Danube on Twitter
- Overheard from a Twitter post by @easyproject
- Overheard from a Twitter post by @atelierfusion
- Overheard from a Twitter post by @dustincurrie
- Overheard from a Twitter post by @nanderoo
- Overheard from a Twitter post by @FOSSwiki
- Overheard from a Twitter post by @guyma
- Overheard from a Twitter post by @FOSSwiki
- Overheard from a Twitter post by @Ewok_BBQ
- Overheard from a Twitter post by @Ewok_BBQ
- Overheard from a Twitter post by @agileshout






























Excellent post and slice of information!
[...] “Ready” state. I really like this idea – this needs to be done as an integral part of the “backlog grooming”. - A team of average developers performs better than one with Prima Donna developers (or a [...]