I am currently working on a productivity tool for Scrum teams and want to know where you have the average of the stories The number is in a product backlog in a particular time
To clarify just the number, the whole story or stories should not be included, which can be broken in many stories in the future. Apart from this, I am interested in what people are doing, rather than what they are doing.
Unfortunately I do not get out and there is not enough about other laboratories, so what is actually the experience for us is normal.
I think there are a lot of consultants on this site which may be able to see more and more team rooms I have.
Now I know that this is a "piece of wire" type question and two people with two others, but I'm just looking for a yard stick. / P>
There is usually less than twenty for our company's teams.
Regards,
Chris
" Should not include complete stories "
Understand.
"Or the stories that will be broken into many stories in the future."
What? This is due to our half back.
Always 5 and PlusMan; 2 stories in the official backlog, because it can handle the mind of all our product's brain. When we finish something, then attack some others at the end, "Well, we want to see it too."
As an architect, I can predict an additional 5 plus plasman; 2 stories of a more administrative, technical nature
This is the top 9 stories in our backlog.
Plus there are always obscurely defined stories "which can be 'to' in many stories in the future." Interestingly, these numbers appear in 5 and Plasman; 2.
These are 3 or 4 of these, depending on your "many" broken in many stories "rules.
In addition, most of the additional people tell us stories For example, for example, our sales person has 5 plus Plasman; 2 stories which are part of a sales demo that they would like to see. This is not the main functionality, and it is unclear and this can be broken into many stories. '', So I think it's not counting
I think that it matters, BTW. Every story should be tracked and mutated and broken, but impossible to understand "real" can be "broken". This means giving priority to - obscure or large or ill-defined ideas can be tracked in the form of badgelogs unless they get such a low priority that other projects have outstanding balance Received are more important than.
The correct answer is (5 Plsman; 2 stories) and time; number of stakeholders
Comments
Post a Comment