With 70% of business and digital transformation programmes failing to deliver, it’s time for a revolutionary approach. We addressed this in a previous post.
Incremental improvements to broken methods only don’t fix the problem, they only delay them.
Existing methods are both technology-led, and waterfall in delivery.
You need revolutionary approach. Agile Transformation.
In this post we are going to discuss HOW and WHY you need Agile Transformation, using Kanban:
- Why use Kanban for your Agile Transformation?
- Benefits of Kanban for your Agile Transformation
- How to use Kanban for your Agile Transformation?
- How to manage your Agile Transformation using Kanban?
Why use Kanban for your Agile Transformation?
Kanban is a visual workflow management tool. It helps people manage and track work as it moves through the process.
Agile and Kanban are not traditionally used for non-software or non-technology programmes— and that’s part of the problem.
All parts of the projects and programme need to be developed and delivered using the same approach – Business AND Technology.
The key to Kanban is you have to decompose the different pieces of work in a similar size. You can’t just get any process and decide ‘let’s make it Agile and manage it via Kanban’. It has to be native to the framework.
This is why we created HOBA®.
HOBA® is the only business-led Agile Business Transformation framework that develops the Business Architecture and delivers it in an Agile fashion, using Kanban.
HOBA®’s requirements, development and management follow similar principles used by the Scaled Agile Framework (SAFe)— an agile adaptive framework. We discussed this in a previous post.
Benefits of Kanban for your Agile Transformation
The benefits of managing your transformation via Kanban is as follows:
Visual Workflow Management Tool
This helps people manage and track work as it moves through the process, in HOBA®, that is the ‘Design Process.
It also helps to bringstakeholders on board and shows them their scope of work.
By visualising the work either on a digital or physical board, everyone is aware of it (the work, workload, and workflow).
Ownership and Accountability
Provides visibility of the work, and accountability that everyone needs to complete their assigned work, so the team pulls together, as a team.
It also provides the ability for everyone to be accountable for their own work, while providing autonomy to go away and ‘get it done’.
Promotes Information Sharing
Everyone on the team is aware of who owns what task, that teams work more efficiently when they are all on the same page about priority, status and progress.
Kanban ensures that people finish one piece of work, before they take up a new task, ensuring tasks are actually finished before starting a new task.
Promotes Sense of Achievement
As you constantly chip away the tasks, one at a time, it both ensures the work flows through the process but gives a sense of achievement as the team can see the work they have also accomplished.
Kanban also allows the team to identify improvements in the process and implement improvements, so the team improves incrementally through the process.
How to use Kanban for your Agile Transformation?
As mentioned above, the key to Kanban is to decompose your work into manageable chunks, of similar size.
For your Agile Transformation, the Business Architecture requirements need to be structured intentionally to support agile transformation.
The Business Architecture highest-level requirements (i.e. vision and themes) are defined at the highest level of the organisation (i.e. the portfolio). This cascades down to operational requirements and the implementation stage. We covered this is a previous post.
These programmes and projects decompose into epics and stories.
Their outcome is complete visibility and traceability from the high-level requirements to the project level.
The requirements created at their respective levels are captured, managed and reported.
In HOBA®, the Business Architecture requirements – are broken down from high level (Reference Models), to their sub and lower (detailed) level requirements (Building Blocks and Blueprints), as discussed in our previous post
Here’s a model that helps illustrates my point:
In Agile, thetheme level requirements (reference models), are broken down into epics (building blocks), features (blueprints) and user stories (user stories) as shown below:
How do you manage your Agile Transformation using Kanban?
Now that we’ve discussed the business architecture requirements, how do you manage them?
Business Architecture requires managing non-technology (or non-software) requirements on the story card.
Kanban provides you with the visibility of all the work in scope – under the three (3) columns – To Do, Doing, and Done. This is shown in the diagram below:
As the work is completed, it is moved across the three (3) columns as the work progresses and is ‘done’.
As the work is managed, and completed using Kanban, you get to reap the benefits as discussed in Benefits of Kanban for your Agile Transformation above.
For your Agile Transformation to be successful, you need to get the senior stakeholders in place.
The Kanban board will help the senior stakeholders, team and organisation get a clear idea of the scale of work that needs to be done for every level of the organisation.
Speak with your Business Architect or your Business Transformator.
They’re not just architects– they’re also strategists, designers, collaborators and negotiators.
They will help you understand the challenges of your Agile Transformation, and help you get the work ‘done’!
Thank you for reading this!
P.S. If you want to join our Business Transformator community of like-minded Business Transformators, join the community on the Business Transformator Facebook Group here.
P.P.S. If you want to learn more about business transformation, check out The Business Transformation Playbook here.
For more information, visit https://hoba.tech