big retro - greg wright, director of software development at kepware
TRANSCRIPT
![Page 1: Big Retro - Greg Wright, Director of Software Development at Kepware](https://reader036.vdocument.in/reader036/viewer/2022070600/58ec93611a28ab340d8b46c7/html5/thumbnails/1.jpg)
LIGHTNING TALK:BIG RETRO
Greg WrightDirector of Software Development
1/11/2017
![Page 2: Big Retro - Greg Wright, Director of Software Development at Kepware](https://reader036.vdocument.in/reader036/viewer/2022070600/58ec93611a28ab340d8b46c7/html5/thumbnails/2.jpg)
2
– 18 Months
– 10 Agile Teams • (Most practicing Scrum)
– 50 Engineers • (including 40% growth)
– 900 Man Months • (144000 Man Hours)
BIG RETRO: KEPSERVEREX 6.0 EFFORT, BY THE NUMBERS
– 160+ Products Refactored
– 2 New languages supported
– 300+ Team Retros
– 120+ Team Kaizens
– 1 Acquisition
– 1 Successful Release
![Page 3: Big Retro - Greg Wright, Director of Software Development at Kepware](https://reader036.vdocument.in/reader036/viewer/2022070600/58ec93611a28ab340d8b46c7/html5/thumbnails/3.jpg)
3
Our Question:
– How can we take something that seems like this:
– And make it feel like this?
Our Answer:
– Engineering wide retro sessions
• Engineers determine the topics
• Breakout sessions scheduled and negotiated (dynamic agenda)
• Discussions, owners and actions
• Beer and snacks and beer
– Borrowed elements from “Open Space” • http://openspaceworld.org/• http://openspaceagility.com/
BIG RETRO: THE CHALLENGE
![Page 4: Big Retro - Greg Wright, Director of Software Development at Kepware](https://reader036.vdocument.in/reader036/viewer/2022070600/58ec93611a28ab340d8b46c7/html5/thumbnails/4.jpg)
4
• Scrum Masters and management planned and socialized the event• Allowed 2+ weeks notice for ideas to cook• Scrum Masters collected Retro notes and shared with their teams• Participation was optional• We prepared for the unknown!
BIG RETRO: THE SETUP
![Page 5: Big Retro - Greg Wright, Director of Software Development at Kepware](https://reader036.vdocument.in/reader036/viewer/2022070600/58ec93611a28ab340d8b46c7/html5/thumbnails/5.jpg)
5
– Opening• Intro and ground rules
– Topic Identification• Topics go on board (group activity)
– Agenda Creation/Negotiation• Topics discussed, aggregated, finalized• Schedule takes shape
– Break• People plan their itinerary
– Breakout discussions held• Notes taken, actions documented
– Closing• Topics and actions summarized• Retro the retro
– Law of Two Feet encouraged
BIG RETRO: THE EVENT
Topics included: Security Testing, Release Regression, Standards, Device Management, Docutecture, Communication, Automation, Project Estimates, Build System, Late Changes, Wild Card
![Page 6: Big Retro - Greg Wright, Director of Software Development at Kepware](https://reader036.vdocument.in/reader036/viewer/2022070600/58ec93611a28ab340d8b46c7/html5/thumbnails/6.jpg)
6
BIG RETRO: THE AFTERMATH
Artifacts: Retro of Retro: Follow-up:
![Page 7: Big Retro - Greg Wright, Director of Software Development at Kepware](https://reader036.vdocument.in/reader036/viewer/2022070600/58ec93611a28ab340d8b46c7/html5/thumbnails/7.jpg)
7
• What made it a success:
– Continuous improvement is core to our culture
– It was fun
– People felt safe
– People were prepared for difficult topics
– We made a commitment to follow up
– We had the support of the organization
BIG RETRO: SUMMING UP