Scrum is a framework that provides structure and process for continual transformation of a VISION into highest VALUE in shortest time, creative way, adaptive manner, and valuable collaboration.

Focus – focusing on a small subset of items with highest value ensures better team work and higher quality deliverable.

Courage – collaborative work of cross-functional members instils courage to tackle greater challenges than an individual could take.

Openness – co-location, meetings, and information radiators ensure team’s results, works, and challenges sharing and openness.

Commitment – sprint ownership and self-organization create strong commitments to the goal.

Respect – team work and sharing sprint success and under-delivering necessitate respect and help each other become worthy of respect

Founded on empiricism, which assumes that knowledge comes from experience and making decisions based on what is experientially known, Scrum enforces:

Transparency, e.g., DoD, DoR, Daily Standup

Inspection, e.g., Sprint review, product demo

Adaptation, e.g., Prioritization, sprint planning, retrospective

Retrospective allows the team to inspect and improve its process in the subsequent Sprint.

Scrum has three roles:

Product Owner PO: Voice of customers, manages PBIs, ensures maximum ROI, has expertise of the product Scrum

Master SM: A servant-leader who enforces Scrum practice and rules, facilitates scrum ceremonies, helps PO, sets effective collaboration, possesses coaching skills, facilitation techniques, and leadership qualities, removes obstacles, and empowers the team.

Development Team: Self-organizing, Cross-functional, Creates the Increment. Team’s size is recommended 6±3 members, excluding PO and SM.

Other people involved are Stakeholders, Users, Sponsors, Customers. Stakeholders: Review increment, Provide feedback, Suggest new PBIs

Sprint Planning | Daily Standup | Sprint Review | Sprint Retrospective

Backlog Refinement, usually consuming no more than 10% of the Development Team’s capacity, is an ongoing activity.

Also a good practice is frequent User Acceptance Testing.

The following time boxes indicate maximum allotted time based on one month Sprint, reduced proportionally for shorter Sprints. Daily Standup always remains 15 minutes:

Sprint Planning 4h | Daily Standup 15 min | Sprint Review 4h | Sprint Retrospect 3h

Product backlog | Sprint backlog | Increment

Functionalities delivered by the Sprint are collectively referred to as an Increment Other artifacts are: Sprint goal, DoD, DoR…

Scrum team creates, continually reviews, and agrees on Definition of Done (DoD) and Definition of Ready (DoR) throughout the project.