Case Study

Greater Predictability. Stronger Partnerships.

A case study of a software house and Meirik

Paweł Feliński

Stronger client partnerships, greater delivery predictability and streamlined processes do not begin with the implementation of a new framework. They begin when an organisation asks itself a simple question: are we truly working towards value?

At a Polish software house specialising in the design and development of mobile applications and comprehensive digital product development for clients worldwide, the impulse for change was not a desire to “move from projects to products” as an end in itself. The goal was more concrete: better management of internal processes, greater delivery predictability – for both teams and clients – and the development of more genuine partnerships built on transparency and business-focused conversations.

At the beginning of 2023, the company initiated a series of organisational changes aimed at increasing transparency, introducing a set of KPIs and establishing client-facing roadmaps. In this context, Scrum Masters played a pivotal role. Formally,they operated within the Scrum framework. In practice, however, theirresponsibilities were significantly broader. They effectively acted as deliverymanagers: ensuring clarity, managing client communication, supporting predictability and safeguarding process stability. Expectations, therefore, extended well beyond facilitating meetings.

From “metrics training” to diagnosing real needs

In response to these challenges, the software house turned to Meirik – a management consulting firm that supports organisations in delivering change through the systematic development of internal capability, rather than through one-off training interventions.

The initial signal was a perceived need to work better with metrics. However, before designing any development programme, Meirik conducted a training needs analysis. Conversations with the team and the wider organisation clarified that the challenge was not simply about tools.

At the core lay confidence in client relationships – the ability to conduct conversations about business goals, metrics, accountability and predictability in a structured, data-informed and partnership-oriented manner.

“We were looking for training for the whole team. We mapped the competencies we were missing and started searching. Meirik was the only company to propose a customised learning pathway,” said the Leader of the Scrum Master team.

From the general ambition of “we want to measure better” emerged a programme designed to strengthen the Scrum Master’s role as a partner in conversations about value and delivery predictability.

Scale of investment: deliberate, not excessive

Ayear-long programme was agreed, covering all Scrum Masters in the organisation and, in selected modules, Business Analysts and the Head of Delivery.

Thestructure was intentionally straightforward:

·    three proprietary training courses (16hours each),

·    three Action Learning sessions (3 hours each),

·    three Coaching Circle sessions (1.5 hours each).

This was not a multi-year transformation nor an expensive certification scheme. It comprised three training courses and six supporting sessions, designed as a coherent whole and spread over time to allow for real implementation between stages.

The key factor was not “how much”, but “how”. The investment was relatively modest, yet precisely targeted at building specific competencies and applying them in practice.

Building capability: value, process, relationship

The programme followed a clear developmental logic.

Th efirst training focused on measuring value. Participants worked on understandingbusiness goals, the distinction between output and outcome, and, crucially, how clients can make meaningful business decisions based on relevant indicators – andhow Scrum Masters can support that process.

The second training addressed process and flow metrics – in essence, the organisation’s capability to deliver value. Participants explored visualisation, data analysis and predictability. The objective was not measurement for its own sake, but answering concrete questions: where are we? when will it be delivered? what affects delivery stability? Although most teamsoperated within Scrum, Meirik’s trainers were not confined to a singleframework and presented practices proven across multiple approaches.

The third training focused on coaching and working with clients. Here, knowledge ofmetrics became integrated with the capability to lead effective conversations. Participants commented:

“Everyone was emotionally engaged”, “We could try itout in a real-life context… it was a real wow moment.”

An important element of the development process was the workshop sessions with a mentor between formal training modules. During Action Learning sessions, participants brought real project cases, analysing and resolving them together whileapplying newly acquired skills. Coaching Circle sessions strengthened their coaching capability in a safe environment, yet centred on genuine objectivesand challenges. As a result, tools transitioned rapidly from theory intopractice.

Confronting market realities

Implementing a value-based approach revealed that some challenges lay on the client side.Not every client has a clearly defined product vision or agreed success metrics.

“How are we supposed to measure a product if there is no clear product idea?”asked one Business Analyst.

The programme did not eliminate such situations. However, it provided the team with greater confidence and a shared language for conducting structured, partnership-oriented conversations with stakeholders.

 “The training wasn’t meant to guarantee that this would happen. It was meant to give us the knowledge to make it happen – that was our step,” summarised the Head of Delivery.

Outcomes: what changed for the organisation and its clients

Even during the programme, participants reported changes in their behaviour whenworking with clients. “Client conversations are conducted differently now”,“We’ve really started focusing on transparency.”

After completion, changes were visible not only at an individual level, but organisationally.

Within the Scrum Master team, systematic process visualisation and analysis werere instated. Projects became more transparent, and client conversations moredata-driven.

“Projects used to fall apart without visualisation. Now we measure, and we have evidenceto show,” said a Scrum Master.

Consistency of approach increased across the team. A shared language around value, metrics and accountability emerged

Within product teams, transparency of progress and budget improved, along with awareness of business objectives. Scrum Masters more frequently initiated conversations about the rationale behind decisions and clarified expectations of client-side Product Owners.

Relationship salso evolved. Conversations became more partnership-based, less reactive andmore grounded in questions and data.

For the organisation, this meant greater consistency in ways of working and a stronger, more equal footing in discussions with clients. For clients, it meant increased predictability, clearer insight into progress and more mature collaboration.

The change was qualitative, not merely procedural.

Impact: greater than the scale of investment

Participant ratings ranged from 8/10 to 10/10. The most frequently mentioned words were: awareness, confidence, transparency, and partnership. The programme strengthened their role not only as process custodians, but as stewards of client relationships and delivery transparency.

 Most importantly, a relatively modest investment – three training courses and six supporting sessions – resulted in change felt at both organisational level and in client relationships.

This was not a structural transformation nor the implementation of a new framework.It was a shift in mindset, measurement and conversation. Such a change does not always require multi-million-pound budgets. It requires a well-designed intervention grounded in a clear needs diagnosis, a coherent developmental logic and consistent transfer of learning into practice – and a trusted partner who knows how to deliver it.

Business improvement does not begin with a tool. It begins with the decision to work more consciously on value, predictability and client relationships.

Inthis case, that combination – precise diagnosis, a coherent programme and practical implementation – enabled capability development to translate into tangible business outcomes.

Got questions?

This is some text inside of a div block.