Project Management

What I've found a team approach to Agile must include

From the Manifesting Business Agility Blog
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.

About this Blog


Recent Posts

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

What I've found a team approach to Agile must include

A shift in my efforts

This is a rough draft, but looking for what I left out.
Having done Agile at the team level for 22 years, I have come to the conclusion that the following are extremely helpful and should be included in any approach. An approach that misses any of these concepts leaves the team with more work on their part to figure out.
1. Provides objectives to be achieved- when practices are provided, they are done within the context of these objectives
2. Provide the why for the objectives and suggested practices
3. Use double loop learning must be done on a
frequent basis to question all objectives and practices. Nothing is sacrosanct.
4. Has a positive attitude towards management. If they are not cooperating ask what they are not seeing and then provide that to them.
5. Design for incompleteness. No system is complete, but approaches should provide guidance on how to fill in the blanks
6. Attend to the factors for simplicity (e.g., value, batch size, efficiency of value stream, visibility, workload, # of interruptions, rate of feedback, quality, value creation structure)
7.Provide guidance for when cross-functional teams don’t exist or are not achievable, and when iterations are not appropriate
8. Provide insights on how to start with a fit for purpose solution
9. Use these insights to also guide improvement on an ongoing basis
10. The approach must be designed so that no useful practice is outside of its scope (this doesn't mean its included, it means doing it won't take you out of the approach)
11. The amount time to get people started should be relatively short. Either a couple of days if delivered as a workshop but also deliverable by an internal coach over time.
12. Provide a navigable list of practices to choose from so people aren’t required to invent their own
13. Provide a way to learn and improve practices on a continual basis.
 14. Include a way of specifying what should be built next and what capabilities are required to build it

When we talk about “simple” we must keep in mind we are more concerned with “simple to use well” than with “simple in design.” Think of a self-driving car.

Note: Disciplined Agile Scrum achieves all of these. For those of you doing Scrum Guide Scrum I'll let you decide how many it provides.

Posted on: September 03, 2021 11:57 AM | Permalink

Comments (2)

Please login or join to subscribe to this item
Hi Al-
Thank you for expanding the scope of learning on the Agile methodology. Best practices are always helpful to make project objectives achievable.

Please Login/Register to leave a comment.


I have an existential map; it has 'you are here' written all over it.

- Steven Wright