Ways of Working Assessment
Understanding your situation
A typical improvement approach:
Each person or team knows their own role and situation well and uses techniques like retrospectives to identify issues and target improvements.
Where this fails:
Having a view of only part of the delivery model and often no control of what is outside of it means a focus on localised improvement. These localised improvements only get you so far.
A better approach:
Taking a step back and looking at a delivery model as a whole system helps you see weaknesses between the connected parts. This will help ensure improvements are understood in the context of the whole delivery model and global issues are tackled.
Ways of Working Assessment
A comprehensive look at your current delivery model, its issues and maturity. Followed up by improvement recommendations.
Approach
An initial 1 hour consultation is free. This gives time to explore problems, options and if you see value. You have nothing to lose by reaching out.
Model
Starting with a person who works across many stages the delivery model is mapped
Identify people who work within your delivery model
Understand
The process is then built out in more detail by interviewing people in many different roles
Problems are captured at each stage
Summarise & Score
Key findings from the interviews are presented back
You then assess your own maturity level across a number of areas
Improve
A selection of interventions is suggested based on the findings
You may chose to take these on yourself or support can be provided
Summarise & Score in detail
The maturity model consists of seven key areas. You will score your own maturity level based on:
Provided maturity criteria
Issues exposed from the Understand stage
You may then prioritise areas for improvement. The Improve stage will then start giving you a range of options.
Approach in detail
This shows the plan in detail. Before the exercise starts people are identified for the understand phase and meetings booked in. You will need to provide logistical support for this.
Interested?
If you would like to know more, please see the case study or reach out for a free discussion
FAQ
Q. What sort of roles are required?
Talking to many different people, not just managers is strongly recommended. Just discussing problems with managers often hides issues. Roles would typically include, people involved in the strategy stages, delivery managers, developers, testers.
Q. Why not get everyone in a room?
Although this is possible it does not give space and time for a deep dive into issues. It often takes time for people to think through the problems they have and draft the associated problem statements. With a fast exercise only surface level insights are gained leading to a poor result.