Agile Project Management Fundamentals: Scrum, OKR and Kanban

Explore how the Scrum framework, rooted in agile principles, encourages continuous improvement, clear communication, and adaptability through short iterations and collaborative practices.

Explore scrum artifacts: product backlog, sprint backlog, and increment with a definition of done. Learn how these lists guide sprint goals and reduce risk through short cycles.

Explore scrum meetings that drive planning, communication, and assessment, including backlog organization, sprint planning, daily scrums, sprint review, and sprint retrospective, guiding increments with the product owner and scrum master.

The scrum team includes a product owner, a scrum master, and a development team who analyze customer needs, maintain the backlog, decide when to ship, and self-organize to deliver sprints.

Explore the five core values of Scrum—commitment, courage, focus, openness, and respect—and how they guide the development team, product owner, and stakeholders to achieve sprint goals.

Scrum, an agile framework, uses short sprints, backlog work, and cross-functional teams to increase transparency and accountability, while Kanban offers a simpler, limits-based alternative.

Scrum defines three roles: product owner, scrum master, and development team, by responsibilities, not job titles, allowing teams to stay with current skills while staying flexible and effective.

Be the product owner who prioritizes the backlog, coordinates with stakeholders, and guides the development team to deliver value through clear plans, releases, and continuous feedback.

Learn how the scrum master acts as a servant leader who ensures transparency, supports the team, and champions agile values while guiding the backlog, self-organization, and effective scrum implementation.

Self-organizing, cross-functional teams deliver product value by completing sprint work and advancing toward the increment in scrum. They hold daily scrums, address obstacles, and optimize collaboration to meet sprint goal.

Explore how user stories describe features from the user’s view and populate the product backlog. Learn how epics frame work, and apply the definition of done and the invest criteria.

Define a shared definition of done as a scrum checklist for every feature. Describe acceptance criteria as an adjustable extension tailored to specific user stories.

Define the definition of ready as clarifying which product backlog items are ready for the next sprint, with a clear quality checklist to maximize value and ensure testability.

Product backlog drives Scrum by compiling user stories from vision, roadmap, MVP, and stakeholders; the product owner creates and maintains it to guide sprint planning.

Discover how the sprint backlog serves as a plan by prioritizing items with the product owner, estimating capacity, and turning user stories into one-day tasks tracked on a three-column board.

The increment is the usable end product delivered at sprint end and meets the definition of done. Ensure a realistic sprint backlog and team collaboration toward a finished increment.

Sprints are fixed time periods with planned tasks from the backlog to deliver a usable increment, guided by sprint planning, daily scrums, sprint reviews, and sprint retrospectives.

Attend a sprint planning meeting where the product owner defines the sprint goal, selects user stories from the backlog, and the development team estimates capacity with the scrum master's guidance.

Showcase the development team's completed work to stakeholders in a relaxed sprint review. Define clear done criteria in backlog, test new features, and invite feedback.

Sprint retrospectives empower the Scrum team to reflect on past work, identify what worked and what didn’t, and create actionable improvements for the next sprint.

Prepare the product backlog for the next sprint by backlog grooming. Remove irrelevant stories, create new user stories, and reassess priorities and effort with the product owner and development team.

Set a clear sprint goal, definition of done, and priorities; maintain a backlog, plan in detail, and include bug fixing, quality assurance, and customer support estimates to ensure realistic sprints.

Adopt Kanban as a lean, just-in-time method that uses a whiteboard to plan what to produce, when, and how much, minimizing waste and coordinating the value chain.

Explore the four principles of Kanban, including finishing current tasks, incremental changes, modular workflows, and keeping existing processes, while using boards to track to-do, doing, and done.

Learn how a Kanban board visualizes tasks, uses backlog, to-do, and done columns, and enforces work in progress limits to drive continuous improvement and collaboration through daily status meetings.

Explore the pull methodology and kanban, using work in progress limits and visual aids to optimize flow, with a traffic light system signaling task status.

Use the kanban backlog as a brainstorming column for unprioritized ideas, with to-do column and work in progress limit. Split backlog into near-term and future columns to prevent lost ideas.

Explore how kanban cards use visual signals to trigger actions, define tasks with a responsible employee, lead time, creation date, and targeted submission date on flexible, virtual boards.

Compare lead time and cycle time on a Kanban board to gauge team productivity, manage backlog, and set work in progress limits.

Apply Kanban work in progress limits to prevent multitasking and keep work flowing. Set work in progress limits by column or team, monitor performance, and adjust as needed.

Divide kanban boards with swim lanes horizontally to keep a unified view, reduce clutter, and improve cross-team collaboration, while keeping backlogs visible and tasks aligned with deadlines.

Visualize workflow with kanban board using workflow mapping to split processes into to do, doing, and done columns. Use flowcharts to assign responsibilities and apply work-in-progress limits and swim lanes.

Explore seven Kanban cadences that keep agile teams focused on the present while sustaining a steady workflow through stand ups, replenishment, service delivery, planning, risk, and reviews.

Prioritize tasks by four service classes—standard, expedite, fixed deadline, and vague—with an emergency category for crises. Allocate capacities 20, 50, and 30 percent and enforce a work-in-progress limit on Kanban.

Explore flight levels for Kanban across four company levels, from team operations to strategic portfolio management, emphasizing coordinated input, value chain optimization, and enterprise-level planning.

Explore the OKR method, defining ambitious objectives with measurable key results to align teams and drive quarterly progress, with examples from Google.

Explore how OKRs boost agility, enable cross-team collaboration, and improve performance with shorter cycles, transparent goals, and accountable, focused work backed by stretch goals.

Explore the four core OKR values—alignment, transparency, commitment, and intrinsic motivation—and how they guide a value-driven, flexible corporate culture beyond rigid rules.

The OKR master acts as a servant leader who facilitates meetings, removes obstacles, and supports teams to implement OKRs effectively, guiding retrospectives and ensuring proper use of the method.

Explore how the OKR cycle unfolds from corporate goals to team and individual OKRs, with phased planning, weekly check-ins, progress tracking, renegotiation, end-of-cycle review, and retrospective.

Plan cadences for strategic and tactical levels with consistent OKRs and three-month cycles, synchronize teams to balance long-term goals and quarterly objectives, and avoid overly short or lengthy cycles.

Define OKRs as a joint, top-down and bottom-up process that aligns strategic goals with team actions, enabling teams to set tactical OKRs that support the company’s strategic objectives.

Learn how to define success with value-based key results in OKRs, focusing on measurable outcomes like attracting new customers, increasing app usage, and boosting website traffic.

Explore how to use OK to set stretch goals that push teams beyond comfort zones, and differentiate roof shots from moonshots to balance ambition with achievable progress.

Track progress with weekly check-in meetings for OKRs and key results within a quarterly cycle, using point-based progress, confidence assessments, obstacle resolution, and planning next steps.

OKR reviews conclude the cycle with a final status report, measuring progress toward objectives and key results, and ensuring updates are visible to all in a report or digital tool.

practice okr retrospectives to drive continuous improvement by reviewing what works, identifying issues, and generating actionable stop/start/continue ideas, with team-based brainstorming, prioritization, and cross-team sharing.

Identify and avoid the five common OKR mistakes, including too many objectives and treating tasks as key results, to sustain focus and measurable progress in early cycles.