February 2012
M T W T F S S
« Jan    
 12345
6789101112
13141516171819
20212223242526
272829  

Does a smaller size of Sprint mean more overhead ?




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 [...]



Problem – When stakeholders disrupt the prioritized feature list of items for a Scrum team




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 [...]



How to define tasks for a User Story without spending a fair amount of time on these ?




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 [...]



Scrum – Having to make crucial product decisions, and yet not aware of the overall design of the product




This is a Scrum story that does not have any easy solutions, and yet we faced these many times. It could be because our working of the Scrum process was imperfect, or could be because of the way that the relationships between the Scrum team and the Product Owner were setup. So, if any of [...]