How Kano model helps to agile product backlog prioritization

Posted 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 more

Is business value enough for scrum backlog prioritization?

Posted on 20, Dec 2010

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 more

Step 4: Planning project releases

Posted on 28, Sep 2010

In this step product owner and development team will try to plan project releases. Who Product Owner Scrum Master Planning in SCRUM SCRUM is based on development in time boxes called Sprint. Sprint is a time needed to complete selected stories (features, bugs, requirements, tasks,…). Length of the sprint is typically 30 days, but it depends on a development strategy and [...]

Read more

Step 5: Planning project sprints

Posted on

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 more

Step 6: Backlog Stories

Posted 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 more

Step 7: Planning Poker®

Posted on

In this step development team is going to estimate stories. Who Scrum Master Developers Planning Poker® Our backlog contains all known stories which has to be developed for product. Team sits down together around the table and they starts to discuss size of each story. Product Development Product Backlog Every developer will get cards with [...]

Read more

Step 8: Sprint planning meeting

Posted 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

Mike Cohn: Agile Estimation

Posted on 23, Sep 2010

(Published with Mike Cohn permission) Part 1: Part 2:

Read more