where are we in terms of 0 to devops... · self-organizing, autonomous, cross-functional ranger...
TRANSCRIPT
Rui Melo
Senior Premier Field Engineer
Microsoft
Willy Schaub
Senior Program ManagerMicrosoft
LISTEN
PLAN
DELIGHTAPOLOGISE
ENABLE
LISTEN
ENGAGE
We’re members of the community
Providing professional guidance, practical experience and gap-filling solutions to the developer community.
We fill gaps, not craters!
We’re distributed … we’re here for YOU! Talk to us!Country Rangers
United States of America 39
United Kingdom 8
The Netherlands 6
Brazil 5
South Africa 5
Sweden 5
Portugal 4
Roaming 4
France 3
India 3
Switzerland 3
Canada 2
Israel 2
Russia 2
Australia 1
Bulgaria 1
Ecuador 1
Egypt 1
FYRO Macedonia 1
Germany 1
Guatemala 1
Italy 1
Jordan 1
Mexico 1
Turkey 1
Ukraine 1
Why did we consider self-organisation?
Our journey …
2006 2009 2012 2015
MSF Scrum Ruck (loose-Scrum)
2016
Kanban +
Self-Organized
Rigid
Agile
Pro
cess
Rigid
Agile
Pro
cess
2 PMs
200+ Rangers
5 Projects
0.5 PM
100 active Rangers
10 Projects
aka.ms/wsbook3 aka.ms/wsbook4
1.75h/WEEK
How do we self-organize?
Deci
de
Be part
of … Ch
oo
se Working
model Sele
ct Tools
Team members …
IDENTIFY
a gap 1VOLUNTEER
to be part of a team
DEFINE a common
vision and goalPITCH
an idea2
4
3
Model blueprint
Common vision
Common sprintcadence (3w)
Small teams
6+-3
PM
Regular Scrums
video conferencing(weekly)
Review and show what we have demo
videosKanban boards
“visual and live”
“How to” plan is owned by team
1-n PBIs
1 epic/release
1-3 features/release
Evaluate + sell vision with a prototype
- -
CI BUILD
CD(elivery) x 3MONITOR
AI
Bugs
Feedback
Embrace DevOps
Self-organizing, autonomous, cross-functional Ranger teams
Engineering
teams
PM
We are passionate about one of the ideas!
We will create a team of passionate volunteers!
“We have ideas or adoption blockers!”
“We cannot implement features on our backlog”
Focus on gaps, avoid craters
Consistent process (sprint length + cadence, “rub on DevOps”)
Enable teams | align expectations & vocabulary with engineering
What are we learning?
Key learnings (so far)
A community with a common vision nurtures vibrant teams
Teams that identify themselves with their “process” produce more
Given the chance, teams will define their “process” and commit to it
Being involved in decision making fuels energy and commitment
Autonomous teams are more passionate and likely to succeed
DevOps enables and focuses teams
Program Manager is key to enable, connect, and encourage teams
Small energetic “teams” deliver more value than a larger “group”
Are we there yet?
ALM Rangers aka.ms/vsarblog@almrangers
Donovan Brown www.DonovanBrown.com@DonovanBrown
Rui Melo [email protected]@ruimelo
Willy Schaub [email protected]@wpschaub
Mentioned content aka.ms/wsbook3 (engineers on their way to pluto)
aka.ms/wsbook4 (managing agile oss projects with VSTS)
aka.ms/devops-extension (pipeline article)
URLs
Contact us on https://aka.ms/vsarblog
Q&AQ&A