May 5, 2011

Ask the Team!

There are some questions asked by Product Owners and they have a simple answer: “Ask the team!”

There are some questions asked by Product Owners

... and they have a simple answer: “Ask the team!”

Story good enough for the Sprint

When a PO ask: “Is the user story good enough, that it can be taken in the sprint?” or “Does this user story have enough acceptance criteria?”

The answer to this question is “Ask the team!”

The team will work with the story, so the story has to be good enough that the team can work with it. For a story to be good enough for the sprint it has to be small (6 to 10 stories in a sprint are a good volume), it has to be estimable (You don't need an exact estimate, but just enough to built an empirical base for the velocity and a help for the PO to prioritise the product backlog) and it has to be testable (It should be clear what is needed to finish a story and with this you have a high-level understanding of testing if the story is completed). To be sure that a story is good enough for the sprint the team should be involved and you should ask the team.

Use of the Sprint Burn Down by people outside the Team

When a PO ask: “What does the current burn down chart tell me?”

The answer to this question is “Ask the team!”

Possible Scenario of Sprint Burn Down based on Story Points

Possible Scenario of Sprint Burn Down based on Story Points

At first sight you could think this chart looks pretty bad, but maybe there are some stories close to be finished. Maybe the team has really just some last thing to finish two of the bigger stories. The team has already reflected on the situation and agreed that this is not critical and how to proceed. Just one day later the burn down could look much better.

Possible Scenario of Sprint Burn Down based on Ideal Hours

Possible Scenario of Sprint Burn Down based on Ideal Hours

At first sight you could think this chart looks pretty good, but maybe there is no story finished. Maybe the team started to many stories at once and they missed tasks or there is still a high risk for surprises in the open stories. The chart could look like this and no story is really done. Only the team can really interpret the burn down chart. It helps them to have the right discussion at the right time to inspect and adapt to the current situation.

I can’t interpret it alone

As a person not involved I can’t interpret the chart alone. To get the right information I would ask the team.

But there is also the other way around

If there is the question from a team, “Is this Story really Done?”, there is only one answer to be sure, “Ask the PO” ;-) There is always a possibility that you and the PO have different understandings of the story and their acceptance criteria. The PO and the team will learn from one another what they can expect and how to communicate expectations properly, but the best way to avoid such surprises is to ask the PO.

Image of ralfkruse81

Ralf Kruse

I'm an Agile coach. Sometimes I'm excited and sometimes I feel more like Marvin ;-) Follow me @ralfhh
blog comments powered by Disqus
Image of ralfkruse81

Ralf Kruse

I'm an Agile coach. Sometimes I'm excited and sometimes I feel more like Marvin ;-) Follow me @ralfhh

Latest Posts

Leading and Lagging Indicators: What is the right way to measure performance?

How can you measure and track your performance using leading and lagging indicators? 

Image of hwong

Hazel Wong

Marketing Assistant at agile42. Passionate about gaining insights from data in order to create content that resonates with the audience. Eager to help teams and companies open their mindset about the application of agile methods to address their challenges.

Changing organizational culture at Siemens Digital Factory

Siemens DF extended the use of agile methods the right way, through a thorough adoption of the essence and practice of being Agile

Image of kpogorzala

Konrad Pogorzala

Presenting at the Regional Scrum Gathering South Africa 2018

agile42 present at the Regional Scrum Gathering to be held in Durban, South Africa, 8-9 November 2018

Image of joperold

Joanne Perold

Agile Coach in South Africa. Explorer, learner, experiencer, part time philosopher, working with teams and organisations to be more agile.

Scrumtisch December 2018

The Berlin Scrum User Group meets on December 13th at agile42, Gruenberger Str. 54, 10245 Berlin.

Image of aballer

Alexandra Baller

agile42 Team Assistant

Motivation to Get Better

When Turkish real estate site Zingat realized that their Scrum adoption suffered from anti-patterns, they decided it was time to improve

Image of ayse.turunc

Ayşe Turunç

As an Agile coach, I strongly believe in people talent, in collective intelligence and that happy teams are more efficient. I'm looking forward to put my talent to help teams and individuals to work better together and grow.
Image of ebru4984

Ebru Yalçınkaya

I act as a change agent where the teams, domains need to enhance agility to reach their goals, to create a shared vision if needed. I coach every kind of team , every domain, like management teams or like customer care, technology and sales groups.