We seem to find ourselves running into a fundamental problem during out Sprint planning meetings. Some of it is from our older methods, but partially it also seems to be a problem with the way we are using our Scrum processes. Consider the process before getting into Scrum. We would have a list of features [...]
|
||||||
|
When a team is following Scrum, it means that the team decides the estimates, the number of features that are to be done per cycle (Sprint). The priority of features is as per the Product Owner, and it is the responsibility of the Product Owner to ensure that all the stakeholders are kept in the [...] Scrum has been setup based on some principles that seek to map how modern software projects actually are, with the biggest basic principle being the fact that business requirements keep on changing. Hence, if there is a methodology that requires you to lock all your business requirements at the beginning of the cycle, and makes [...] In the previous post (Scrum team – Difference between Capacity and Velocity), I had talked about some of the reasons as to why the capacity of a scrum team is different from that of its velocity. In this post, I will try to explain how we can bridge this difference. Most teams do not see [...] |
||||||
|
Copyright © 2012 Learn Software Development - All Rights Reserved |
||||||
Recent Comments