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.

Scrum: Making the team aware of their Velocity before they start committing for the next Sprint …

A few of the last series of posts talked about the Scrum team running into a situation whereby the actual time required for a feature was much more than the estimate. This was one of the problems that can pose a significant problem to the Scrum team and their productivity. A twist to the same […]

Scrum: Features balloon beyond initial estimates and don’t look like getting done in the current Sprint – Part 3

This is a series of posts that focuses on the problem where in a Sprint, the feature does not match the estimates (and it’s not that the feature gets done before the estimated time). For every Sprint, there are a certain number of tasks that can be done, and these are based on the estimates […]

Scrum: Features balloon beyond initial estimates and don’t look like getting done in the current Sprint – Part 1

This is one of those items that keeps on showing up in discussions that we have within the teams, and with other Scrum Masters (which of course means that their teams also run into these features from time to time). In an ideal world, the Product Owner has described the feature in enough detail in […]

Scrum: Testing getting done by the end of the Sprint / Or not

The question of testing tasks and Scrum is one of the questions that keeps on popping up at regular intervals. Teams that are initiating Scrum as their development process, or those that are running in a situation where there is a lot of focus on development tasks and less so on testing tasks have a […]