Scrum Exams - Revision Sheets

Scrum: a Framework, not a methodology.

Delivers Adaptive Products of highest value to solve complex problems in volatile environment. It's the opposite of the waterfall process.

• Empirical process: Test and feedback oriented. Knowledge comes from experience.
• Lean: delivering superior customer value by eliminating waste - continuous improvement.
• 3 Scrum Pillars: Transparency, Inspection, Adaptation.
• 5 Scrum Values: Commitment, Courage, Focus, Openness, Respect.

5 Scrum Values

1. Openness: facilitates teamwork and collaboration.
2. Commitment: Scrum Team commits to goals. "It will be done no matter what"
3. Courage: Do it right. Courage?facilitates empiricism and collaborative teamwork.
4. Focus: Focus on the overall outcome.
5. Respect: Respect people, accountabilities, dedication, accomplishments.?

Other key concepts

Technical debt:?The result of prioritizing speedy delivery (quick and dirty) over perfect code (long term stability). Maintenance and fixing will be required.

Changes vs performance: When a change of people occurs within the Scrum Team, coordination and training will be required in a first place which will lower the short-term velocity. The same principle apply to adding a new Scrum Team on a product (for Nexus / Scaled Scrum)

No special Sprints: No hardening sprint or Sprint 0. All the Sprints must deliver an increment ready to be released in production whenever needed.

Scrum Team self-management: The Scrum Team is responsible for executing the tasks and monitoring and managing process and progress.

Integrated Increment: Multiple Scrum Teams working on the same product must deliver at least one integrated increment at the end of the Sprint.

Scaling vs Sprint lengths: Multiple Scrum Teams working on the same product may have different Sprint length and start/end dates (not recommended though). Nevertheless, they must integrate the increment by the Sprint Review.

Start the first Sprint: Scrum requires a Scrum Team and a Product Backlog with enough items for a first Sprint.

Size of the Scrum Team

Scrum Team (ST) : Typically 10 or fewer.

Product Owner (PO) : 1 per Product. Can also work as a Dev.

Developers (Devs) : Typically 10 or fewer.

Scrum Master (SM) : 1 per Scrum Team. Can also work as a Dev.

Multiple Teams working on a Product (Nexus / Scaled Scrum)

Scrum Teams (ST) : Frequent increments' integration. Coordinate, minimize or suppress dependencies. In Nexus: 3-9 STs.

Product Owner (PO) : 1 PO for all Scrum Teams. Remember : 1 product = 1 Product Owner = 1 Product Backlog

Developers (Devs) : Integrate often.

Scrum Master (SM) : 1 per ST maximum (1 Scrum Master can be in many Scrum Teams).

Definition of Done (DoD)

• ST defines DoD. The Devs apply it.
• DoD must follow organizational standards as minimum.
• Multiple Scrum Teams have one DoD.
• Includes testing.

I. ACCOUNTABILITIES

Scrum Team (ST)

Composed of a Product Owner, a Scrum Master and Developers.

No hierarchies. No dependencies. Self-managing and cross-functional.

The Scrum Team delivers valuable and usable increment every sprint. All product-related activities. Creating a valuable, useful Increment every Sprint. Improves every Sprint (via the Sprint Retrospective). Optimizes flexibility, creativity, and velocity. Receive feedback from users and stakeholders.

ST's commitment : The Product Goal

Product Owner (PO)

1 person, not a committee. Stakeholders and users representative. Visionary.

Maximizes the Value of the Product built by the Developers. Product Backlog Management.

PO's commitment : The maximum of value for the Product

Developers (Devs)

Cross-functional, no titles, multi-skilled.

Build the usable increment that meets the Definition of Done. Create the Sprint Backlog. Commit to the Sprint Goal. Ensure the increment meets the DoD.

Product Backlog Items estimation

Monitor the progress of the Sprint (Daily Scrum).

Devs' commitment : The Sprint Goal

Scrum Master (SM)

A true leader, facilitator and a coach. Supports the Scrum Team.

Promotes Scrum as it is described in the Scrum Guide ?within the organization. Accountable for Scrum Team’s effectiveness.

Facilitates?Scrum Events and ensures to keep them within time-boxes.

II. SCRUM EVENTS

Sprint

Time-box : 1 month max

Purpose (outcome) : Build a new increment

Participants : The Scrum Team

Sprint Planning

Time-box : 8 hours max

Purpose (outcome) : Define the Sprint Goal (why, what & how) and the Sprint Backlog

Participants : The Scrum Team (+invitees if needed).

Daily Scrum

Time-box : 15 mins max

Purpose (outcome) : Inspect and adapt the progress toward the Sprint Goal. Update the Sprint Backlog if needed. Talk about the current activity and impediments.

Participants : The Developers only (invitees can attend the Daily Scrum as silent observers).

Sprint Review

Time-box : 4 hours max

Purpose (outcome) : Inspect Increment and adapt the Product Backlog. Receive feedback in terms of changes, new requirements, new ideas...

Participants : The Scrum Team + Stakeholders.

Sprint Retrospective

Time-box : 3 hours max

Purpose (outcome) : Inspect the Scrum Team in terms of people, relationships, process, tools and plan improvements for the next Sprint. Review the Definition of Done that the Developers will have to apply to the next increments.

Participants : The Scrum Team only.

III. SCRUM ARTIFACTS

Product Backlog

Description : List of Product Backlog items (PBIs) which will compose new increments with the maximum of value. Dynamic and never complete, it's owned by the PO and frequently refined by the PO + the Devs.

There is 1 Product Backlog for 1 product owned by 1 PO.

Commitment : Value maximization and Progress Towards Product Goals

Sprint Backlog

Description : Selected Product Backlog items (PBIs) for the Sprint (at the Sprint Planning) which will compose the new increment and reach the Sprint Goal. It's owned and managed by the Developers and can be updated during Daily Scrums (with the agreement of the PO).

There is 1 Sprint Backlog for 1 Scrum Team. (Therefore on Scaled Scrum, there are as many Sprint Backlogs as Scrum Teams but still 1 Product Backlog for 1 product).

Commitment : Create a new increment and Progress Towards the Sprint Goal. In case of remaining work at the end of the Sprint, the incomplete Sprint Backlog Items will return to the Product Backlog for future Sprints.

Definition of Done (DoD)

Description : Standard of quality for the Increment. DoD is part of the standards of the organization?which all Scrum Teams must follow at a minimum.

Is case of Scaled Scrum, all Scrum Teams working on the same product must define and comply with a mutual DoD.

Commitment : Ensures a standard of quality for an increment to be potentially releasable.

MORE RESSOURCES

How To Become a Certified Scrum Product Owner :

Product Owner Certification Mock Exams 2022 – 800 questions :

Scrum Master Certification Mock Exams 2022 - 800 questions :

Scrum Master Level II Certification Preparation Tests :

Scrum map : https://www.xmind.app/m/v5sjPe/