Enterprise Agile Adoption A New Venture

Over the past 6 months I have been working for a new company that wishes to become more Lean / Agile. It's been quite the journey so far.

In the beginning I would ask myself "What have you gotten yourself into?" Now after a lot of hard work and a little patiences I can see some change. A change in mentality for my co-works, a change in relationships with our business partners, a change in the way the company is working together. I take pride in being a change agent and I can say that if I can help mould more teams agile adoption pace will quicken.

After 6 months of working and sweating out some of the changes with my co-workers I have to say I am proud at the accomplishments my team has made. They've gone from 'doing agile' to actually practising agile scrum in a fashion most people would recognize as scrum.

Here's what I've learned along the way.

Have an agile adoption strategy

When a company goes through some organization change it's best to have a vision and plan for rolling out the change. Having a strategy in place to start, build and support agile teams as they transition is key in successful agile adoption.

Embedding an agile expert on a team

To help nurture the ceremonies and practices of agile, an expert can help by provide guidance along the way and explain some of the foreign behaviours to people brand new to this new way of working. These experts can also help bring agile awareness to the company.

Agile Maturity Model

Establish an agile maturity model to help build the behaviours and attributes of a team gives teams a insight into what they can achieve next. I also shows possible where in the organization teams may experience some bumps along the road to their next level of agile maturity. A maturity model shouldn't be set in stone. Like any other agile practice it should be review and incrementally changes has the organization matures to a high performing organization.

Visual Baseline Metrics

Having a visual baseline metrics for each agile team help keep an even level of transparency into how each team is performing. Velocity is normally the metric that you hear when talking about agile scrum but what should really be focused on in the beginning is cycle time. How long does it really take the team to transform an idea into a tangible item customers can use?

I'm looking forward to see what else I can learn over the next six months. Learning is a passion of mine and have a chance to observe as well as participate in agile adoption at a company of this size is really exciting.


comments powered by Disqus