As a part of every project or product development cycle, there will be some items that you feel will take a short period of time, but to get them done is difficult because they are prioritized low. So, whether you are doing a prioritization for the use of Scrum monthly Sprints, or using other development [...]
|
||||||
|
Our team was used to working on short projects, doing projects that had a total duration of between 2 /3 months. For such short projects, we would meet regularly (twice a week or more, depending on how close we were to the release), and would review status at each such meeting. In these meetings, based [...] In the organization where I work, most of the Sprint cycles are 3-4 weeks long. When trying to determine the size of what a Sprint should be, most teams new to Scrum do not have any great planning process on how to determine the size of the Sprint cycle, and decide based on their talking [...] When you start working out some of the basic assumptions of how a Scrum team is supposed to work, one of the base assumptions is that the Product Owner sets the priorities of all the features / User Stories for a Sprint. Now, depending upon business needs, this order can even be changed midway during [...] |
||||||
|
Copyright © 2012 Learn Software Development - All Rights Reserved |
||||||
Recent Comments