Showing posts with label product backlog. Show all posts
Showing posts with label product backlog. Show all posts

Thursday, November 20, 2008

# 9 Monitoring the product backlog entries Vs User stories



Before any feature is taken up for production, the user story (stories - one feature can have multiple user stories)  should be ready along with the acceptance tests. It is the responsibility of the product owner to ensure this. Elaboration of the product backlog entries into user stories is a continuous process throughout the project (the product backlog is allowed to grow), and it is important to track this. CollabTeam provides this chart to track the total number of features Vs user stories against them. 

The second bar in red colour, indicates the total number of  bugs handled through the product backlog. 

Wednesday, November 12, 2008

# 7 Handling of defects by collabteam

In collabteam, defects are handled through the product backlog. Defects are booked under the product backlog under the category "defects", to be considered during the next sprint.

Tuesday, November 4, 2008

# 2 Product backlog























  • Product backlog is owned by the product owner

  • It is the wish list of the features to be developed

  • During the sprint planning meeting, a subset of the features from the product backlog is taken up for production.

  • Before taken up for production, the product backlog entries are elaborated into user stories

  • A user story contains a narration of the feature to be developed, the accetance test cases for that feature.

  • All clarifications that happens during the feature development are captured as conversations in the product backlog.

  • The product backlog entry and the user story provides sufficient information for the tem members to estimate and develop the features. This replaces the conventional software requirements specification.
Product backlog feature in collabteam

  • CollabTube has the feature to create the product backlog, assign estimates, categorize them into high, medium, low priority.
  • Against every product backlog entry, user stories can be created. User story comprises of a small narration of the feature to be developed, acceptance tests, and conversations ( all the discussions that happen during development regarding the feature).