Share
Embed
Slide 1
Slide 1 text
Azure Engineering
@cmaneu
Slide 2
Slide 2 text
Increase flow of value Shorten cycle times Continuously Improve
Slide 3
Slide 3 text
No content
Slide 4
Slide 4 text
Sprint 1
August 2010
Sprint 29
June 2012
VSTS Preview
Sprint 64
April 2014
VSTS GA
Sprint 67
June 2014
1ES
Sprint 92
Nov 2015
Extensions
Sprint 102
June 2016
GVFS
Sprint 124
Sep 2016
Slide 5
Slide 5 text
Build what
customers
actually want
Empower
individuals and
teams
Innovate at a
Cloud
Cadence
More features in the 2016
calendar year (262 features)
than the previous 4 years
Combined (256 features).
And the growth continues!
22
58 65
111
262
435
2012 2013 2014 2015 2016 2017
Slide 6
Slide 6 text
Team Autonomy + Enterprise Alignment
Shift Left Quality
Customer Focused
Production First Mindset
Infrastructure as Flexible Resource
Slide 7
Slide 7 text
Team Autonomy + Enterprise Alignment
Shift Left Quality
Customer Focused
Production First Mindset
Infrastructure as Flexible Resource
Slide 8
Slide 8 text
Alignment
Autonomy
“Let’s try to give our teams three things….
Autonomy, Mastery, Purpose”
Slide 9
Slide 9 text
No content
Slide 10
Slide 10 text
No content
Slide 11
Slide 11 text
No content
Slide 12
Slide 12 text
Teams
Physical team rooms
Cross discipline
10-12 people
Self managing
Clear charter and goals
Intact for 12-18 months
Own features in production
Own deployment of features
Slide 13
Slide 13 text
UI
API
Data
Slide 14
Slide 14 text
UI
API
Data
Slide 15
Slide 15 text
Employee choice, not
manager driven
Typically <20%
change, but 100% get
to make a choice
Cross-pollinate talent
and micro-culture
Sticky Note Exercise - Self Forming Teams
Slide 16
Slide 16 text
Sprint
3 weeks
1
Plan
3 sprints
3
Season
6 months
6
Scenario
18 months
Teams are responsible for the detail
Leadership is responsible
for driving the big picture
Slide 17
Slide 17 text
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
18 month scenario
6 month plan
CY17 H1
Slide 18
Slide 18 text
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
18 month scenario
6 month plan
Slide 19
Slide 19 text
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
18 month scenario
6 month plan
Slide 20
Slide 20 text
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
18 month scenario
6 month plan
Slide 21
Slide 21 text
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
18 month scenario
6 month plan
Slide 22
Slide 22 text
3 weeks
Spring
Fall
Spring Fall
Slide 23
Slide 23 text
What we accomplished
Progressive
Deployment
Week 1 Week 2 Week 3
Week 1 Week 2 Week 3
Week 2 Week 3
Sprint 98
Sprint 97 Sprint 99
The sprint plan
Slide 24
Slide 24 text
No content
Slide 25
Slide 25 text
No content
Slide 26
Slide 26 text
Spring
Fall
Spring Fall
3 sprints
Slide 27
Slide 27 text
No content
Slide 28
Slide 28 text
No content
Slide 29
Slide 29 text
Work Management
Information Tools
Coding Tools
Testing Tools
Build Tools
Debugging Tools
Developer
Time
Source: Internal Microsoft Telemetry analysis of 4700 engineers in WDG
Slide 30
Slide 30 text
Team Autonomy + Enterprise Alignment
Shift Left Quality
Customer Focused
Production First Mindset
Infrastructure as Flexible Resource
Slide 31
Slide 31 text
No content
Slide 32
Slide 32 text
Code Test & Stabilize Code Test & Stabilize
Code
Complete
Planning
Slide 33
Slide 33 text
No content
Slide 34
Slide 34 text
engineers on
your team
# 5 ?
x =
Slide 35
Slide 35 text
Rule: If your bug count exceeds your bug cap… stop working
on new features until you’re back under the cap.
5 50
x =
10
Slide 36
Slide 36 text
• Tests that anyone can run anywhere (inc production)
• Shifted to unit tests from automated functional tests
• Core tests run before pull request
• Fast and 100% reliable build and test is critical
• Rolling tests run after commit
Slide 37
Slide 37 text
No content
Slide 38
Slide 38 text
Team Autonomy + Enterprise Alignment
Shift Left Quality
Customer Focused
Production First Mindset
Infrastructure as Flexible Resource
Slide 39
Slide 39 text
No content
Slide 40
Slide 40 text
No content
Slide 41
Slide 41 text
No content
Slide 42
Slide 42 text
• Original estimate
• Completed hours
• Lines of Code
• Team capacity
• Team burndown
• Team velocity
• # of bugs found
Things we don’t watch
• Acquisition
• Engagement
• Satisfaction
• Churn
• Feature Usage
Usage
• Time to Detect
• Time to Communicate
• Time to Mitigate
• Customer Impact
• Incident Prevention Items
• Aging Live Site Problems
• SLA per Customer
• Customer Support Metrics
Live Site Health
• Time to Build
• Time to Self Test
• Time to Deploy
• Time to Learn
Velocity
Slide 43
Slide 43 text
Found one of the top customers with low availability.
Proactively reached out and resolved their issue.
Slide 44
Slide 44 text
No content
Slide 45
Slide 45 text
No content
Slide 46
Slide 46 text
No content
Slide 47
Slide 47 text
Team Autonomy + Enterprise Alignment
Shift Left Quality
Customer Focused
Production First Mindset
Infrastructure as Flexible Resource
Slide 48
Slide 48 text
•
•
•
•
•
•
•
Slide 49
Slide 49 text
No content
Slide 50
Slide 50 text
Slide 51
Slide 51 text
1 2 3 4 5
Slide 52
Slide 52 text
https://github.com/Netflix/Hystrix/wiki
Slide 53
Slide 53 text
•
•
•
•
•
•
•
•
•
Slide 54
Slide 54 text
Double blind test
Full disclosure at or near end
vs.
Share tactics & lessons learned
Continued evolution
Assume Breach - Use War Games to the learn attacks and practice response
Slide 55
Slide 55 text
Team Autonomy + Enterprise Alignment
Shift Left Quality
Customer Focused
Production First Mindset
Infrastructure as Flexible Resource
Slide 56
Slide 56 text
No content
Slide 57
Slide 57 text
Shared abstraction layer
Single master branch, multiple release branches
Update 1
Update 2
Update N
Visual Studio Team Services
Team Foundation Server
One code base with multiple delivery streams
Slide 58
Slide 58 text
Shared Platform Services (SPS)
North Central
TFS SU1
North Central
AT
AT
AT
JA
JA
JA
Blob
TFS SU7
Australia
TFS SU0
West Central
Containerized Services
Slide 59
Slide 59 text
•
•
•
•
•
• If you are starting out today and cloud native, consider
PaaS, Service Fabric + Azure Functions
• We need to ship same code to on-prem & cloud
Slide 60
Slide 60 text
After
• 3-week sprints
• Vertical teams
• Team rooms
• Continual Planning & Learning
• PM & Engineering
• Continual customer engagement
• Everyone in master
• 8-12 person teams
• Publicly shared roadmap
• Zero debt
• Mockups in PPT
• Inner source
• Flattened organization hierarchy
• User satisfaction determines success
• Features shipped every sprint
Before
• 4-6 month milestones
• Horizontal teams
• Personal offices
• Long planning cycles
• PM, Dev, Test
• Yearly customer engagement
• Feature branches
• 20+ person teams
• Secret roadmap
• Bug debt
• 100 page spec documents
• Private repositories
• Deep organizational hierarchy
• Success is a measure of install numbers
• Features shipped once a year
Slide 61
Slide 61 text
No content