Agile Approaches

Time To Transform Is Now!

We are constantly bombarded with sentences about how important, relevant and urgent it is, that we change our behavior; how we run our organizations – how fast we need to deliver and how adaptive we should be. We truly need to change the “How We Change” in organizations.

Transformation projects are long term events that implement valuable, strategically important features for and with your organization. And as we do that, the way we work, innovate, create value and operate change as well. Strategies are great and visions important. But without the ability to execute and continuously rethink and change you will loose out.

Scaling Agile from IT to your entire organization

The greatest challenge lies not in the new practices put in place, but in the interface and coherence between these practices and the existing organizational processes.  With the goal to address the scalability challenge, a number of frameworks has emerged that claim to offer the much needed guidance for scaling Lean-Agile to the large-scale development efforts, where there are several development teams with digital architects, business analysts, and developers working in multi-year projects or programs. 

Most commonly known models include Disciplined Agile Delivery (DAD), Large Scale Scrum (LeSS), and SAFe:

Which Lean-Agile enterprise model is best for you?

Disciplined Agile Delivery - DAD

The key purpose of DAD is to increase overall business agility in a simple way. Arguing that every situation is unique, DAD promotes pragmatism and an approach of adopting the Agile processes to the specific needs of the company and product.

DAD offers a lot of “Bang for the Bucks” and fast deployment. Within the DAD framework, a goal-driven approach is applied to create and adapt Agile processes.

Large Scale Scrum - LeSS

Large Scale Scrum (LeSS) focuses on how to apply principles and elements of Scrum in a large-scale context without overcomplicating processes or installing unnecessary bureaucracy.

It is a ‘barely sufficient methodology’, revolving around many cross-functional, full-stack teams working together on their common goal and shared responsibility of delivering one shippable product – a complete end-to-end solution intended for real customers.

Scaled Agile Framework - SAFe

Scaled Agile Framework (SAFe) is the most comprehensive framework for adopting Agile development practices and principles at enterprise scale. It is continuously updated with new and different components, resembling a software product with versioning and backward compatibility.

The framework is used by 29% of the respondents in the Annual State of Agile Report, making it the most popular framework for Agile today.


Scrum@Scale (or Scrum at Scale) is one of the newer Agile frameworks, addressing the complexities and impediments of multiple Scrum teams working with the Scrum guide to deliver value to their customers.

The purpose of Scrum@Scale is to offer a simple and lightweight framework to scale Scrum with as little bureaucracy as possible. It is one of the least prescriptive of the scaled Agile methodologies.

A quick guide on "how to"

How can you apply agile methods in business, and not only when implementing new IT? What are the success factors in agile business transformation projects and which mistakes should you avoid? 

Forget creating the great master plan. Make progress as you use your own projects or initiatives to implement agile – but scale fast and monitor progress! We can show you how it is easily done.

Cultural changes requires focused attention, and embracing Agile and Lean methodologies requires a significant mindset shift. It goes in business projects as well as IT, and running projects on agile principles is the easiest way to introduce agile. Using metrics, automation and stronger executive agile leadership is mandatory and we know how to make that change in both small and large organisations (i.e. TeamHealth Radar).

Small, self-directed teams are central in agile projects and the “way of working”. The effect of team-work quality on team performance, learning and work satisfaction should be monitored and steadily improved.  The objective is to optimize and balance team-work-quality and velocity. This can be achieved by designing working space and leverage learning from direct experience with the help of our frameworks.

Your organization need to change. But where to start? You cannot do everything at the same time. How do you know which initiatives are the most important to start with? We create transformation maps that  communicate the vision and breakdown into Epics and Features that can be used as guidance for your organization. We provide sawy Lean Business Case templates that fit into your transformation map.  And we always focus on data-driven decision making, and guide you on how to keep that focus crisp and relevant.

It may sound daunting, but the thing is  – it is mostly liberating, exiting and utterly rewarding. Both on business but also on a personal level. Start the journey on focusing on five areas: Personal, principles, process, practice and pace. The first is the most important. You need to be or know a transformation leader within your organization, who will go all the way in leading the journey. Then the principles, or some might name it vision and purpose of what you want to strive for. We guide you through the process of that and of process, practice and pace too. 

Most are probably already in our organization, and just need the framework and some coaching to make transformation into agility happen. Sometimes different competencies are also needed and discussions about how, where and how often to meet in teams and across teams rises to the surface. Maybe you need agile coaches, scrum masters or interim product owners? Let’s discuss how you create the right set-up in your organisation.

Workspace surroundings are critical for realizing the lean-agile potential. Projects are often linked to a very specific type of office work, especially those managed by means of Agile methods. Special features of Agile Project Management, especially with respect to communication and information exchange forms, frequency and actors may make Agile Project Management office arrangements a task you need to take seriously. 

Presentation of information destined for the entire team or teams is important. While e.g. Confluence or any other shared service based solution is fine, the actual visualization on boards motivates discussions and helps clarify impediments in an informal manner. This feature can successfully be implemented by providing additional whiteboards for each team – and across teams. Each team can use two whiteboards and a large conference card, directly attached to the walls. One of the tables is used as the Sprint Backlog/Kanban Board. The second board can be used for the communication of additional information, the necessary design work and work planning – and of course during Retrospectives.

The criticality of individual and team well-being in lean-agile delivery models underpin the need for hygiene values e.g. image, culture, adaptability, health and safety, innovation and creativity, sustainability, and corporate social responsibility. 

You most certainly will be looking for identifying the most important interventions, measuring tools and KPIs. Remember less is more.

Want to know more?

You might want to know about the agile business transformation projects we’ve run, or you may want to share your experience about running agile projects and how you have been amazed by how much value you all created in a short period. Whatever the reason, just get in contact. We are happy to listen and exchange views and stories.