Category: Scaled Agile Framework

How to PI System Demo like a boss

SAFe® The Evidence Series #1

Check out the amazing things that high performance, motivated teams can do. This is business agility and Lean-Agile culture at its best. The transformation of my client’s organization is amazing. We are using Lean, Agile, Scrum, Kanban (and systems thinking), SAFe®, OrgMindset®, and other tools to inspire and persuade a positive change in culture at the FAA-ESC.

It is hard work, but it is worth every minute of it. It isn’t perfect, but the results are significant and measurable. The “why” was a burning platform. Now, just a few PI’s later, it is a thriving platform. We focus on the goals, not the tools to achieve positive business outcomes.

Congratulations to Team Armada for winning the “Relentless Improvers” innovation football for PI6.

Big kudos to John Wiese and his team for putting together an awe-inspiring PI System Demo.

Special thanks to the FAA-ESC, John Wiese, and teams for providing permission to publish the video under the safe harbor notice/policy. Also, special thanks to Matt Taylor for sharing a different video perspective as a content contributor.

#SAFe #Agile #Culture #OrgMindset #BigLakeSoftware

 

man flip chart

Advertisements

VersionOne 12th Annual State of Agile Report – Scaling Methods Growth Comparison

The newest VersionOne 12th Annual State of Agile Report was released on April 9, 2018. Last year I compared the growth of scaling frameworks and methods to each other year over year. (click here to see the report from last year) Continue reading “VersionOne 12th Annual State of Agile Report – Scaling Methods Growth Comparison”

The Agile End Game & the Agile Fallacy

March 28, 2018 - by Marshall Guillory

Agile is itself a fallacy

“We are ‘Agile’ because we were delivering ‘working software’ every two weeks”

But did we build the right thing? Do the right thing? Was it valuable?

Oops, we forgot to read the details… the values AND the principles are important. Is it a good thing they clarified the value in the #1 principle on the second page?

What about culture? Not so simple as four plus twelve equals Agile? Continue reading “The Agile End Game & the Agile Fallacy”

SAFe® POPM Guide

The first SAFe® POPM Guide & Checklists

Blogagility.com and our sponsor Big Lake Software are very pleased to present the first guide with checklists designed for SAFe product stewards & practitioners – The Blogagility.com SAFe® POPM Guide & Checklists (View interactive version here). The guide includes checklists for each of the roles in a scaled agile implementation using SAFe as a framework. Each checklist includes guidance on the following topics as follows. Click the links below for the individual portions of the guide and the checklists: Continue reading “SAFe® POPM Guide”

Agile Moment: Lego Serious play for Teams Sim

During the Lego Serious play for Teams Sim this week one of the teams decided they were a component team supporting the rest of the ART.

Do you think the experiment worked?

Continue reading “Agile Moment: Lego Serious play for Teams Sim”

Retrospectives @Scale within SAFe® portfolio context

Did you know that the value of facilitating retrospectives is also valuable at scale? In other words, facilitating cross-organizational retrospectives. Improvement is necessary to create better business outcomes. Relentless improvement should be a prime directive in every Lean-Agile organization.

In particular, if you are working within a Lean-Agile SAFe® portfolio you may be familiar with some of the following retrospectives. Others may not be so obvious. The point of which is that we should retro our performance for significant activities/ceremonies. When there are obvious bottlenecks in the system, do a retro, and use wisdom when this is not the case. And remember the easiest way to fail at a retrospective is to neglect to create improvement stories that make their way into the backlog. Continue reading “Retrospectives @Scale within SAFe® portfolio context”

The Death of Agile – How to rename stuff and make money

I’m sitting here on Sunday morning thinking about how there is a propensity in the “Agile” space to re-name or [re] label things that already exist so they supposedly become “new” things. That action in of itself is not bad. It can create new value, new wealth, new knowledge. Perhaps?

It becomes bad when it is sold as something entirely new, but it isn’t actually. Where is the innovation? In the content or context — how the pieces were moved around or collected or displayed?

Continue reading “The Death of Agile – How to rename stuff and make money”