Geek Answers Handbook

Scrum story rating

We started a project that will be managed using Scrum / XP. We have written an entire portfolio of products for evaluation for evaluation purposes. We make sure that all stories are customer-oriented, and we evaluate them

  • the value of a business story : the MoSCoW method - should, should / should not be implemented.
  • story / complexity (= plot points): 1, 2, 3, 5, 8, 13, 21, 100 - is connected with the complexity of the plot / effort, and not with ideal days lasting

100 story points may have some stories with V / Will not, because they are actually more complex stories that will be broken down later if necessary.

The calculated meaning of the story is based on value and effort, not overlapping the history of MoSCoW.

But without 100 point stories, our stories so far (also broken) have a difficulty between 2 and 8, which, in our opinion, is a suitable story size to avoid micro-control. But some stories have become connected with each other. We have stories that can take more if they are done first, and less if some other story is made before them.

Questions
Can plot points be adjusted later during development, how can we do with story tasks, where can we re-evaluate them, add new ones, delete existing ones, or does this not apply to stories? Due to changes in their complexity, estimates of the end date based on the planned speed will also change. What is the best practice in this case?

+5
4

, . , Sprint Sprint.

, , - Sprint, . . , Sprint, , . , , .

, Velocity , . , 3- 4- , , . , , , , , 20 15 . , , .

, . , . , : " , , , 15% ", .

- Sprint. , , , -. , . , Sprint.

, .

+5

. , . ; .. ). , . , - .

: - 3 - 8 , 2, 12 , .

, , , . , , , . , , (.. " -" " -" ).

!

+2

.

, , 18 . , , 15 . , , , 3 - 0,6 .

. . , , .

8 .

, - ( ). , spring ( 20 ), , , .. 2 .

, ( , ). , - , .

0

, User Stories , INVEST, , , , . : http://www.richardlawrence.info/2009/10/28/patterns-for-splitting-user-stories/ , ; -)

Just remember that separating and maintaining dependencies (which is like creating a critical path in a Gantt chart) will exceed the team’s ability to be creative and negotiate on these stories, and it may also hide “without a value-proposition”.

NTN
ANdreaT

0
source

More articles:


All Articles