![Single Secret Leader Election - Stanford Universitycrypto.stanford.edu/~saba/slides/SSLE.pdfPart 1 com(u1) com(u2) com(u3) com(u4) com(u5) Election R∈[N] com(u2) com(u5) com(u4)](https://static.fdocuments.in/doc/165x107/6049abecaf0f86461d49642a/single-secret-leader-election-stanford-sabaslidessslepdf-part-1-comu1-comu2.jpg)
Languages
Pages
Legal
TFS
2008TFS
2010TFS
2012
TFS
2013
TFS
2005TFS
2015
TFS
U1
TFS
U2
TFS
U3
TFS
U4
TFS
U5
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 AND high quality and meets customers needs.
Our teams
Program Management Engineering
Cross discipline10-12 peopleSelf managingAutonomous backlogIntact for 12-18 monthsPhysical team rooms
Teams
3 week sprints
3 weeks
Week 1 Week 2 Week 3
Week 1 Week 2 Week 3Week 2 Week 3
Sprint 69Sprint 68 Sprint 70
Deployment
Sprint Planning Done!
What we accomplished
Week 1 Week 2 Week 3
Week 1 Week 2 Week 3Week 2 Week 3
Sprint 86Sprint 85 Sprint 87
The sprint plan
Plan Accomplished
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
18 month scenario
6 month plan
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
18 month scenario
6 month plan
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
18 month scenario
6 month plan
Scenario18 months
Plan3 sprints
3
Sprint3 weeks
1
Season6 months
6Teams are responsible for the detail
Leadership is responsible for the big picture
Code Test & Stabilize Code Test & Stabilize
CodeComplete
Quality before• Multi-year cycles
• Milestones and stabilizations
• Debt
Quality after
Bugs
Bugs
© 2015 Microsoft Corporation. All rights reserved.
Microsoft, Windows and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Top Related