Team Foundation Server 2010<br />1<br />TFS 2010 In real life – EXAMPLES<br />Author : Vincent TAVONEKHAM<br />Date : 04 M...
Why this presentation ?<br />Because I often hear from my various customers : <br />« Yes, TFS 2010 and this Scrum methodo...
THEbiggestcustomer in the world<br />Microsoft is the biggest customer of TFS 2010 and TFS vNext (i.e. could be called TFS...
THE biggestcustomer in the world<br />The use of TFS within Microsoft :<br />42 instances of TFS<br />19,700 unique users<...
Dev 11: The next version of TFS is focused on 90 User’s real needs, called scenario (or Epics in Scrum)<br />Scenario<br /...
Dev 11: Decomposing the next 2 iterations<br />13,732 tasks<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br...
THE biggestcustomer in the world<br />Best practice at Microsoft :<br />« Shorter iterations lead to better decision makin...
THE biggestcustomer in the world<br /><ul><li>Best practice at Microsoft : “Managing and Killing debts” early</li></ul>The...
“Managing and Killing debts” early<br />9<br /><ul><li>Example of a General Electric software
Project management : Scrum + CMMI 2,
Development team scattered in 3 countries (US, India, France),
Deployed in 550 Hospitals worldwide (19 countries and 7 languages).</li></ul>Less and less bugs as we go (the trends tends...
THE biggestcustomer in the world<br />Best practice at Microsoft<br />KISS “Less is more/better” but not always applied !<...
Upcoming SlideShare
Loading in...5
×

Tfs2010 Large Projects Real Life Vincent Thavonekham 2011

1,804

Published on

As a TFS 2010 trainer, I often hear from my various customers :

« Yes, TFS 2010 and this Scrum methodology are great, but it(*) can only work on small projects ! 

Indeed, our project is different, and our team / project is too big and critical to apply this. »

This presentation illustrates the TFS 2010 adoption of one of the biggest customer : Microsoft, and General Electric.


(*) The sticky notes on the big board, the detailing of the User story as we go, the Agile planning and estimating, the self-organizing team, …

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,804
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
23
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Tfs2010 Large Projects Real Life Vincent Thavonekham 2011

  1. 1. Team Foundation Server 2010<br />1<br />TFS 2010 In real life – EXAMPLES<br />Author : Vincent TAVONEKHAM<br />Date : 04 March 2011<br />
  2. 2. Why this presentation ?<br />Because I often hear from my various customers : <br />« Yes, TFS 2010 and this Scrum methodology are great, but it(*) can only work on small projects ! <br />Our project is different, and our team / project is too big and critical to apply this. »<br />2<br />(*) The sticky notes on the big board, the detailing of the User story as we go, the Agile planning and estimating, the self-organizing team, …<br />
  3. 3. THEbiggestcustomer in the world<br />Microsoft is the biggest customer of TFS 2010 and TFS vNext (i.e. could be called TFS 2012)<br />Developing TFS requires :<br />1,032,045,223 files<br />2,024,223 check-ins<br />911,432 work items<br />3,612 unique users<br />17.3 TB of data<br />Largest table: 3.1TB(4.3 billion rows)<br />11,962 areas and iterations<br />(Source Microsoft TechEd Europe 2010 – DPR202)<br />3<br />“Autonomy is both difficult and necessary”<br />
  4. 4. THE biggestcustomer in the world<br />The use of TFS within Microsoft :<br />42 instances of TFS<br />19,700 unique users<br />6,154 team projects<br />7.9 million work items<br />(Source Microsoft TechEd Europe 2010 – DPR202)<br />4<br />
  5. 5. Dev 11: The next version of TFS is focused on 90 User’s real needs, called scenario (or Epics in Scrum)<br />Scenario<br />Scenario<br />Scenario<br />90 scenarios<br />1,115 experiences<br />Experience<br />Experience<br />Experience<br />Experience<br />Experience<br />5,179 user stories<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />
  6. 6. Dev 11: Decomposing the next 2 iterations<br />13,732 tasks<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />User Story<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />Task<br />
  7. 7. THE biggestcustomer in the world<br />Best practice at Microsoft :<br />« Shorter iterations lead to better decision making »<br />« Deliver as often as possible (upgrade) » <br />7<br />Comparing the size of ONE iteration across TFS versions<br />(Source Microsoft TechEd Europe 2010 – DPR202)<br />
  8. 8. THE biggestcustomer in the world<br /><ul><li>Best practice at Microsoft : “Managing and Killing debts” early</li></ul>The red arrow shows the evolution of bugs<br />On TFS 2005 : As the developer are coding and closingbugs, new bugs are introduced. Hence the number oftotal bug remains around 30,000.<br />On TFS 2008 : There is far less bugs. As the project evolves, the number of bugs decreases.<br />8<br />2005 Beta1<br />2008 Beta1<br />
  9. 9. “Managing and Killing debts” early<br />9<br /><ul><li>Example of a General Electric software
  10. 10. Project management : Scrum + CMMI 2,
  11. 11. Development team scattered in 3 countries (US, India, France),
  12. 12. Deployed in 550 Hospitals worldwide (19 countries and 7 languages).</li></ul>Less and less bugs as we go (the trends tends to zero !)<br />Few bugs (v8.4.1), hence concentrate on delivering on time<br />(Source French Scrum User Group, Catherine Boudlal, 2010)<br />
  13. 13. THE biggestcustomer in the world<br />Best practice at Microsoft<br />KISS “Less is more/better” but not always applied !<br />Below an non-KISS approach to fill in a Bug form.<br />10<br />96 visible fields!<br />(Source Microsoft TechEd Europe 2010 – DPR202)<br />(*) KISS : An Agile concept « Keep It Simple Silly ! »<br />
  14. 14. KISS estimating and planning<br />Cone of Uncertainty (IT field, engineering, hurricane, …)<br />About 70% of projects fails in meeting their estimates (Standish group survey 2010)<br />So why not think differently ? Don’t try to estimate ALL upfront, but estimate / re-estimate as you go<br />11<br />“Cone of Uncertainty”<br />
  15. 15. Branching and Merging<br />Example in small to medium projects : <br />« Basic Branch Plan » from Rangers Guidance III<br />It is already difficult to maintain !<br />12<br />
  16. 16. Sources and referenceS<br />More information on TFS and AGILE on my blog<br />www.Thavo.com<br />Microsoft TechEd Europe and US (2009 and 2010)<br />French Scrum User Group : General Electric, Catherine Boudlal<br />http://www.frenchsug.org/pages/viewpage.action?pageId=2818123<br />Visual Studio TFS Branching Guide 2010, ALM Rangers<br />http://tfsbranchingguideiii.codeplex.com<br />“Cone of Uncertainty”, initially developed by Barry Boehm, 1981. Applicable to COBOL, .Net, hurricane, …<br />More references on customers using TFS<br />http://memoprojects.blogspot.com/2010/11/37-case-study-on-tfs-2010.html<br />13<br />These slides are free to use and modify, as long as you insert in your presentation the text in the footer below that mention this copyright,www.Thavo.com<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×