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
- Results of an Agile Assessment
- Introduction to Scrum Video
- Complexity and cost of change
- Technical Debt – The High Cost of Change
- Strategic Vision and Scrum
- Agile and PPM – Q&A
- Estimating Earned Business Value on Agile Projects
- Building the Product Backlog
- Intro to Agile
- The Agile Manifesto and Twelve Principles
- The Daily Scrum; It’s a Good Habit to Make
- Obstacles to Enterprise Agility
- What is Scrum?
- Can CSMs and PMPs Get Along?
- Free Scrum Webinars
Categories
- Agile and Scrum (27)
- Agile Assessment (1)
- Agile Manifesto (5)
- Agile Principles (7)
- Scrum Basics (43)
- Scrum Discussion (26)
- Scrum Transitions (16)
- Uncategorized (7)
Archives
- January 2012
- December 2011
- November 2011
- October 2011
- November 2010
- September 2010
- June 2010
- April 2010
- March 2010
- February 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 ALM
- 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 @CloudForgeHQ
- Overheard from a Twitter post by @billportelli
- Overheard from a Twitter post by @PDXGoonie
- Overheard from a Twitter post by @PDXGoonie
- Overheard from a Twitter post by @davidp98
- Overheard from a Twitter post by @karishmavivek
- Overheard from a Twitter post by @karishmavivek
- Overheard from a Twitter post by @tshrinivasan
- Overheard from a Twitter post by @tshrinivasan
- Overheard from a Twitter post by @eillenperalta
[...] “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 [...]
[...] una corriente de opinión Scrum que cree necesaria la introducción de una reunión llamada Backlog Grooming. Existe una corriente general que apuesta por este tipo de reuniones. En resumen podemos decir que [...]
[...] (backlog grooming) is the best thing since sliced bread, but how much time should this take. Ken Schwaber, who founded Scrum, advises teams to dedicate five percent of every sprint to this acti…. Michael Cohn has recommended roughly 10% of current sprint time to be dedicated to future sprint [...]