Categories

A sample text widget

Etiam pulvinar consectetur dolor sed malesuada. Ut convallis euismod dolor nec pretium. Nunc ut tristique massa.

Nam sodales mi vitae dolor ullamcorper et vulputate enim accumsan. Morbi orci magna, tincidunt vitae molestie nec, molestie at mi. Nulla nulla lorem, suscipit in posuere in, interdum non magna.

Ensuring some time in the current Sprint for planning for the next one

We were having a discussion with a few project managers about one of the biggest problems that we could see in terms of usage of the Scrum model for some of our teams / products, especially the ones that were more complex. And then we realized that the problem was not with the Scrum process […]

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