The requirements both for an approach and for its Architecture
From the Manifesting Business Agility Blog
by Al Shalloway
This blog concerns itself with organizations moving to business agility—the quick realization of value predictably and sustainably, and with high quality. It includes all aspects of this—from the business stakeholders through ops and support. Topics will be far-reaching but will mostly discuss FLEX, Flow, Lean-Thinking, Lean-Management, Theory of Constraints, Systems Thinking, Test-First and Agile.
Recent Posts
What is a Lean-Agile Coach?
My Approach to Sensemaking in Knowledge Work
Why if you are a PMP who understands the value of Agile your next workshop should be the Disciplined Agile Value Stream Consultant
My views (past posts) on cause and effect in complex systems
Transcend the thinking that scope, time and cost are in opposition to each other with Lean-Thinking
Categories
lean,
value streams
Date
Any approach to Agile at scale must attend to the following:
- Organizations need a well-defined place to start
- Since no one size fits all this starting point must be tailored to the organization adopting it
- The process of tailoring must be done in conjunction with the people doing the work
- The process of tailoring the starting point should also teach how to do ongoing improvement
Architecture for an approach must enable content to be presented while:
- Avoiding cognitive overload
- Being sufficient
- Being extensible
- Never having the addition or subtraction of a process that is useful be grounds for saying you’re no longer doing the approach
Developers of this architecture know
- That the content is always incomplete
- We live in a complex world
- Must provide a way to get feedback on all decisions/practices as to whether it was useful, not useful or if something is missing
The general attitude follows George Box’s mantra – “all models are wrong, some are useful.”
Posted on: August 06, 2020 05:38 PM |
Permalink
Comments (3)
Please login or join to subscribe to this item
Ashleigh Kennett-Smith
ICT Project Manager| Australian Red Cross Lifeblood
Adelaide, South Australia, Australia
Very neat encapsulation Al!
I think one of the difficulties with any approach that allows change to occur to the delivery method and controls, is that we still need to provide some boundaries and controls to ensure fit for use and fit for purpose are still met. It's the "we don't care how you do it" that makes it difficult. Because we must be able demonstrate that we only release changes that truly meet requirements (including regulatory, quality, scalability, security etc)
Please Login/Register to leave a comment.
|
"Opera is where a guy gets stabbed in the back, and instead of dying, he sings."
- Robert Benchley
|
