A brief analysis of the software cost estimation method used in agile development-Agile Estimating 2.0 (Agile Estimating 2.0)

Agile Estimating 2.0 (Agile Estimating 2.0) method is an updated software cost estimation method used in agile development, similar to the most widely used agile estimation method-Planning Poker (Planning Poker) estimation method. It is also based on expert opinions, analogies and decomposition, using Fibonacci series, which can significantly shorten the meeting time compared to planned poker estimates. The Agile Estimation 2.0 method is also a kind of story point estimation method, and its steps are as follows:


  1. The product owner introduces each user story to the team to ensure that all requirements-related issues are resolved before estimation.


  2. The whole team participates in this game together. There is only one simple rule of the game: only one person at a time puts a user story card in a suitable position on the whiteboard: small stories on the left, large ones on the right, and the same size vertically arranged in a row. The entire team moves the user story cards in turns until the entire team agrees with the order of the user story cards on the whiteboard.


  3. The team assigns story points to each user story (column). The simplest way is to use voting to determine which Fibonacci number is assigned to each user story.


  4. Use different colors to distinguish different aspects that affect the estimated size, and reconsider whether you need to modify the estimated value. For example, use red to indicate user stories that cannot be covered by automated test scripts. Therefore, those user stories need a larger number to accommodate the cost of manual regression testing.

Guess you like

Origin blog.51cto.com/15151357/2677450