Continuum, our Methodology for team improvement.
How awesome would it be to have a team of master IT ninjas at your beckon call?
Well, what if we tell you there is a strong chance that you already have an army of master ninjas, just a few feet away from your desk, right now.
Brain Leke Betechuoh, from Standard Bank, presented how they are currently working on identifying and continuously improving current team skills. They are not looking at individual assessments, but team assessments.
They do this through a very innovative in-house MVP application, called Continuum.
Continuum currently tries to understand and improve their current practices and capabilities. It also tries to increase team’s ability to respond to changing business conditions. This, they believe, will help them to better leverage innovation.
Brian broke down the end-user’s journey into three phases of evolution and emphasised that they also layered specific skill dimensions on top of the various maturity stages.
- Traveller – start delivering software with quality and pace.
- Artisan – starting to improve ourselves.
- Expert – achieved a level of consistency.
- Professional – Getting things done
- Master – how do I continually stay here?
A team’s skills, the priority of which is set by the team itself, and its maturity state is relative to the governance of the organisation. Brian also emphasised the fact that you should set your target maturity stage based on a realistic view of what is achievable in a specified time frame
A live demo of their current MVP (version 1), that takes the model and puts it into a self-assessment application. There was a lot of interest from the audience in terms of how the tool is used. How often are teamed self-assessing, how quickly does a team move from traveller to master?
The MVP application currently has the ability to suggest a start and stop behaviours for that maturity level. It can also export from Excel and import into Jira. The app also creates a trend over time base on a history of assessments.
It is important to note that this approach should not replace retrospectives in teams and is purely meant to improve team skills – in a cool and innovative way.
Was this blog post helpful? Don’t you think your buddies would like to know more about what was learnt at Africa DevOps Day 2017? Please share on Twitter, Facebook & LinkedIn.