Professional Certificate in Agile and SCRUM

Contrast waterfall and agile by showing six-month release cycles versus one-month iterations that deliver MVPs, gather customer feedback, and reduce risk through continuous learning.

Learn how to define a minimum viable product (MVP) and apply an iterative, incremental agile approach that delivers usable, feedback-driven improvements from a skirting board to a car.

Discover the agile mindset, its four values and 12 principles, and how frameworks like scrum, design thinking, and xp drive practices such as self-organizing teams, cadence, time-boxing, and retrospectives.

Learn how agile values prioritize individuals and interactions over processes and tools, and working software over comprehensive documentation, driving collaboration, efficiency, and real product value.

Explore agile values that boost adaptability and customer satisfaction by prioritizing customer collaboration over contract negotiation and responding to change over following a plan.

Explores the agile manifesto's 12 principles for delivering valuable software early and continuously. Highlights daily collaboration, welcoming changing requirements, working software, sustainable pace, self-organizing teams, and continuous improvement.

Defines scrum as a lightweight framework, not a methodology, for solving complex problems. Explains how scrum master, product owner, and scrum team work with backlog, sprints, increments, and stakeholder inspection.

The scrum framework, grounded in empiricism and lean thinking, rests on transparency, inspection, and adaptation, and uses three accountabilities, five events, and three artifacts to deliver increments.

Explore scrum artifacts and commitments that structure the product backlog, define sprint goals and the definition of done, and enhance transparency, focus, and measurable progress.

Explore the theory of scrum, rooted in empiricism and lean thinking, and how iterative, incremental sprints with cross-functional teams enable the three pillars of transparency, inspection, adaptation.

Explore the three Scrum pillars—transparency, inspection, and adaptation—and how artifacts like the product backlog, sprint backlog, and increment enable inspection by the team and stakeholders, with formal events guiding adaptation.

Explore the five scrum values—commitment, openness, courage, respect, and focus—to guide goals, reveal challenges, and reinforce transparency, inspection, and adaptation in agile teams.

Explore how the scrum team, up to ten people, unifies a product owner, a scrum master, and developers to deliver a useful product increment each sprint through self-management and cross-functionality.

Plan the sprint backlog, adapt daily, and deliver a usable product increment as developers in a scrum team who hold each other accountable without a manager.

Define and communicate the product goal, maximize value of the product, manage and order the product backlog, and ensure its transparency to all stakeholders as the accountable single product owner.

The scrum master establishes the scrum, coaches the team, and ensures events, clear product backlogs, and value-driven increments. They support the product owner and stakeholders through empirical planning and collaboration.

Identify stakeholders defined in the Scrum Guide Expansion Pack, including customers, users, decision makers, sponsors, regulators, experts, and even laws or AI systems, and engage regularly.

Explore the Tuckman model of group development and its five stages—forming, storming, norming, performing, and adjourning—to optimize team collaboration, roles, and high-quality outcomes.

Manage the product backlog as a single, transparent, ROI-driven list owned by the product owner; top backlog items maximize value and clarity in a living, evolving plan.

Define the product goal as one active, long-term objective guiding the product backlog and sprint planning toward the product vision. Refine it in sprint reviews as market needs evolve.

The sprint backlog defines what the team will deliver this sprint, including the selected product backlog items and the plan for delivering the increment to achieve the sprint goal.

Define the sprint goal as a commitment and single objective that explains why the sprint exists, guides the sprint backlog PBIs, and enables renegotiation of scope without changing the goal.

define the definition of done as the formal state where an increment meets quality measures—code is reviewed, tests pass, and documentation is updated—ensuring transparency for the scrum team.

Learn how the scrum framework guides agile product development from idea to release, prioritizing features, building the product backlog and PBIs, running sprints, and delivering a shippable increment.

Explore how user stories guide agile product development by articulating who, what, and why in the as a user I want so that format, and applying invest criteria.

Learn to write better user stories through the 3 c's: card, conversation, and confirmation, for agile teams to deliver real value.

Apply the Rice framework to quantitatively prioritize product initiatives by evaluating reach, impact, confidence, and effort, then rank features to drive data-informed roadmaps.

Fix sprint length, such as two weeks, protect the sprint goal, and keep the sprint backlog stable while delivering a product increment and refining the backlog with the product owner.

The sprint acts as a container for all other scrum events, including sprint planning, daily scrum, sprint review, and sprint retrospective. Each sprint ends with a product increment.

Describe how scrum events create regularity and transparency by inspecting and adapting artifacts (product backlog, sprint backlog, and product increment) based on feedback, with fixed times and places.

Master sprint planning, a core scrum event, to decide why, what, and how for the upcoming sprint. Create the sprint goal and sprint backlog as a forecast guiding delivery.

The daily scrum is a 15-minute, time-boxed event where developers inspect progress toward the sprint goal and plan the next 24 hours.

Inspect the last sprint and adapt to improve people, processes, tools, and the definition of done. Achieve continuous improvement through actionable changes for better team collaboration.