Agile Release Management: Unlocking Value For Scrum & Kanban

Master release management fundamentals: set product vision with a vision board, create an agile roadmap, build user personas, and apply velocity and capacity planning toward an evolving definition of done.

Maximize your learning by using adjustable playback speed up to 2x or 0.5x, professional subtitles with CC, and transcripts, and provide ratings and feedback to help improve the course.

Develop a compelling product vision that sets a clear destination for the next two to five years, rallying the team and guiding early evangelists toward product market fit.

Create a product vision board to guide release management, defining a vision statement, strategy, two-sided passenger and driver needs, app features, and short, medium, and long-term goals.

Develop an agile product roadmap that emphasizes goals and outcomes to guide the team, align stakeholders, prioritize work, and adapt to uncertainty with a flexible plan.

Create a flexible agile product roadmap that centers on outcomes with defined goals and key results, not feature specific, using now, next, someday to plan releases.

Assess your release management state using quantitative metrics (average release time; type and priority of releases; errors; delays) and qualitative interviews to build a collaborative, lightweight process toward standard practice.

Evaluate your current state by combining quantitative metrics: release frequency, deployment duration, on-time delivery, defect escape, rollbacks, downtime, and value delivery, with qualitative interviews of key release management roles.

Identify your release’s target users by building data-driven user personas that blend assumptions, surveys, and interviews to inform ideation and align your teams, including marketing and design, around the product.

Create a user persona prototype by outlining assumptions, gathering data from interviews and analytics, and building a Canva or Extensible persona with traits, goals, frustrations, and channels.

The scrum guide 2020 defines a usable increment by sprint end, meeting the definition of done. The team decides when to release and may deploy continuously, even mid-sprint.

Compare velocity based and capacity based (commitment based) planning in agile sprints, detailing how to set sprint goals, select backlog items, estimate tasks, and check velocity against prior work.

Compute the team's velocity from three sprints by averaging story points delivered, adjusting for availability and commitment. Use velocity to inform release planning toward the product vision.

Define your release strategy by balancing risk, regulatory demands, stakeholder needs, and delivery infrastructure. Automate deployments, use feature toggles, and align with architecture to support frequent releases or infrequent cadences.

Evolve your definition of done with a three-zone exercise (now, next, future) where developers define the current DoD, plan improvements like automated tests and continuous integration, and envision longer-term capabilities.

Explore release planning fundamentals, then manage risk with MVPs and NCVHS, and practice fixed scope and fixed date release plans.

Explore how agile estimates measure effort for a work item, considering scope, complexity, and uncertainties, while clarifying that estimates are not targets or commitments and should separate estimation from planning.

Identify the iron triangle of planning, where date, budget, and scope constrain release outcomes. In agile release planning, fix schedule and resources in sprints, vary scope for MVPs.

Identify and mitigate value, usability, feasibility, and business viability risks using MVPs and MVFs, validating with low-risk releases and prioritizing outcomes over outputs.

Define your MVP by selecting a rider persona, outlining measurable outcomes and risky assumptions, and separating needs from wants to form a minimal viable feature set.

Identify external constraints and feature estimates to prepare release plans for scrum or kanban just in time. Visualize with a backlog line to define fixed date or fixed scope releases.

Develop a fixed date release plan by determining the number of sprints, estimating velocity as a range from historical data, and selecting must haves and might haves from the backlog.

Create a fixed scope release plan by totaling MVP backlog items into story points, estimating velocity as a range, and deriving optimistic and pessimistic sprint dates for stakeholders.

Explore the deployment pipeline and distinguish continuous integration, delivery, and deployment, then examine configuration management, the testing stack, and doc launches to guide future releases.

Discover the three key ingredients for great releases: modular architecture, strong team relationships, and automation. Implement API contracts, a bill of materials, and automated deployments to reduce risk.

Explore how the deployment pipeline delivers code from commit to production with push-button releases, enabling agile release management with build, test, and deployment automation for visibility, control, and traceability.

Understand how continuous integration merges changes into the main branch with builds and tests, how continuous delivery automates deployment to testing, and how continuous deployment pushes updates to production automatically.

Establish a central source of truth for assets, services, and configuration. Provide visibility into changes, states, purposes, and rollback across cloud and CCD infrastructure.

Explore the testing stack from unit to exploratory testing and how automation shapes the pyramid for faster end-to-end validation, with a focus on release-aligned test strategy.

Use dark launches to release production-ready features to a small user group via feature flags, enabling controlled rollout, feedback, and safe rollback without affecting all users.

Learn deployment strategies to minimize downtime and manage incidents while rolling out updates. Explore recreate, rolling updates, blue green deployment, and shadow testing with considerations for rollback and backward compatibility.

Assess readiness to scale agile and compare three scaling frameworks: safe, less, and Nexus. Get a high level overview with pros and cons and guidance on when to use each.

Identify signs your organization is ready to scale agile, such as interdependencies, duplicated efforts, and a uniform customer experience across teams.

Explore the scaled agile framework, its value streams and the agile release train. Learn how program increments enable regular value delivery, cadence, and release on demand.

LeSS scales scrum for multiple teams on a single product, delivering value while reducing complexity. Begin with basic LeSS for 2–8 teams, using one product backlog and one product owner.

Explore the Nexus framework, a lightweight expansion of Scrum with a Nexus integration team coordinating 3–9 Scrum teams on one product backlog to deliver an integrated increment each sprint.