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