Tag: agile

22 April 2013 / Agile & Scrum
Most common mistakes in scrum ceremonies 5/7: the sprint review

Turning it into a status meeting, focusing on time tracking The goal of a sprint review is to show the product owner and the stakeholders what the team developed during the sprint. It is not about listing what each team member did, how much time he/she spend on that and how they got it done. This is not valuable for the stakeholders and pretty frustrating...

15 April 2013 / Agile & Scrum
Most common mistakes in scrum ceremonies 4/7: the daily standup

Losing focus during the ceremony The bigger your team gets, the harder it will be to make sure that everyone listens to the rest of the team, otherwise the whole idea of sharing knowledge and checking whether you can still meet the sprint goal is thrown out the window. In order to avoid everyone talking at the same time and losing focus during this very...

8 April 2013 / Agile & Scrum
Most common mistakes in scrum ceremonies 3/7: the sprint planning

No acceptance criteria listed on user stories This will keep the team from really committing to the sprint backlog. If they have no clear idea on how to demo a user story, how the product owner will decide whether or not a story is really done, the team will have no way to feel confident about the commitment they are making. This will frustrate the...

1 April 2013 / Agile & Scrum
Most common mistakes in scrum ceremonies 2/7: estimating stories

Spending too much effort in estimating stories People have the tendency to spend too much effort on estimating the incoming work. Having some basics skills available, like high/low showdown, deal and slide and planning poker will help the team to make well educated estimates they feel comfortable with. These techniques are also designed to maximize the return on investment of your time when it comes...

25 March 2013 / Agile & Scrum
Most common mistakes in scrum ceremonies 1/7: grooming the backlog

No prioritization Although there is a product backlog that contains almost all the work that can be planned, there is no real prioritization and things get picked up ad hoc, purely based on reactionary prioritization. In most cases this is a symptom of a number of possible underlying diseases. More often than we like to, we see product owners not really equipped for reaching their...

14 December 2012 / Agile & Scrum
Agile planning: the basics explained

There are different ways to build a planning that actually embraces change. The most basic requirements are that this planning is easy to use, fast to change and makes it easy for you to visualize impact of change. It should give you just the necessary amount of information to make decisions about change well founded and fast. Whether you are using story points for your...