The transition to the Agile way of working is more than a process change. It requires a different way of interaction and behavior and a different mindset. In a large (a little less than 200 people) Agile Implementation endeavor we organized an Agile Mindset session to explain Agile principles and to push the Agile teams away from the comfort of their traditional patterns. Getting on the Agile track successfully... In a large Agile transformation assignment 11 teams started to work the Agile way less than 2 months ago. We put them on a 3-weeks iteration track, so they are now in their 3rd sprint. The teams perform amazingly well: They managed to deliver software all the way into production within the sprint, and retrospectives confirm interaction and team spirit is developing very fast. And we can tell you that was a completely different story in the ‘old’ way of working, which was very traditional, waterfall-like, silo centered and hierarchically controlled. But is it Agile? Just at the beginning of the 1-week sprint 0 the team members went through a 1-day Agile Introduction course, in which the Agile manifesto had been discussed for about an hour. During the first two sprints the daily team-coaching emphasized team cooperation, team problem solving and of course software delivery. As mentioned before, the teams did very well, but solutions to problems tended to be more on the ‘right side’ of the manifesto and less efficient than desirable from an Agile point of view. That is why we decided to expose the teams to an Agile Mindset treat in Sprint 3. The Agile Mindset session explained The setup of the Agile Mindset sessions is quite straight forward:
- What is it and why do we do it now
- We give an explanation of the 4 Agile values
- The team gets an assignment to relate team experiences to the 4 values, and
- We have a discussion on how issues should be solved with an Agile Mindset.