Transform Your Scrum Team in 90 Days: Strategies for Continuous Delivery and Empowerment

Published on
3 minute read

When I embark on the journey of working with a new Scrum team, I often find myself reflecting on what I hope to achieve within the first 90 days. In my experience, this timeframe is typically sufficient to make significant strides, but it’s essential to consider the context in which the team operates.

Understanding the Landscape

The starting point for any Scrum team can vary dramatically based on their organisational environment. Here are a few factors that can influence the journey:

  • Organisational Support: If the organisation is open and receptive, the potential for transformation is immense. Conversely, limited support can create constraints that hinder progress.
  • Team Readiness: The existing knowledge and experience of the team play a crucial role. Are they familiar with Agile principles, or are they starting from scratch?

The 90-Day Transformation

Assuming we have a supportive environment, my goal is to take the team from a state of minimal delivery capability to a position of continuous delivery within those 90 days. Here’s how I envision this transformation:

  1. Establish Continuous Delivery: By the end of the 90 days, the team should be able to deliver a usable product to production at the end of every Sprint. This shift is not just about engineering practices; it’s about embedding a culture of delivery.

  2. Clarify Value: It’s vital for the Product Owner to have a clear understanding of what value means for the business. This understanding allows for rational conversations about prioritisation and helps create an ordered backlog that aligns with organisational goals.

  3. Integrate Feedback Loops: Closing the feedback loop is essential. The team should be equipped to collect telemetry, engage with users, and validate whether they are indeed building the right product. This iterative learning process is crucial for refining both the product and the approach.

  4. Empower Champions: Throughout this journey, I aim to identify individuals within the organisation who can champion this new way of working. Ideally, by the end of the 90 days, the entire team should feel empowered to take ownership of the process.

The Path Forward

Once we reach this milestone, my role shifts. I want to step back and allow the team to flourish independently. They should have developed a unique organisational structure that fits their needs, enabling them to continue their Agile journey without my constant oversight.

Of course, I remain available for coaching, answering questions, and providing support as needed. However, the ultimate goal is for the team to feel confident in their ability to navigate challenges and drive their work forward.

Conclusion

In summary, the first 90 days with a new Scrum team can be transformative if approached with the right mindset and strategies. By focusing on continuous delivery, clarifying value, integrating feedback, and empowering champions, we can set the stage for long-term success.

If you found this insight helpful, I encourage you to engage with me further. Whether you have questions about Agile, Scrum, or DevOps, or simply want to chat over a coffee, feel free to reach out through Naked Agility. Your journey towards agility is just beginning, and I’m here to support you every step of the way.

Hmm, that’s a good one. What would I hope to achieve with a new Scrum team in the first 90 days? Uh, 90 days should be enough for everything. That’s my view.

It depends on where the team is and where their organisation is and what the organisational constraints are going to be, because I’m sure there’s organisations I’ve gone in to help teams with where there is very limited support from the rest of the organisation, and then you’re working within that bounded box, right? You can poke at it, but you get limited ability to do that.

But if you have an open, receptive organisation, an open, receptive leadership within the organisation, you should be able to take them from zero to a hundred in 90 days, right? They should be able to go from barely able to deliver a working product or not delivering a working product at the end of every Sprint to continuous delivery in that time. That should be where you want to get them at the end of that 90 days.

They are able to continuously deliver a usable working product to production, separating out the ideas of release, which is a business idea, and delivery, which is an engineering practice, and enable the Product Owner to better represent the value, right? The business now has an understanding of what value is for them, right? Because that’s different for every organisation.

What value means to them so that you can then have rational conversations with them about what things are more important than other things and why, so that you have an ordered backlog, a direction, a goal, right? What is it we’re trying to achieve together? And that then informs that release side, right? What are we actually going to ship?

You’ve got that engineering side with the continuous delivery of value to production, right? Continuously delivered to production, and then you mesh that together, then closing the feedback loop, right? With learning. So are you then able to collect telemetry and talk to users and figure out whether you’re actually building the right thing or the business value idea is actually correct?

Have you validated them and then close that feedback loop all the way around to change what it is we’re working on based on those things that we learned? That’s kind of the minimum that I would expect to get to in 90 days.

And then hopefully within those 90 days, I found somebody within that organisation who is able to be the champion for this process, or everyone being the champion for this process, this new way of working going forward, so that at the end of 90 days, right, I can back off.

Let them get on with it, right? They’ve built their unique organisational structure, right, that fits them like a glove, that they’re then able to take forward and use. And then perhaps be available to help tweak, coach, answer questions, and be available after that. But ultimately, it’s their problem to solve; it’s their work to do.

If we can get them to a certain place in the first 90 days that they understand it, then they should be able to take it from there.

Thanks for watching the video. If you enjoyed it, please like, follow, and subscribe. I always reply to comments, and if you want to have a chat about this or anything else Agile, Scrum, or DevOps, then please book a coffee with me through Naked Agility.

Scrum Product Development Value Delivery Continuous Delivery Product Delivery Scrum Team Team Performance Self Organisation Organisational Agility Working Software Team Collaboration

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Emerson Process Management Logo
Teleplan Logo
Philips Logo
Kongsberg Maritime Logo
Bistech Logo
Workday Logo
DFDS Logo
Healthgrades Logo
Slaughter and May Logo
Lean SA Logo
Microsoft Logo
MacDonald Humfrey (Automation) Ltd. Logo
Big Data for Humans Logo
Alignment Healthcare Logo
Hubtel Ghana Logo
Genus Breeding Ltd Logo
Capita Secure Information Solutions Ltd Logo
Flowmaster (a Mentor Graphics Company) Logo
New Hampshire Supreme Court Logo
Royal Air Force Logo
Nottingham County Council Logo
Ghana Police Service Logo
Washington Department of Enterprise Services Logo
Department of Work and Pensions (UK) Logo
Illumina Logo
Epic Games Logo
Qualco Logo
Higher Education Statistics Agency Logo
Sage Logo
Lockheed Martin Logo