Scrum - 5

 

# Scrum Metrics

The following are some key metrics that helps measure the work done by scrum teams and value delivered to customers:

Sprint Goal Success

Team Velocity

Sprint Burndown

Time to Market

ROI

Customer Satisfaction

# Agile Estimation

Agile estimation is ”the process for estimating the effort required to complete a prioritized

task in the product backlog”.

This effort is usually measured with respect to the time it will take to complete that task, which, in turn, leads to accurate sprint planning.

Agile teams also make estimations with reference to story points.

A story point is used in Agile Development project to estimate the difficulty of implementing a

given user story.

Agile Estimation Techniques

Planning Poker

T-Shirt Size

Fibonacci Sequence

Planning Poker#

Number-coded playing cards are used to estimate an item. The cards are distributed across the team (sized 2 10), with each of the cards representing a valid estimate. The reading on the cards could be something such as 0, 1, 2, 3, 5, 8, 13, 20, 40, and 100. Now, the product owner or the analyst describes the user story to the team, and the team can ask any related queries.

Each team member secretly selects a card number for an estimate, which is revealed when all the cards are turned over. The card with the most voting is the finalized estimate for the item under discussion. In case of uneven estimates, meetings are held, and the next round of voting commences to produce an estimate everyone agrees with.

T Shirt Sizing #

In this t-shirt sizing Agile estimation technique, the items are estimated in standard t-shirt sizes (i.e., XS, S, M, L, and XL). This is more of an informal but creative technique, and numbers can be assigned to each user story categorized under different t shirt sizes for better understanding.

A story estimated as XS is usually small and requires less effort than the XL story, which is large and has a big estimation number.

Relative Estimation is one of the several distinct flavours of estimation used in Agile teams, and consists of estimating tasks or user stories, not separately and in absolute units of time, but by comparison or by grouping of items of equivalent difficulty.

Fibonacci Sequence#

The Fibonacci sequence is one popular scoring scale for estimating agile story points. In this sequence, each number is the sum of the previous two in the series. The Fibonacci sequence goes as follows: 0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89… and so on.

# User Story Splitting

“Splitting ” consists of breaking up one user story into smaller ones, while preserving the property that each user story separately has measurable business value.

Story splitting user stories avoids overwhelm by giving the team smaller, more manageable pieces of work.

Story splitting helps teams deliver value to customers early and often.

Story splitting changes the mindset from thinking about layers of development to the experience of the user.

Story splitting requires that the team prioritizes the highest value goals and features for users

User Story Splitting Techniques

Split the user stories by roles

Break down the user stories by workflows

Divide the user stories by data types

Split the user stories by data entry

Split the user stories by business rules

Split user stories by acceptance criteria