Posted on 21, Feb 2012
You know that probably. Requirements are coming, coming and coming. There is no time to stop and think about them. There is no time to organize them. There is no time to analyze your backlog so you know which requirements should be developed as next. Even more, many customers ask you of new functionality or defect fixes. In our [...]
Read morePosted on 28, Dec 2010
Our previous blog posts were about core product ownership approaches how to prioritize backlog according to business value. Another dimension a product owner should know is expected customer satisfaction. Satisfaction with developed feature or story. Mr. Noriaki Kano developed Kano model as valuable technique helping to recognize that. Applying this method the product owner can identify importance of stories [...]
Read morePosted on 20, Dec 2010
Product owner is often confronted with a large backlog. This post continues to explain how to consider priority of stories. See principles in previous post. Measuring risk and positive value allows to calculate the order in which stories should be developed. Very nice and simple visualization can be Risk vs. Value chart. Chart is split into [...]
Read morePosted on
Agile coaches teach teams to develop a business value that is delivered at the end of the sprint. But should be a value an indicator of the priority? Yes, but not the only one. There are many other attributes we often forget to consider. We suggest to apply different approach. We would like to have a [...]
Read morePosted on 28, Sep 2010
In this step product owner and development team will try to plan project sprints. Who Product Owner Scrum Master Planning in SCRUM In Step 4 Planning product releases we defined sprint as time box for developers to complete selected stories. Product Development Product Backlog Release A Release B Sprint 1 Sprint 2 Sprint 3 ScrumDesk: Planning sprints [...]
Read morePosted on
In this step product owner and development team are going to plan project sprints. Who Product Owner Creating stories Target for this step is to create backlog stories. Product Development Product Backlog Stories in scrum are mainly created by product owner. As a first step let’s log in as product owner. Product owner is responsible for requirements specification and prioritization. [...]
Read morePosted on
In this step product owner and development team will plan sprint. Who Product Owner Scrum Master Developers Visitors Sprint planning meeting Development team meats with product owner on sprint planning meeting. Product owner shows the team his plan for first sprint. Product owner chose stories by top importance (priority). Product Development Product Backlog Release A Sprint [...]
Read more