Earlier this year, the Center for Medicare and Medicaid Services launched their new Quality Payment Program (QPP), which aims to deliver real-time, actionable feedback to doctors to help shift healthcare to focus more on the quality of care provided. QPP used agile development to develop a product that exceeded its first year goals, all while navigating the challenges posed by working on a government program with multiple contractor teams and legislatively mandated deadlines.

In this experience report, I will share the lessons learned over the last year of working on QPP, including how we managed legislative deadlines while staying agile, coordinated delivery across 20+ teams, and built a collaborative culture across multiple contracting companies and our government stakeholders. The session will end with an interactive discussion where attendees will be asked to reflect on their own projects and think about how they could apply some of these lessons learned within their environments.

 
 

Outline/Structure of the Experience Report

  • Introductions
  • Project Background
    • What is the Quality Payments Program?
    • What goals did CMS have for the first year of QPP?
    • Team Composition
  • Tools for Managing Deadlines
    • Milestone Planning
    • MoSCoW Prioritization
    • Risk Registry
  • Scaling Agile Up
    • What wasn't working
    • SAFe Overview
    • Our first PI Planning
  • How did we do?
    • Goals & KPIs
    • Stakeholder Feedback
    • User Feedback
  • Lessons Learned
    • Managing Products not Projects
    • Maintaining a System View
    • Focus on the Business Value
    • Build a Collaborative Culture
  • Interactive Discussion
    • Individual Reflection
    • Small Group Discussion
    • Large Group Sharing
    • General Q&A

Learning Outcome

  • The value of aligning teams around a clear product vision.
  • A toolkit for managing firm deadlines in an agile environment.
  • An introduction to SAFe and the value it can provide on large projects.
  • The benefits we gained from building a unified culture across contract teams on a program.

Target Audience

Scrum Masters, Agile Team Members, Product Owners

Prerequisites for Attendees

Attendees will get the most out of this presentation if they have a base knowledge of agile and scrum.

schedule Submitted 1 year ago

Public Feedback

comment Suggest improvements to the Speaker
  • George Dinwiddie
    By George Dinwiddie  ~  1 year ago
    reply Reply

    I like these aspects of the submission, and they should be retained:

    • Experience reports are great when they show both the successes and failures of the experience.

    I think the submission could be improved by:

    • Telling prospective attendees in the description what sort of lessons they might take away from this session.
    • Be careful not to over-generalize and over-promise based on one experience. That may not translate to the situations that others face.
    • Austin Gardner
      By Austin Gardner  ~  1 year ago
      reply Reply

      Thanks George! I've updated my description to give attendees a better idea of what to expect from the session, and have also expanded the Q&A section into an interactive discussion where attendees can reflect on how they could apply some of these lessons to their own projects/environments.