Professional Diploma in Agile and Scrum

Demonstrates how waterfall delays a first product release for six months, while agile delivers MVP increments in one-month cycles, enabling customer feedback and reduced risk.

Define a minimum viable product (MVP) and apply an incremental agile approach, using early user feedback to evolve from a board to a car.

Explore the agile mindset, its four values and twelve principles, and how practices like Scrum, time box, and retrospectives enable self-organizing teams.

Discover how agile values prioritize individuals and interactions over processes and tools, and working software over comprehensive documentation to boost collaboration, efficiency, and adaptive teams.

Agile values favor customer collaboration over contract negotiation and responding to change over following a plan, guiding Scrum teams to build the right product with adaptability.

Apply the agile manifesto and its twelve principles to deliver valuable software early and continuously, welcoming changing requirements and collaborating daily with business and developers.

Scrum is a lightweight framework, not a methodology, uniting Scrum Master, Product Owner, and Scrum Team to transform product backlog into sprint backlog and increments through sprint planning and inspection.

Master the scrum framework, founded on empiricism and lean thinking, emphasizing transparency, inspection, and adaptation. Learn the three accountabilities, five events, three artifacts, and the lightweight, practice-heavy path to mastery.

Explore scrum artifacts and commitments, including the product backlog and sprint backlog, and how the product owner, developers, and scrum master collaborate toward the product and sprint goals.

outline scrum theory built on empiricism and lean thinking, explain the house of scrum pillars, and emphasize iterative delivery with cross-functional teams and events for inspection and adaptation.

Explore how transparency, inspection, and adaptation form the foundation of scrum, using visible artifacts (product backlog, sprint backlog, increment) and formal events to inspect and adapt through empiricism.

Discover how scrum values—respect, openness, courage, commitment, and focus—guide team behavior, decisions, and the embodiment of transparency, inspection, and adaptation.

the scrum team, a self-managing unit of up to ten people (one product owner, one scrum master, up to eight developers), collaborates cross-functionally to deliver a usable increment each sprint.

Developers in scrum plan sprint backlog and adapt their plan to hit sprint goal. They deliver a usable increment by handling architecture, coding, testing, and user interface design.

Learn how the product owner maximizes product value by defining and communicating the product goal, ordering and making the backlog transparent, and aligning stakeholders.

Enable the Scrum across the team and organization by establishing Scrum Guide practices and events, coaching the Product Owner and developers, and removing impediments to deliver high-value increments.

Identify stakeholders defined in the scrum guide expansion pack, including customers, users, decision makers, sponsors, regulators, experts, and non-human entities like laws and AI systems.

Explore the Tuckman model of group development and its five stages—forming, storming, norming, performing, and adjourning—to guide leaders and teams toward effective collaboration and high-quality outcomes.

The product backlog is a transparent, living list of backlog items for sprints, ordered by return on investment and dependencies to maximize customer value, managed by the product owner.

Set a single, measurable product goal that guides the product backlog and sprint planning, refining it in sprint reviews with the product owner and stakeholders.

Navigate the sprint backlog as a highly visible plan that links the sprint goal with selected PBIs and the how parts, including coding, refining, and testing.

Commit to a single sprint goal that explains why the sprint exists for stakeholders and guides PBIs with focus and flexibility, while renegotiating scope without changing the goal.

Master how an increment advances the product goal in scrum, delivering usable value. See how increments are additive, verified, and released continuously within a sprint.

Learn how the definition of done formalizes when an increment meets quality criteria, ensuring transparency, accountability, and release readiness in scrum projects.

Explore agile product development with scrum, from idea through product vision and market analysis to backlog prioritization, sprint planning, and delivering a valued increment.

Master user stories to articulate who, what, and why, delivering independent, negotiable, valuable, estimable, small, and testable features that foster clear scrum team alignment and value delivery.

Learn the three Cs—card, conversation, and confirmation—that make user stories clear, discussed, and testable, ensuring agile teams understand requirements and deliver valuable, actionable software.

Apply the Rice framework to quantify reach, impact, confidence, and effort, then calculate a Rice score, computed as impact multiplied by confidence divided by effort, to prioritize product initiatives.

Sprints define the heartbeat of scrum with fixed length, protecting the sprint goal, refining the backlog, and delivering a product increment.

Explain how a sprint acts as a container for all other scrum events—sprint planning, daily scrum, sprint review, and sprint retrospective—delivering a product increment in each sprint.

Inspect the scrum artifacts—product backlog, sprint backlog, and product increment—and adapt based on learnings and stakeholder feedback at every scrum event to enable transparency and regularity per the scrum guide.

Align the scrum team on the why, what, and how of the sprint. Create a sprint goal and sprint backlog as a forecast, not a commitment.

Daily Scrum is a 15-minute time-boxed event for developers to inspect progress toward the sprint goal and plan next 24 hours, with the Scrum Master and Product Owner attending optionally.

Explore how a sprint review inspects the sprint increment and aligns stakeholders. The product owner leads a time-boxed, collaborative session to adapt the backlog and plan the next sprint.

The sprint retrospective is the final scrum event to inspect and adapt people, processes, tools, and the definition of done, producing actionable improvements to boost quality and effectiveness.