Your SlideShare is downloading. ×
Adopting Leffingwell's Scaled Agile Framework, the Theory and the Practice
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Adopting Leffingwell's Scaled Agile Framework, the Theory and the Practice

4,986
views

Published on

Case study on Telstra adopting Dean Leffingwell's Scaled Agile Framework

Case study on Telstra adopting Dean Leffingwell's Scaled Agile Framework

Published in: Technology, Business

0 Comments
13 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
4,986
On Slideshare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
415
Comments
0
Likes
13
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • About UsEm was business person, now leads the EDW delivery teamMark was my coachMark...
  • We started with one pilot project in Feb 2011By October/November we had 5 Agile Teams and 4 projects in flightWe had proven we could deliver more with Agile but we still weren’t getting the type of results we needed to be successful
  • I went to Bali on my Xmas holidays.My coach sent me with a reading list, specifically Dean Leffingwell’s scaling software AgilitySat in pool and read bookMessaged Mark “I want a Release Train”As luck would have it, 8 weeks later, I was asked to lead the newly formed EDW Delivery organisation
  • Today...
  • Mark
  • Mark - What is the ART
  • Mark – what is an agile release train
  • Mark – What’s in your backlog
  • Mark – how does Dean’s recommend you start
  • Em4 workshops over a couple of weeksA one hour deck from Mark, based on Leading SAFe
  • Em – how we chose to structureIn the beginning – Pipeline, Dev & Dep SERVICESPlus – Project management for in flight outsourced projectsLater we added the specialist chapters and loco – more on that later
  • EmKanban wall, represents the value streamEvery project is an EPIC, and every card represents an EPICEvery EPIC is on the wall, including outsourced projectsSwim lanes represent teams (Teams have train names)
  • Mark
  • Mark
  • Em -Having established the org and the program wall it was time to start planning for our first PSI eventIt was the end of the financial year and we only had a very short pipelineWe originally decided on a PSI lite – one day every four weeksIn the end could not build even a four week backlogRetro – what would we miss – UnityEm – So Unity Day was born as an opportunity for the whole team to spend time together‘At this time, there were 100 people in the group and we didn't know everybodys namesEmUnity Day is the first hour of every iterationThe agenda changes from iteration to iterationGenerally we try to cover, topics like architectural runway, upcoming releases and customer contextIn the beginning there was a big focus on team building and we spent over half of every session on Agile Learning activitiesUnity Day is also used for our Innovation ChallengeToday the session are organised by the team.
  • EmServant LeadershipLearning culture, book clubsContinuous improvementSpecialist chapters
  • mark
  • em
  • Mark
  • mark
  • Mark
  • Em
  • Mark
  • Em
  • Em
  • Transcript

    • 1. TELSTRATEMPLATE4X3BLUEBETA|TELPPTV4 ADOPTING LEFFINGWELL'S SCALED AGILE FRAMEWORK: THE THEORY AND PRACTICE EM CAMPBELL-PRETTY, GM STRATEGIC DELIVERY @PrettyAgile www.prettyagile.com MARK RICHARDS, PRINCIPLE CONSULTANT, RICHDATA @MarkAtScale www.agilenotanchy.com
    • 2. 5 Wagile Teams 4 Projects
    • 3. 3PRESENTATION TITLE | PRESENTER NAME | DATE |
    • 4. THE EDW AGILE RELEASE TRAIN Average delivery cycle time down from 12 month to 3 months Frequency of delivery increased from quarterly to fortnightly Cost to deliver down 50% 95% decrease in product defects 100% projects delivered on time and on budget Happy project sponsors (NPS 29) Happy teams (Team NPS 43 )
    • 5. THE AGILE RELEASE TRAIN • A virtual organization of 5 – 12 teams (50-100 individuals) that plans, commits, and executes together • Common cadence and normalized story point estimating • Aligned to a common mission via a single program backlog • Operates under architectural and UX guidance • Produces valuable and evaluate-able system-level Potentially Shippable Increments (PSI) every 8-12 weeks The ART is a long-lived, self-organizing team of agile teams that delivers solutions Define new functionality Implement Acceptance Test Deploy Repeat until further notice. Project chartering not required.
    • 6. EPICS FEATURES STORIES
    • 7. THE BEST WAY TO START  Train everyone at the same time  Same instructor, same method  Cost effective  Align all teams to common objectives  Commitment  Continue training during planning  Orientation for specialty roles  Open spaces  Tool training for teams Training: SAFe ScrumXP Release Planning Enterprise Scrum Master Quickstart Enterprise Product Owner Quickstart Mon Tue Wed Thu Fri Tooltraining You Are Agile, Now When you find the first train, go “All In” and “All at Once”
    • 8. HOW WE STARTED
    • 9. STRUCTURING THE AGILE RELEASE TRAIN Deployment Services Pipeline Services (connecting, feeding, and shielding the delivery teams. Identification of strategic opportunities) Development Service (engaged and delivering directly to Epic/Feature Owners) Leadership Team ‘Loco’ + Specialist Chapters (virtual teams made from the workers themselves) SD System Team (identifies, manages, and eliminates bottlenecks) Team Collaboration
    • 10. VISUALISE THE PROGRAM PORTFOLIO
    • 11. SCALING THE SPRINT
    • 12. RELEASE PLANNING • Two days every 8-12 weeks • Everyone attends in person if at all possible • Product Management owns feature priorities • Development team owns story planning and high-level estimates • Architects, UX folks work as intermediaries for governance, interfaces and dependencies • Result: A committed set of program objectives for the next PSI Cadence-based PSI/Release Planning meetings are the “pacemaker” of the agile enterprise
    • 13. „PSI-LITE‟ BECOMES UNITY DAY 1515
    • 14. THE FOUNDATION IS LEAN LEADERSHIP 16PRESENTATION TITLE | PRESENTER NAME | DATE | 16PRESENTATION TITLE | PRESENTER NAME | DATE |
    • 15. SCALING THE PRODUCT OWNER Source: Agile Portfolio and Program Management in the Scaled Agile Framework, Dean Leffingwell, Agile Melbourne Meetup, 15/02/12
    • 16. SCALING THE PRODUCT OWNER EPIC OWNER FEATURE OWNER PRODUCT OWNER
    • 17. THE RELEASE BOARD FEATURE LEVEL
    • 18. CONTINUOUS INTER-TEAM COORDINATION • Agile team members may visit other team‟s… • Backlog grooming: to see what‟s coming next sprint, request adjustments • Sprint planning: request adjustments • Daily standups: follow up on execution • Team Demo: summarize current stage Agile teams self-manage dependencies and resolve risks Agile Team 1 Agile Team 2 Dependent story Join other team scrum ceremony
    • 19. SCALING COMMUNICATION: THE DAILY COCKTAIL PARTY 22PRESENTATION TITLE | PRESENTER NAME | DATE | 9:00am 9:15am 930am 9:45am
    • 20. SAFE SCRUM / XP
    • 21. A LITTLE TASTE OF OUR CULTURE http://www.prettyagile.com/2013/05/the-power-of-haka.html
    • 22. QUESTIONS?

    ×