• Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 24 other followers

  • Archives

  • Advertisements

SCRUM – Stories and Estimation – Part I

Story is a useful perceivable Value to a stakeholder.

Customer or Scrum master can define stories for the prioritized backlog items in the running sprint. It should be done in user pitch and to developer understanding. There is no firm requirement in defining stories.

We can use the SCRUM acronym for defining and estimating stories.

S – Specific to functionality being developed
If the story is “Dashboard Report “(of a Project management Tools in development) – it can be something like this:

“As a Project Manager, I want Status Graphs of running project so that I can know about completed and pending functionalities of my project.”

C – Criteria of acceptance– clear and independent as much as possible
Dashboard report should have
Status graphs for indicating completed functionalities,
Remaining functionalities,
Status on all functionalities with respect to delay/on time/
deferred / closed.
Escalation for delays.

R – Realistic – can be executed in the current sprint
Have the ability to complete in present sprint and is independent functionality

U – User valuable – valuable for stakeholders
Stake holder – Project manager and other users can view the
status of project any time

M – Measurable – can estimate them and test them
Can measure the effort for the Story called “Dash Board” and can be further subdivided into tasks and they also can be estimated.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s