Saturday, 18 August 2018

SCRUM - Quick Reference Guide (Part Two)


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

As part two, let’s move on other important aspect of Scrum.

Agile is all about depending on adaption, instead of a predictive (static, upfront) plan & design.

By time-boxing, the risk of pursuing a wrong direction is limited to the cost of one sprint.


source: Internet

Development Team (DT) characteristics: -
ü  Self-organising
ü  After the sprint review, DT should discuss this issue.
ü  No one (not even scrum master) tells the DT how to turn product backlog into increment of potentially releasable functionality.
ü  Estimating is the responsibility of DT.

Development Team sees the workloads: -
o   Remove items from backlog.
o   Discuss with the Product owner about this and monitor progress.

Development Team in First Sprint: -
o   Develop and deliver at at-least one piece of functionality.
o   Deliver an increment of releasable software.

DAILY SCRUM is only for ‘DEVELOPMENT TEAM’. Others can attend but they wont participate.

Product owner avoid waste in the product: -
·      By not adding too much details to product backlog items until they move to the top of the backlog.

Agile artefact’s – Product Roadmap should be updated at least semi-annually.
    Product Vision – should be at least once a year.

SPRINT REVIEW is a formal event, but informal meetings. It has two part – INSPECT (The increment) & ADAPT (The product backlog).

Eight stances of the scrum master: -
o   Servant leader
o   Coach
o   Facilitator
o   Teacher
o   Mentor
o   Manager
o   Impediment Remover
o   Change agent


Cone of Uncertainty: -
 How much is known about the product overtime.

Scrum Team-> is responsible for crafting the sprint goal at the sprint planning.

Sprint Planning input: -
·      Past performance of the Development Team
·      The latest product increments
·      The product backlogs
·      Projected capacity of the dev team in the sprint.


DEVELOPMENT READY - > Breaking down ‘stories’ into ‘manageable tasks’ per sprint and ‘DONE’ by the team definitions of ‘DONE’. In short, clear enough to be done in sprint.
Stakeholders review from previous sprint and add input to next sprint.


Five Scrum values: -
·      Commitment
·      Courage
·      Focus
·      Openness
·      Respect


For Scrum certification: -
            Scrum.org for PSM (Professional Scrum Master)
            Scrum Alliance for CSM (Certified Scrum Master)

Thank you!

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

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