The results of introducing Agile at scale: WIP down by >30%, team confidence up by >20%
Does Agile at scale really work? How do you quantify the improvements? How long does it take? Come to this session to understand the key elements of the first year of implementing Agile at scale in Australia's largest wagering and gaming company: Tabcorp.
With a growing pipeline, reduced budget, frozen headcount and Australia's largest merger on the horizon, a perfect storm was set to rage unless we adopted Agile at scale to prioritise the delivery of work in our largest portfolio of 350+ people, and implemented ways of working that enabled the Business and IT stakeholders to collaborate continuously through delivery.
During this session we reveal the fundamental elements to a successful deliver transformation that reduced WIP by >30%, increased delivery team confidence by >20% over a 12 month period, lead to unexpected examples of Business value being delivered, and what elements you need in place to achieve the same (or better!) results. For example:
- how do you make $20 million of in-flight work visible?
- how do 350 people collectively plan their work? (including Business and IT stakeholders)
- how do you convince people the LESS work-in-progress leads to MORE productivity?
- how Big Room Planning pays for itself: the unexpected Business Value we delivered from real time collaboration
The session shares real data and photographs from the transformation to bring you inside the journey, and concludes with take away actions for companies ready to step forward and adopt Agile at scale.
Outline/Structure of the Case Study
The session will follow the structure below:
5 mins - introduction and context
5 mins - describing the problem statement: what was wrong with the status quo
5 mins: solution 1 - how we made our portfolio visible to 350+ Business and IT stakeholders
5 mins: solution 2 - how we continuously collaborated (Business and IT) to plan and deliver $20 million of in-flight work
5 mins: solution 3 - how we built trust and increased teams' delivery confidence by >20%
5 mins: behind the scenes - what else needs to be in place for scaled Agile to succeed?
5 mins: takeaway actions - what can you take back to your organisation
5 mins: Q&A
(5 mins buffer)
Learning Outcome
People who attend this session will achieve the following learning outcomes:
* understand key elements of scaled Agile, and how to apply these
* understand the benefits of embedding scaled Agile across large portfolios
* understand takeaway actions to get started with implementing scaled Agile in their own organisation.
Target Audience
CIO, VPs, General Managers, Portfolio Managers, Business stakeholders
Prerequisites for Attendees
Participants should understand the basics of Scrum and Agile.
Video
Links
An earlier version of this talk was delivered at Agile New Zealand 2017 (November), which will be updated for Agile India 2019.
N.B.: The slides appear to be word-heavy, but are mostly conversation-driven. The words are mostly showed after each picture is discussed, and as a memory jogger for people who attended the session.
schedule Submitted 4 years ago
People who liked this proposal, also liked:
-
keyboard_arrow_downSuzanne Nottage - GO WITH THE FLOW: Your Scrum team is interrupted 2,000 times per Sprint. Let's get our teams' 'flow' back.
45 Mins
Talk
Intermediate
This talk is for people who care about their Scrum teams, and how to tackle one of the most insidious threats to our team's productivity: the tyranny of interruptions.
In 45 minutes you'll learn why interruptions are endemic in some organisations (but not others), how disruptive they are to teams (it can take 15 minutes to re-focus after each interruption), how the impact productivity and team happiness, and several secrets from mature Scrum teams for reducing interruptions for individuals and teams.
My talks are always interactive and this talk includes a short, fun game to demonstrate how destructive the context switching from handling frequent interruptions is to our productivity. It's simple enough you can play it back in your company after the conference.
The context for this talk is described below.
The average IT worker is interrupted every 15 minutes, which equates to 2000+ interruptions for a Scrum team every sprint. This is "death by 1000 paper cuts for your teams' productivity." Unthinkable on a production line, yet too often the norm in offices.
Ask the Scrum teams around you whether they regularly deliver their committed work per Sprint and you'll find that most teams (very) seldom complete their planned work in a sprint, let alone two consecutive Sprints.
The material for the talk is distilled from original research I conducted with Scrum teams in Australia last year as part of my Master of Management thesis (and achieved an A), to understand the causes, patterns and impacts of these interruptions on the team's effectiveness and their happiness. And, how mature teams control interruptions rather than let themselves be controlled by interruptions.
I selected teams in Australia because the culture is relatively open to discussing challenges and is willing to experiment with new ways of working: hierarchy and tradition are arguably less influential than in some other cultures. (For the record, I'm not Australian...I'm a New Zealander and British, with experience working in the US and Australia as well.)
I delivered this talk the LAST Conference (July 2018, Melbourne, Australia) to a full room and it received one of the highest feedback scores from attendees at the Conference because the topic is so relevant to contemporary teams.
My talks are always highly practical and I provide 3 takeaway actions for people and teams to improve their 'flow' and reduce interruptions.
Please vote for my topic if you would like to help your teams optimise their performance and increase their happiness by reducing interruptions. Thank you.
~ Suzanne Nottage
-
Recent Activities
Call for Proposals CLOSED
Ended on Nov 15 '18 11:00 PM IST
All proposals will be public. Registered user of the submission system will be able to comment on your proposal. You are required to reply to those comments to provide clarifications, explain revisions and respond to questions. The program team will look at how well you've responded to comments and updated your proposal to incorporate public suggestions. Ultimately the decision to accept a session resides with the program team.
Your proposal stands the best chance to be selected, if it's unique, fully flushed, ready-to-go. Please ensure you've read:
To encourage early submissions and iterative improvement of proposals, we'll start accepting proposals as soon as we find them a good fit. As time passes by, the competition gets tougher. So don't wait till the last date to submit your proposal.
Tathagat Varma
Anand Bagmar
Vivek Ganesan
Jeremy Kriegel
Alhad Akole
