Agile systems dynamic model

Here is an illustration of an Agile Systems Dynamic Model by Pierre E. NEIS. More on it in his blog.

The iteration in the model is of any size, biweekly Scrum sprints, quarterly project stages, or annual PMO assessment cycles.

In understanding the model, less attention should be paid to a system’s cause/effect (the original Cynefin theme) and more attention should be paid to agents, agents’ interaction and their objectives.

Obvious. Find an objective (or objectives) for the agents. These objectives need *not* be shared (Scrum team members, project board members, and PMO stakeholders will have conflicting priorities, varying demands on end-stage deliveries, and different appreciation of benefits).

Chaos. Work out some means to proceed. Perhaps borrow from your familiarity with the obvious (the best practice).

Complex. The agents carry out the work.

Complicated. Sit and reflect in a retrospective session, review an end-stage report, or check a PMO balanced scorecard. Whatever you learn will make some of the obscure obvious.

In conclusion, if you aren’t comfortable with the obvious, you won’t be able to find your way back to it.

#AgileGothenburg #Agile #AgileSystemsDynamic #Scrum #ProjectManagement #PMO #Cynefin