Being Agile does not mean following a specific framework to the letter. It is more about how to adress problems, how to collaborate and how to implement change.
In another post I have written about agile vs. Agile, in this post I want to highlight the Agile mindset.
* Problems are adressed with curiousity and as opportunities to make change. Change is positive and continous. Solving problems is a stepwise exercise where you size workload in each iteration depending on the capacity you have. After each iteration the output is evaluated and based on result the next step is planned. This means that you probably never come to a fixed solution …
* Collaboration is impled. Not if, but when issues appear they should be brought to the attention of all in a transparent way. This is not to put blame on indivuduals/groups but to drive learning and gaining experience. It is ok to fail, you should fail occasionally to learn and progress. Youd should not make the same mistake twice though…
* Implementation of change is a continous exercise with a regular cadence. Stakeholders and implementors are in the same team, there is nowhere to hide. Stakeholders work on detailing the problem at hand by clarifying the problem statement, iteration by iteration by evaluating the output, comparing to objectives and updating problem statement. Implementors update the working code adding their expertise and experience iteration by iteration and work together with stakeholders on what is possible.
