Agile ways of working – balancing structure and flexibility
Agile ways of working are today a natural part of how many digital products are developed. At the same time, "agile" can mean very different things in different contexts. For some, it is an established everyday practice. For others, it is something they are familiar with in theory but less so in practice. At Intunio, we have worked agile for many years, often with Scrum as a foundation. It is a way of working we know well and feel confident in. Over time, we have also learned that agile works best when it is applied with an understanding of the context and the people involved, not as a rigid set of rules.
Tobias Rydenhag
Head of Design
A proven way of working that creates confidence
For us at Intunio, agile work is about having a reliable engine at the core. A way of working the team is comfortable with, and that creates stability in day-to-day collaboration.
We often work in iterations of two to three weeks, with clear roles and responsibilities. The Product Owner owns the vision and priorities, while the team plans, designs, and builds together. Daily check-ins, sprint planning, and sprint reviews are used to keep the work aligned and transparent.
For customers who are already familiar with agile work, this often feels natural. For those who are less experienced, it means being able to rely on a team that takes responsibility for structure, pace, and follow-up. The process is there and it works, without the customer having to carry it themselves.
When agile works in everyday practice
At its best, an agile way of working creates clarity, momentum, and continuous learning. Work is broken down into manageable parts, feedback is captured early, and priorities can be adjusted without the entire plan falling apart.
But agile practices serve more purposes than delivery efficiency alone. Recurring ceremonies such as daily stand-ups and retrospectives are also important spaces for collaboration. They create rhythm in everyday work, make room for dialogue, and help build relationships within the team.
In practice, these moments are often where people get to know each other better, gain insight into each other's everyday realities, and talk openly about what is working well and what feels challenging. Retrospectives become not only a way to improve the process, but also a way to build trust and shared ownership over time.
When agile does not work as intended, it is rarely because of the framework itself, but because of how it is used. When the purpose of the ceremonies is lost, they can feel like empty routines. When used with the right intention, they support both delivery and collaboration.
Structure as a prerequisite for flexibility
One important lesson from many projects is that flexibility does not emerge on its own. It requires clear boundaries.
When goals, priorities, and responsibilities are clear, it becomes much easier to handle change. New insights can be absorbed, feedback can be turned into action, and direction can be adjusted without losing momentum.
Agile work is therefore not about avoiding planning, but about planning in a way that leaves room for learning.
Adapting to the customer's reality
We always start from how an organisation works today. When there are established processes, tools, and ways of working, we adapt to them, while contributing structure and experience where needed.
At the same time, we have a well-tested base model to rely on when clarity around direction, pace, or responsibility is missing. When collaboration needs structure, we can introduce an agile setup that creates calm, predictability, and forward movement.
For customers who are less experienced with agile work, this means being in safe hands. The structure is in place, the work moves forward, and there is room to gradually become more involved in the process.
Transparency and continuous improvement
A functioning agile way of working is built on openness. It should be clear what is being prioritised, what is currently in progress, and what comes next. Tools are used to create transparency and shared understanding, not control.
Equally important is taking time to regularly reflect on the collaboration itself. What is working well. What creates friction. What could be improved. This kind of reflection applies both to the product and to how the team works together.
Agile as everyday practice, not ideology
For us at Intunio, agile is not a statement or an identity. It is a proven way of organising work in complex product and technology projects.
When it works as intended, the work feels both structured and flexible. There is a clear direction, while still allowing room to adapt as reality changes.
That balance is what we strive for in our collaborations.