Upload
patrick-blair
View
214
Download
0
Tags:
Embed Size (px)
Citation preview
Karen NgPrincipal Group Program ManagerVisual Studio Cloud ServicesMicrosoft
Agile and DevOps at Microsoft
VSIP SUMMIT 2014
There is no single way Agile is done at Microsoft
This is the Developer Division’s story• 3 week sprints• Scrum at the team level• Emphasis on self-managed teams• Top-down and bottom-up• Expanding to DevOps
The punchline
VSIP SUMMIT 2014
OLD: Planning
Planning M1 M2
SpecsSpecs
Specs
We knew exactly what to build, and we knew it
was right!
VSIP SUMMIT 2014
OLD: Milestones
Planning M1 M2
Beta RTM
We had a perfect schedule and knew exactly when it would
be ready!
VSIP SUMMIT 2014
OLD: Milestones
Code Test & Stabilize Code Test & Stabilize
We now had perfect estimates and we understood how it would
all come together!
VSIP SUMMIT 2014
OLD: Writing code
Code Test & Stabilize Code Test & Stabilize
CodeComplete
We wrote all the code months before we shipped a release.
VSIP SUMMIT 2014
OLD: Fixing bugs
Code Test & Stabilize Code Test & Stabilize
Stabilize
We now just needed to stabilize the code and get it ready to ship to customers
Diego Lo Giudice and Dave West, ForresterFebruary 2011Transforming Application Delivery
Times have changed!“Firms today experience a much higher velocity of business change. Market opportunities appear or dissolve in months or weeks instead of years.“
VSIP SUMMIT 2014
• Roles• Organization• Teams• Cadence• Plan• Practices
Guiding principles
Alignment
Autonomy
Autonomy, Mastery, Purpose
http://www.youtube.com/watch?v=u6XAPnuFjJc
VSIP SUMMIT 2014
Our roles
Program Manager – Responsible to ensure we’re building the right thing.
Engineer – Responsible to ensure we’re building products that are fast, reliable, and well engineered.
VSIP SUMMIT 2014
• Cross discipline• 10-12 people• Self managing• Autonomous backlog• Intact for 12-18 months• Physical team rooms
Teams
VSIP SUMMIT 2014
• Yes, we do have some remote individuals. It’s the exception, not the rule.• We aim for remote teams, not remote
disciplines.
Q: What about remote employees?
Question?
VSIP SUMMIT 2014
3 week sprints
Week 1 Week 2 Week 3
Week 1 Week 2 Week 3Week 2 Week 3
Sprint 69Sprint 68 Sprint 70
Deployment
Sprint Planning
Done!
VSIP SUMMIT 2014
What we accomplished
3 week sprints
Week 1 Week 2 Week 3
Week 1 Week 2 Week 3Week 2 Week 3
Sprint 69Sprint 68 Sprint 70
The sprint plan
VSIP SUMMIT 2014
Code Test & Stabilize Code Test & Stabilize
CodeComplete
Q: Are these real sprints? Question?
VSIP SUMMIT 2014
Things we don’t watch• Team burndown• Team velocity• Original estimate• Completed hours• Team capacity• # of bugs found
Q: What do you track?
Things we watch• # of bugs• Unit test coverage• Rolling build quality• Dev cycle time• Live site issues
Question?
VSIP SUMMIT 2014
1. What’s next on your backlog?
2. What’s your debt situation?
3. Any issues?
3 Questions
VSIP SUMMIT 2014
• Storyboard of what you’re going to build• High level execution plan• Talk about sprints, not hours
• Feedback, feedback, feedback
Experience Review
VSIP SUMMIT 2014
• Monthly view of service availability• Health check of operational metrics• Talk about what happened, how, and what
you’re doing about it
Service Review
VSIP SUMMIT 2014
Vision
SpringFallSpring Fall
6 month plan
SpecsSpecsExperience Reviews
18 month vision
SpecsSpecsScenario Review
VSIP SUMMIT 2014
Now what?
SpringFallSpring Fall
Done!
What did we learn over the last 6 months? What did customers tells us? What did the telemetry tell us?What changed in the marketplace?
VSIP SUMMIT 2014
Planning
SpringFallSpring Fall
6 month plan
SpecsSpecsExperience Reviews
18 month vision
SpecsSpecsScenario Review
Done!Done!
& Learning
VSIP SUMMIT 2014
1. Less is more2. Get out of your teams’ way3. Autonomy, mastery, purpose4. Plan & learn5. Have fun
Take-a-ways
VSIP SUMMIT 2014
http://aka.ms/engineeringstories
Hear more about our journey…