9 years in Levi9: what changes, and what stays the same in delivery management

Nine years is a long time in technology.

Ways of working change. Technologies change. Customer expectations change. And the role of the people responsible for bringing all of that together changes with them.

For Mirjana Cussen and Vera Stojanovic, both Delivery Managers at Levi9 in Belgrade, the last 9 years have given them a front-row seat to that evolution. They joined Levi9 from very different starting points: Mirjana already had years of experience in a similar role in the UK, while Vera came from a marketing agency and started her Levi9 journey as a junior. 

Nine years later, their experiences point to something that hasn’t changed nearly as much as the technology around them: good delivery still depends on understanding people, building trust and getting close enough to the customer’s business to understand what it really needs.

Different starting points, one evolving role

When Mirjana began thinking about returning to Serbia after living in the UK, it wasn’t the Levi9 name that initially caught her attention. It was the job itself. 

“I was initially surprised to see that there was my job in Belgrade because when I left, 17 years earlier, there were no jobs like that in Belgrade.” She had already spent years doing similar work in the UK. Finding that same professional opportunity in Belgrade was what made her apply.  

Vera took a different route. She was working in a marketing agency, increasingly on IT-related projects, when a friend recommended Levi9. What she saw was an opportunity to enter the technology industry without being a developer. 

“Levi9 was one of the first companies that, I think, recognised the potential and value of the Delivery Manager role in development teams.”

Vera joined as a junior. Mirjana joined as a senior. That makes their perspective today particularly interesting: they experienced the evolution of delivery from different starting points but arrived at many of the same conclusions about what matters most. 

From Agile and SAFe to AWS: delivery keeps evolving

A lot can change in nine years. Mirjana has seen both ways of working and technology evolve, from Agile and SAFe to AWS. What stands out to her, however, is how Levi9 kept adapting as new requirements emerged. 

“We had all the training and everything that we needed in order to meet the requirements that were coming up. All the new things were always followed, and no one was ever left hanging and trying to find out. We were able to meet the requirements, however new they were.” 

But underneath all those changes, she sees one constant. 

The basics are still the same. The most important things within delivery management are the personal things, the human things: managing relationships and maintaining relationships.

Vera sees another important shift. Earlier in her career, the Delivery Manager role was much more focused on facilitation, meetings and Scrum. Now, with AI becoming part of how the industry works, she sees the role moving further towards understanding the customer’s business. 

Now with AI and, of course, with everything changing, we're changing our role. We are definitely not Scrum Masters anymore. Our role is changing towards the business of the client, to understand their business more.

That means understanding more than how development process works. For Vera, business knowledge is becoming an increasingly important part of the role, helping teams understand requirements and ultimately build better products for end users. 

“I think it will be hard for people to do the Delivery Manager role without this business knowledge and understanding.”

That growing focus on business understanding builds on something Vera says has been important from the beginning: customer focus. What is changing is the depth of that understanding. Knowing the customer and maintaining a strong relationship is no longer only about facilitating delivery. Vera sees the Delivery Manager moving closer to the customer’s business, understanding what sits behind the requirements and helping shape a better product for end users. 

Business knowledge is becoming part of good delivery

That shift from process towards business understanding is especially relevant when customer expectations, team needs and business priorities don’t neatly align. 


Mirjana is very direct about that reality: “You naturally want to support the team and you would like your team always to be right. However, they’re not always right. Nor are you as a Delivery Manager. We’re all humans.”

Her approach is to step back from personal feelings and look at what the project is trying to achieve. Sometimes that means having a difficult conversation with the team. At other times, it’s the customer’s expectations that need to be challenged.

 

“Sometimes you need to criticise the customer rather than the team, because they can have expectations which cannot be met.”

The important part, she says, is explaining why. “As long as you’re being honest and open and sharing all the logic behind the decision, that goes down well.”  

Vera looks at the same challenge through information. A Delivery Manager needs to know what’s happening on both sides: whether the team is satisfied, whether the customer is satisfied and, if not, what is behind it. 

“If I have the information, maybe I cannot solve the problem immediately, but I can work on it.“ And getting that information depends on something that can’t simply be added to a process: trust. 

As Mirjana puts it “You have to build trust with people so that people feel comfortable giving you the information, regardless of what the information is.”  

Trust takes time

For Mirjana, building that level of trust isn’t something that happens immediately. 

 

“You have to build a relationship. You have to understand the client, understand the team and everything around it. It takes a lot of time.” 

Relationships aren’t separate from delivery. They allow difficult information to surface, expectations to be discussed honestly and problems to be addressed. 


That same long-term perspective also changes how Vera and Mirjana think about milestones. 


Ask Vera what stands out from 9 years, and her answer isn’t technology or a particular delivery framework. It’s seeing what happens to people over time. She remembers colleagues arriving as interns and juniors and later becoming leads and architects. 

 

