Scrum Bookends Sprint Planning to Sprint Review & Retrospective

Scrum Bookends – Sprint Planning & Sprint Review/Retrospective

  • Improve Adaptive Execution
  • Seek Better Feedback

 

Why?

The “bookends” of Scrum are Sprint Planning and Sprint Review.  The importance of these meetings is critical for results, and yet they remain some of the hardest skills to master. With these skills you can establish a flow of value. Without these skills we have seen teams fail to deliver in the context of strategic goals, fall apart as a unit, rely on top-down, “chain of command” behavior and abandon agile practice.

These issues are recognized. We focus on mastery of techniques and skills around planning, product demonstration, and retrospective meetings.  Application of these skills is critical for success. However, many of the deeper aspects of these skills are not fully appreciated until someone has been applying agile/scrum for some time as part of a well formed team. It takes most teams many months/quarters/years of working together to discover and apply these skills.

This course is geared at helping you cut down the learning curve by rapidly acquiring these agile techniques through an applied immersion experience. By incorporating techniques used successfully in product development efforts with teams as large as 80, and across numerous industry verticals, attendees will be better equipped to connect sprints into a smooth flow of value delivered and realize the promise of agile adaptation.

Agenda

  • Leverage natural rhythms in your team’s environment
  • Connect sprints together to achieve “long-term” gains
  • Tap the power of the Scrum framework to navigate extreme complexity
  • Plan
    • Product plans which balance strategic and tactical views
    • Create plans from “non-agile” sources
    • Build ROI in easy to track steps
    • Use stories to maintain team focus
    • Generate Sprint plans which adapt to emerging situations
    • Balance the needs of the sprint, the team, the product, and the organization
  • Learn the importance of the Product Demo
    • Pulling critical business involvement to validate the team’s work
    • Driving speed and quality
    • Building trust and enthusiasm with stakeholders
  • Run solid retrospectives
    • Help the team take ownership of its process
    • Engage teams awareness to foster self-organization
    • Let Agile drive architecture instead of the other way around
    • Nurture emergent behaviors to build Well-Formed Teams

Attendees will create work products (agile plans and retrospective reports) and use multiple tools during the session.

Objectives

Our goal is to help you leave armed with the following techniques / skills:

  • How to plan just enough
  • Ways to Stimulate great team environments
  • Use multiple tools during the session
  • Sharpen pragmatic skills and thinking
  • Master engaging team dialog and learning
  • Adaptive plans and how feedback loops work at every level
  • Informed decision making
  • Product results and how to keep business interest close
  • Techniques to raise awareness of yourself, your team and your org
  • Take-away work products and tools made available to the students after the session, along with two whitepapers relevant to the topics covered

Who Should Attend

This course is for people who have some background in agile project work. It is intended to help experienced agile practitioners focus on the difficult challenges of tuning aspects of their agile implementation:

  • Scrum course students (e.g. attendees of “Certified ScrumMaster“) desiring a “deep dive” into techniques for more effective Sprints
  • ScrumMasters who wish to improve their team’s sprint planning effectiveness
  • Agile development team members who want to work better as a team
  • Project managers who want to integrate agile plans with their organization’s traditional project management needs
  • Product Owners seeking better visibility into the strategic view of their product being developed

Prerequisites

  • Participants should have some familiarity with Agile, either by attending beginner Agile training or through some practical Agile experience.
  • Participants should be prepared to review the problem domain background material prior to attending the session.