Aside Posted on
Enjoying the questionnaire Nissreen Barakat. I have pondered this question for a while too. I don’t feel like the answers I’ve found so far tell the whole story, although most are decent. What are your thoughts?
From your point of view, what is the definition of organizational agility?
My take at starting the discussion:
An internalization [permanent] of the capacity of an organization to consume simple, complex and/or complicated problems quickly without requiring a formal reconfiguration or restructuring (adaptability) of the organization’s internal structure while being able to deliver on the mission and value delivery in a way that customers of the organization would consider successful outcomes. Measurable organizational agility would be reflected as a learning culture focused on relentless improvement with no regret failure. “Pivoting without mercy or guilt” as Leffingwell and Knaster would say. Learning cultures in organizations should also be able to consume chaotic problems by bringing order to the chaos through iterative experimentation and study of outcomes and generation of new hypothesis. Also, organizational “agility” is possible without “Agile.”
#SAFe #Agile #agility #organizationalagility #howto #whatnext
Have you ever worked in an organization run by committee? All decisions requiring consensus, even the minutiae? Immutable command and control structures that were often too busy to collaborate with underlings? What did their results look like? I like how Mel ties in the social construct and communication into the discussion of organizational structures. How we work together is important, just like what we are working on.
To the extent that an organization is not completely flexible in
its communication structure, that organization will stamp out
an image of itself in every design it produces.
… Because the design that occurs first is almost never the best
possible, the prevailing system concept [the design] may need to
change. Therefore, flexibility of organization is important to
effective design. Ways must be found to reward design managers
for keeping their organizations lean and flexible.
We had a “SAFe Air Bear” visit us for P3 PI Planning this week! Hilarious selfie’s ensued… The SAFe Air Bear was motivating our Agile Release Planes (ARPs) to successfully plan out feature flights for the next three months (Program Increment three).
Two ARPs, and a little over 150 people participated. Still working on feature / PI Objective counts… Release Plane Flight Engineers, where are you?
We are formally requesting an “Air” version of the SAFe. Airplanes are faster than trains. They can go where trains will never reach without tracks. Quality is higher on a plane than a train. Airplanes can break the sound barrier. In-flight entertainment.
Due to privacy laws, I had to blot out people. But not the SAFe Air Bear. I do not work for or represent Scaled Agile Inc…
Coaches and Practitioners of Lean-Agile and the SAFe
In my experience the amount of time that we get to spend in Lean-Agile and SAFe courses on the subject of Velocity and Capacity Planning is inadequate. So I spent some time building a tool for one of my client organizations. I have since spent some time greatly enhancing the tool and getting it ready for distribution. I am offering the tool for free. All that I ask is if you decide that the tool has value and you are going to use it, to like my blog. Perhaps even share this article on your favorite social media. Read the rest of this entry »
The good folks at Scaled Agile, the SAFe® community, Agile agnostics, consultants, and some in the “Agile” community are onto something incredibly important in defining the elusive and dynamic Agile End Game for organizations. Read the rest of this entry »
Aside Posted on Updated on
I can’t say that I agree at all with Dave Snowden’s approach to communication. The guy is rough around the edges, a “perpetual curmudgeon” in his own words. And that is describing it kindly. He does have some good ideas on decision making though. Read the rest of this entry »
S_Fe is not Agile. S_Fe is not even Scrum. – Mike Beedle
In response to Mike Beedle on LinkedIn. Mike is wrong about the SAFe of course. And not just because of his childish method of attack. Facts, evidence, experiments, my experience and dozens of business case studies back up the experiments of the SAFe. Mike sounds a lot like project managers that swear the PMBoK/waterfall works better than agile for large scale “projects” with high complexity, significant uncertainty, many dependencies and new knowledge to be obtained to deliver the product. Project management works in those scenarios (fantasy). But not as well as Agile (reality). Read the studies (Chaos Report, Standish Group; State of Agile, VersionOne; others). A sea change is in play — right now. Customers want predictability, results — and truth. Not endless “Change Requests” and contract modifications for more time, more money and more people. One truth about the Agile Manifesto is that it is great guidance as a value system and principles for software development. The big problem is that it [Agile Manifesto] is STATIC. Relentless improvement drives us to go beyond yesterday. Study the Scaled Agile Framework for the enterprise and come to your own conclusions. Evolve or join the museum with the other artifacts of the information age.