“To see how people are professionally and personally growing within the company is really awesome. And if you can be part of it, you feel that you are also part of that growth.”  

Mirjana immediately recognised the feeling. She remembers working with a colleague who started as a junior and whom she later saw become a team lead and be selected as Tech Leader of the Quarter. 

“I’ve been with him through good and bad and through everything, and to see how he has grown just makes me feel really proud.” 

What delivery looks like when the stakes are real

Long-running projects give another perspective on what changes over time. 

Mirjana points to one project that she has seen develop over six years. It started as a small application for the Dutch market and developed into an application shared with Volkswagen Pon Financial Services for the European market, bringing more countries, more people and new challenges into the picture.  
What she remembers isn’t only the growth. “Through all the challenges they have been through, the budgeting challenges especially, where the team had to be reduced, they have still remained positive and really good.”

Another project, Lucky 13 with Talpa, created a completely different kind of pressure because it followed a live television programme. The deadline wasn’t something the team could simply move. “The show is at 8 PM on the telly and you have to be ready. There was no excuse. The overtime, the dedication, the working over the weekend, the team at the time were really great.” 

Different projects bring different pressures. What connects Mirjana’s examples is the team response when circumstances became difficult. 

Nine years later, the constant is still people

Neither Vera nor Mirjana describe delivery as a frictionless job. Mirjana is particularly candid: “Sometimes it can be stressful and difficult, but that’s part of the job.” 

And yet, when Vera looks back at what has mattered across her nine years at Levi9, she comes back to the same thing that runs through much of their conversation: 

“People that we are surrounded by are the biggest value that I see in working at Levi9 for all these years.”

Agile, SAFe, AWS, customer expectations and the delivery role itself have all been part of the change they have experienced. But the foundation they describe is much less technical: understanding the business, being honest when expectations don’t match reality, building relationships and creating enough trust for people to tell you what you need to know. 

After 9 years in delivery, perhaps that’s the part worth holding on to. 
In this article:
9 logo
Written by:
Levi9
Published:
4 November 2026

Related posts

June 26th

The Cost of Choice

Most companies spend up to 40% to much on cloud, are you? Cut spend, not options. Smart standardizations win.

Cloud cost overruns and growing technical debt rarely stem from tooling alone—they are symptoms of architectural and operational choices. This session looks at how senior technical leaders can regain control by connecting cloud spend directly to business value. We’ll explore unit‑economics thinking, ownership models, and lifecycle management practices that reduce waste while preserving delivery speed. You’ll learn how to combine FinOps principles with technical‑debt controls to create a cloud environment that is financially sustainable and technically healthy.

May 28th

AI AGENTS DESERVE AI PLATFORM

Portable patterns for Azure, AWS and GCP that survive the next upgrade

AI agents are moving rapidly from experimentation into real production use cases, but architectures vary widely across cloud platforms. In this webinar, we compare practical patterns for building and running AI agents on Azure, AWS, and Google Cloud Platform. We’ll focus on what to standardize, where to embrace cloud‑native capabilities, and how to design for security, observability, and future change. The goal is not to pick a winner, but to help leaders understand how to scale agent‑based solutions without locking themselves into fragile designs.

April 23rd

Winning on Repeat: Product Engineering in the Age of AI

Cadence, quality and outcomes over output

Delivering a successful solution once is no longer enough. In the age of AI, organizations need product engineering models that enable them to win consistently across teams, releases, and markets. This session explores how leading organizations evolve from project‑centric delivery to product‑centric execution, supported by AI‑augmented engineering practices. We’ll look at cadence, quality, and accountability, and how leadership decisions shape sustainable delivery performance over time.

April 2nd

GOVERNING AI IN PRODUCTION

Designing cloud and data platforms that survive real-world pressure

Many organizations succeed in building AI proofs of concept, far fewer succeed in scaling them safely into production. This webinar focuses on what it takes to move from experimentation to reliable, governed AI platforms. We’ll discuss platform architecture choices, model governance, security, and policy patterns that enable teams to deploy AI at scale without slowing down delivery. Designed for senior technical leaders, this session provides practical guidance on turning AI initiatives into durable capabilities that deliver value beyond the first demo

March 5th

Navigating Digital Sovereignty and Strategic Cloud Choices

How Organizations Can Balance Innovation, Compliance, and Control in a Multi-Cloud World

In today’s rapidly evolving digital landscape, organisations face increasing pressure to ensure business continuity, maintain public trust, and comply with complex regulations like NIS2, DORA, and GDPR. This webinar explores the critical concepts of digital and operational sovereignty, the strategic importance of hybrid and sovereign cloud models, and the risks of vendor lock-in.