We are all familiar with the final version of the Agile Manifesto

However, have you seen the draft version before it was published ? Looks like they had divisions like the one below. I like this version below which is easier to grasp. What about you ? Which version do you like and why ? Send me a message :-)

Came across this article where the author envisages AI roles of the future. A few examples below, but read the above article for the

🔹 Chief AI Officer: Leads AI strategy and oversight.

🔹 Head of AI: Directs AI initiatives and teams.

🔹 AI Architect: Designs scalable AI system architecture.

🔹 AI Product Manager: Manages the AI product development lifecycle.

🔹 AI Risk & Governance Specialist: Ensures AI compliance and risk management.

🔹 AI Ethicist: Addresses ethical implications of AI.

🔹 Model Manager: Oversees the AI model lifecycle.

🔹 Model Validator: Verifies AI model accuracy and reliability.

🔹 AI Developer: Builds and implements Gen AI & Agentic systems.

🔹 Model/ML Engineer: Develops and deploys machine learning models.

🔹 AI Application Developer: Integrates AI into business applications.

🔹 AI App Dev Platform Architect: Designs AI development platform infrastructure.

🔹 AI Cybersecurity Analyst: Mitigates AI-specific cybersecurity risks.

Here is the section from the “Practices of Scaling Lean and Agile Development” Book. This paragraph is packed with wealth of knowlege

Planning large-scale agile development is simpler than traditional approaches—or at least should be. We notice that this simplicity is disconcerting for some, because the traditional paradigm of management is that big complex work needs big complex planning and control by project managers.

But there is a different way: the emergence of order from self-organizing Scrum feature teams. Top-down planning and control is not particularly effective in systems with variability and discovery—because the plans assume something relatively static or deterministic—and the approach grows even less effective as these non-linear systems grow larger.

Complex systems on the boundary of chaos and order (chaordic systems [Hock99])—and that includes big development groups—cannot be truly planned or controlled from above. No false dichotomy regarding “no planning” versus “top-down planning” …

In Scrum, the group does start by creating a Release Backlog for a future goal, identifying and estimating the product features. But after that starting point, agile planning emphasizes continual learning and adapting.

How to do that within a large chaordic system?
By
(1) encouraging self-organization and bottom-up emergence of order,

(2) increasing transparency and feedback, and

(3) making it easy to frequently inspect and adapt.

This is precisely what agile approaches such as Scrum offer. Consequently—in contrast to those that assumed agile development was for small groups—agile planning is especially use ful for the large scale.

We have heard of Systems Thinking, Design Thinking, Critical Thinking… but did you know that there are 20 most popular ones.

Cambridge university press has the detailed list of these 20 thinking approaches with detailed analysis. If you have the habit of reading, this is a treasure.

Copyright (C) 2025 The Empirical Coach Pty Ltd. All rights reserved.
You are receiving this email because you have opted during one of the LeSS events or requested in relation with any of the trainings conducted by the Empirical Coacht Pty ltd

Our mailing address is:
The Empirical Coach Pty Ltd
High Street Road
Glen Waverley, VIC 3150
Australia