It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,875
×12,002
×14
×10

question asked: Feb 18 '16, 5:49 a.m.
question was seen: 3,539 times
last updated: Feb 18 '16, 5:49 a.m.

Related questions

Story points, closing a story and testing

0
Morten Madsen (305●32●50) | asked Feb 18 '16, 5:49 a.m.
 This question is closely related to this question: https://jazz.net/forum/questions/112658/story-points-and-progress-tracking

I agree in the solution, but now I have a question about the "next step".

So, you work with your story, you complete the development and then the story gets "ready for testing", so you put the story in "Ready for test". One dilemma now is, that if your "Ready for test" state is not in "Closed" group, then you won't cash in the story points in the current sprint, because the testing might take some time.

How would you solve this?

We are currently doing as follows:
  1. Decompose a main story to many sub-stories
  2. The developer then directly closes these sub stories when done and thereby cash in on the story points.
  3. When all sub stories are done, the main story (with no story points) is set ready for test
  4. Defects are created against the main story, and remains in "Ready for test" until all defects are solved
  5. If a defect is in fact "missed functionality" a new child story is created instead.
Does this sound..... uhm... sound?

Be the first one to answer this question!

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.