Agile manifesto


It looks like a giant step into a new world. And being honest, yes it is, but step by step it is a beautiful journey. To get to the level, as they call it, Responsive Enterprise, it takes 2 or maybe 3 years. But as my favourite Chinese saying tells me: 'if you want to walk to Beijing, at one day you have to take your first steps. otherwise you will never arrive.' Within the first few months you will feel the benefits and you will not like returned to the old school way of working. Just do it.

Transition to Agile

The transition to Agile/DevOps/Scrum is a culture change.  This culture change is not that big thing for employees, The greatest step is to be made by the  management. Self-steering teams are different, It will ask for different governance. 

The great impact: better connection to the business, quality software, less incidents and teams who takes the ownership of the change.

On the left side, my all-time favourite, less than 16 minutes Scrum education. Within 16 minutes you know what will happens into the Scrum way of working. Great explanation from Henrik Kniberg.

Agile, basics, only 4 roles, thats it.

Get in mind: it don't tell you that you don't need the right site of the 4 principles. It tells you: please to think it over what you really need there. Example: how much paper do I need to change 1 line of code?

And about a plan: you need a plan, that is ok, but the plan can or will change. And you still can have deadlines.

Fail fast is a (financial) benefit.

It is better that you face a big issue after 2 or 3 sprints. Maybe this change will takes more time, and it will cost more money. Then you can reshape the model, or even make an decision to stop. In the classic world the project goes on, timelines will be unpredictable and also the cost. And only at the end you will be sure that it give you that what you thought it should be, or not.


What I like on the Scrumprocess is that the scrumguide is not more then 14 pages of plain text. available in several languages.  Please find it at

My suggestion in this is, implement scrum by the book, differensation after 1 year (take all bennefits first).

Agile way of working

First step on your move into Agile way of working is business buy in. The awareness of the business is needed to get their commitment on this route to Agile way of working. Less paper, but more control than ever before. But also daily business (Product Owner) attending at every team meeting. And change Requirements into User Stories. Fail fast (if something will not work you will see that in an early state) and prototyping are common in this new way of working. More creativity and say goodbye to time consuming PPD, PID and Project boards. Moving from Program boards into portfolio based on Epics, features and roadmaps. Architecture is enabler for the future. Yes it will impact your labour. Roles/functions will disappears, like Project Manager, PMO. functions will be impacted, like Business and System Analyst. New functions and roles will start, like Business consultants (at business side to translate business grow into User stories) and the role of integrator. You will start changing thinking in functions into roles. The teams will think in roles not in functions. Developer will be tester and analyst, analyst will be tester and developer. Functional Application Manager will take the role of Business Analyst.

No silo's in the teams, no key man risk

The outcome of the Transition

The outcome of the transition to a Agile organisation and Agile way of working:

  1. Business in the driver seat
  2. Flexibility in the market
  3. Value stream focussed
  4. Teams alignment with the business
  5. IT buy in
  6. Motivated teams
  7. Huge improvement in pace of change (up to 40% faster TTM)
  8. Less incidents (read business interruptions)
  9. Options/time for prototyping
  10. Management in a facilitating and coach focus
  11. Discussions on what documentation do we really need?
  12. No time spend on PPD/PB, PID or Project Boards
  13. Old functions like ProjectManager, PMO and Business Analyst will disappear, new functions and role will start. Like System Integrator and Business Consultant.
  14. Teams are thinking in roles instead of functions. Developers will be testers, FAMer will be testers and analyst, developers will do analyst roles as well.


Management Drives: Oranje / Geel

Copyright @ All Rights Reserved