Agile Transformation at an International Media Conglomerate: Based on a True Story | Part Seven



at---cx-circle---9b-sg-lowerres-6-squashed

Agile Transformation at an International Media Conglomerate: Based on a True Story


Scott M. Graffius, CEO of Exceptional PPM and PMO Solutions™, helps companies achieve their strategic objectives and business initiatives through project management leadership. A fantastic agile transformation outcome with a client organization in the entertainment industry was the inspiration for Scott's award-winning book,
Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions. This is the story behind the book—told by Scott. Identifying details have been changed and certain elements are not included.

This article is the seventh installment of the eight-part story. If you haven't already read the earlier parts, you can find them here:


Part Seven: The Pilot – Sprint Review and Sprint Retrospective

at---cx---the-call---sg---9b9---p7-lowerres-squashed

The Scrum team—Product Owner, Scrum Master, and the Development Team—and I discussed techniques for the sprint review. The event is sometimes referred to as the sprint demo. The timebox (not to exceed duration) in hours for the meeting was calculated as:

  • 1
  • multiplied by the number of weeks in the upcoming sprint (2 in this case),
  • which equaled 2 hours for the event.

Participants included the Product Owner, Scrum Master, Development Team, and stakeholders. All of the stakeholders (the executives mentioned in earlier parts of the story) were invited to and attended the sprint review. At the session, the Product Owner welcomed attendees and communicated the agenda. He pointed out the sprint goal, which was displayed on the wall in the meeting room. Next, the Development Team listed the work that was committed to the sprint. They then listed the work that was completed and the work that was not completed. For each completed story/feature, the Development Team demonstrated the "done" working functionality and answered questions. Stakeholders were invited to interact with the "done" working functionality and they did so. Then the entire group reviewed the product backlog and collaborated on what to do next. The Product Owner incorporated feedback into the Product Backlog. It involved adding new items to the backlog and/or re-prioritizing existing items. After the sprint review, the Scrum Master incorporated any feedback related to problems into the impediments backlog.

The Scrum Master and I discussed techniques for the sprint retrospective event. The timebox in hours for the meeting was calculated as:

  • 0.75
  • multiplied by the number of weeks in the upcoming sprint (2 in this case),
  • which equaled 1.50 hours for the event.

At the sprint retrospective, the Development Team identified what went well, what didn't go well, and improvements to be implemented in the upcoming sprint—an example of inspection and adaptation. For improvements to be implemented, each member of the Development Team wrote their top one, two or three suggestions on sticky notes. Each idea got its own sticky note. Then the Development Team grouped the sticky notes into categories/themes, and they discussed the items and voted to determine the top one (initially limited to one, later it was raised to two) for adaptation and improvement. The Development Team committed to the change and the Scrum Master recorded the information.

Agile Transformation at an International Media Conglomerate: Based on a True Story concludes with Part Eight: The Success.

© Copyright 2019 Scott M. Graffius. All rights reserved. This material may not be published, broadcast, rewritten or redistributed without the express written permission of Scott M. Graffius.




custom - back to main page of blog