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:
-
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.
-
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.
-
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.
-
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.
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Navigating Agile Transformation: Empowering Teams for Success in a Rapidly Changing Landscape
Explores effective Agile transformation by empowering teams, improving collaboration, focusing on value delivery, and fostering continuous …
Mastering Scrum: Essential Insights for New Teams from a Scrum Master's Journey
Guidance for new Scrum teams on building strong foundations, embracing empiricism, Scrum values, continuous learning, and the Scrum Master's …
Unlocking the True Power of Agile: Embracing Change and Collaboration for Team Success
Explores how Agile success relies on team collaboration, embracing change, continuous improvement, and focusing on delivering real value to …
Mastering Agility: Balancing Engineering Excellence and Effective Processes in a Rapidly Changing Business Landscape
Explores how to balance engineering excellence and effective Agile processes, highlighting the need for technical skills, continuous …
From Developer to Agile Advocate: How My Journey Unveiled the Power of Scrum and DevOps
A personal account of moving from traditional project management to Agile, highlighting lessons learned with Scrum and DevOps to improve …
I do continuous deliver, why should I Sprint?
Explains why Sprints are valuable even with continuous delivery, highlighting benefits for planning, feedback, communication, and …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Kendall Guide - A System of Work for AI Adoption
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster
Stop confusing acceptance criteria with definition of done, learn the crucial difference to boost quality, speed, and trust in your agile …
How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum
Unlock a smarter Definition of Done, start small, evolve standards, and build team momentum without overwhelm. Discover how progress drives …
Why Most Transformations Fail Without Honest Conversations
Most transformations fail without open, honest conversations that address real issues, making transparency and tough dialogue essential for …
Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth
Transform your definition of done into a strategic advantage, deliver real value, reduce risk, and drive business impact with every sprint.
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Why Big Bang Rewrites Fail: How Sustainable Change and Engineering Excellence Transform Legacy Systems
Ditch the Big Bang rewrite. Discover why sustainable, in-place change drives true engineering excellence and lasting transformation in your …
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
Telling People What to Do Is Not Leadership. It’s a Failure of System Design
Explores why real leadership means designing systems that enable team autonomy, flow, and accountability, rather than relying on …
From Legacy Pain to Modern DevOps: My Proven Roadmap for Real Engineering Transformation
Transform legacy engineering with a proven, step-by-step approach, learn how to automate, adapt, and build a resilient, modern DevOps …