Tags
agile, business process, business value, economic success, empowerment, highly efficient teams, kanban, Lean, resource management, scrum, scrum master
I have seen it countless times, when faced with a challenge, people, businesses, revert to old, known behaviour. It takes courage to actually stand still, investigate what is right and be brave enough to implement it.
At my current company, we have had a huge success with Agile. When the CTO made the courageous decision to hire a completely new team and a very talented Agile Coach/scrum master, and took on a new project ( with a deadline ) he knew that he was setting himself up for success. And that is what happened. Not only did he deliver in time, the product was delivered with high-quality, by a happy, self organised team.
The last sprint goal was: keep calm. And that was it. Never before had I, or any other team member been in a live release that was so calm and effective, it was almost surreal and it showed us all what Agile can do.
That, was only scratching the surface and it wasn’t even SCRUM to the letter, as with most projects, in reality, there is a balance to be found, it’s continuous improvement, it’s transition towards Agile. But even in this setting, these were some of the side effects.
The team members were actually happy, a sight that you don’t often see in a place of work. Even though countless studies have shown the immense importance of happiness on productivity, loyalty, drive and creativity.
The team had clarity and transparency, again, not 100% but the trust is there, the basis has been set and now, when there are issues or dangers, they get raised fast and we have the ability to react quickly.
The team was a team, everyone knew what they were doing and they helped each other grow.
Now… a project got thrown in with a rush, it had to be delivered in 2 weeks. No product owner, no clarity, no reason why, no agile, it just had to be done and it had to be done quick.
So what has happened? Almost every member of that team and of the other teams working on this project has come to me with frustration, anger, dis-trust in the project, dis-trust in the company and even in other team members. That well-oiled machine got a huge spanner thrown into the wheels and now it’s stuck, it’s at a risk of over heating, explosions are imminent.
So what can we do? As scrum masters, first thing we did is try and create clarity. Force people to stand still and talk to each other long enough to get at least more visibility and get things down on cards. At the same time, manage individuals to keep motivated, keep believing that this is just a spanner and once taken out, we will be running smoothly again. My co-scrum master had the brilliant idea of doing a scrum reset, the perfect time to get back to basics. Together, we set up the process to introduce bitesize scrum (scrumbites) to lead the way back to how it should be. In daily iterations we will get back to basics, diffuse the situation, get everyone motivated again and bring back a productive happy environment.
Well… as we all know, knowledge comes from experience and I think this has shown us again how far we have come through agile and it has shown us that we do not want to go back.