SCRUM - Quick Reference Guide (Part One)

Scrum is being used widely in software & IT industry to define, measure & deliver business requirement in working software.

Scrum controls the risk associated with long term planning & big commitments by constraining the product development into shorter iteration called sprints.

source: internet

Scrum is founded on empirical process control theory or empiricism: -

·      Transparency

·      Inspection

·      Adaptation

Empiricism asserts that knowledge comes from experience and making decision based on what is known.

Scrum compromised of: -

·      Roles

·      Rules

·      Events

·      Artefacts

Scrum team Role: -

·      Scrum Master

·      Product Owner

·      Development Team

Scrum Events consists of: -

·      Sprint planning

·      Sprint retrospective

·      Daily Scrum

·      Sprint Review

·      Sprint

Sprint Planning consists of two sections: THE WHAT & THE HOW.

Duration of Sprint planning depends on Sprint

Sprint Duration	Hours for planning
2 weeks sprint	4 hours
3 weeks sprint	6 hours
4 weeks sprint	8 hours

Daily Scrum (stand-up): - 15 minutes time boxed

ü  What did you do yesterday?

ü  What will I do today to help?

ü  Impediments.

Team model is scrum: -

    Productivity

    Flexibility

    Creativity

Five powerful things about the sprint: -

o   Focus

o   Predictability

o   Control

o   Freedom

o   Opportunity

Product Backlog features: -

§  It is never complete.

§  It is dynamic.

§  As long as Product exists, its Product backlog also exists.

Product backlog refinement usually consume no more than 10% of the capacity of the development team.

Note: It is OK for the Product owner and the scrum master to be in development team.

Product backlog refinement is the act of: -

Ø  Adding details

Ø  Estimates

Ø  Order    to the backlog.

To be continue......

Thank you!

Satender Kumar Mall
Twitter: @satenderiiit

Facebook Page: https://www.facebook.com/pages/Satender-Kumar-Mall-Blogs