stories in backlog marked as done

[Fleur]

hello telerik people,

We have been starting to use scrum and teampulse at the same time and we are learing a lot about both of them.
We are happy with the Best-practices section, because it helps us to work agile, but we do not understand evey best practice.
I couldnot find information about that in your documentation.
Can you explain to me the following best practice:

"There are stories in the backlog that are marked as done."
In our first sprint we did some stories, and when I look at these stories the stories themselves and the undelying taskst were all marked as done.
it says: "Story X is in the backlog but is done."
What do we need to do to get the story out of the backlog?

regards,

Fleur

[Steve]

Hi Fleur,

In the current release of TeamPulse, an item is considered to be in the backlog if it not assigned to an iteration (or left assigned to the root Project iteration). In Agile development, work happens inside of an iteration, so stories that are done should be done as part of that iteration and assigned to an iteration.

I hope that makes this best practice clearer.

We're revisiting Backlog management as part of next release in August. Please stay tuned for upcoming news on the new features in our next release.

Ta.
Steve
the Telerik team

[Richard]

Hi Steve and salut Fleur !

I am not sure I understand. I am starting to evaluate TeamPulse, today, with the trial version and the test project in the trial version.

 

I have a story, “Add request a vacation functionality”. These story has 3 tasks, all “done”. The story is assigned to “Team vacation project/Iteration 1”. And in the Best practice panel, I have a message saying this story is in the backlog but done (I attached 2 pict).

 

Where is the problem?

 

Thanks

 

Richard

[Kamen Ivanov]

Hi Richard,

In that particular case, the start date of your project is set to a date in the future - 02 November 2011 so each item in the project is supposed to be in your backlog because in the backlog are all items that the team will work on in the future. And the best practice analyzer catches that case when story is with status Done but corresponding to the iteration it belongs to is not started yet (the story is still in the backlog).

The regular flow is that you create stories and they will stay in the backlog for a while. Then when you plan to work on a particular story you will put it in the current iteration and that will automatically remove it from the backlog.

Regards,
Kamen Ivanov
the Telerik team

[Richard]

Ok, thanks a lot :)