Definition of SCRUM :
Scrum is one of the Agile
frameworks followed to complete challenging projects wherein there are dynamic
changes in the requirements by using one or more cross-‐functional,
self-‐organizing teams of about 7 +/-‐ 2 people on each team.
Standards of Scrum :
· Scrum consists of 3 roles: product owner, ScrumMaster, and development team/engineering team. Roles and responsibilities of each role will be elaborated in the following sections.· Scrum uses fixed-‐length iterations called sprints ranging from one Week four weeks (or 30 days long).
· Scrum teams should consist of 7 +/-‐ 2 people.
· Sprint cannot exceed more than 30 days.
· Sprint is time bound.
· Scrum team aims to build a potentially shippable product by end of each sprint.
· Daily Scrum / Stand-‐up meeting should be only for 15 mins. and as the name goes, the team should be standing during entire meeting time.
Estimation and Techniques:
Once the team has worked for
a while in Agile projects, their ability to estimate the user stories becomes
much better and more accurate.
But teams new to Agile
sometimes face difficulty in estimating the points for the user stories.
Below are the few estimation
techniques, which can be used to estimate the user stories accordingly:
Planning Poker
Planning Poker is a game that the team members can play
during planning meetings to make sure everyone participates.
To begin with, each team member is given with set of cards
with numbers on them. Usually the team follows the Fibonacci sequence: 0, 1, 2,
3, 5, 8, 13, and 21.
Then each story is read aloud. After each story
presentation, each of the team member is asked to hold up the card showing the
level of effort involved according to them.
Once every team members gives the points forthe story, the
one with lowest value and the one with highest value will be asked to explain
why they have chosen that value. Experts with detailed knowledge will be able
to explain to the team why a certain story is much easier/more difficult than
it first appears.
Then the team will come to an agreement on the estimate for that user story and conclude on that.
T-‐Shirt Sizes
At times it happens that the team members startaligning the
story points with the hours of effort, which can create confusion. To avoid
this, it may be more effective to switch to a non-‐numeric estimation
technique.
With T-‐Shirt Sizing, the team is asked to estimate the
story effort in terms of extra-‐small, small, medium, large, extra-‐ large,
or double extra-‐large. By removing the numeric concept, team will be free to
think in more abstract way. But there is a practical issue involved with this
method. Non-‐numerical scales are generally less granular. While that can
speed up the voting process by reducing the number of options, it may also
reduce the accuracy of velocity estimates.
For the above reason, the T-‐Shirt Sizes method of
estimates will be good for the teams just starting with Agile projects.
Eventually it’s a good idea to move toward numeric method of estimation.
Relative Mass Valuation
Usually the process of deciding the story point for each
story will consume lot of time. With this method,it consumes less time.
0 Comments