TFS 2010: Team Development on Crack


Published on

Steve Lange's afternoon session at the Rocky Mountain Tech Tri-Fecta ( on 2/27/2010.

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

TFS 2010: Team Development on Crack

  1. 1. TFS: Team Development on Crack<br />Team Foundation Server is all grown-up with the upcoming 2010 release.  This session will demonstrate why TFS is more than a central repository for development artifacts; but an integrated platform for “getting stuff done.”  We’ll explore the new moving parts of TFS 2010, covering architecture, version control, work item tracking, build, and reporting; and see how it all ties together.  Attend this session and learn why TFS 2010 needs to be the center of your development universe.<br />Steve Lange<br />Sr. Developer Technology Specialist<br />Microsoft | Denver, CO<br />Field specialist for:<br /><ul><li>Team Foundation Server
  2. 2. Visual Studio Application Lifecycle Management
  3. 3. Visual Studio Test Professional
  4. 4. Lab Management</li></ul><br /><br />
  5. 5. Team Foundation Server<br />Team Development on Crack<br />
  6. 6. First Things First<br />This session is not about crack<br />I am not on crack<br />Microsoft does not condone the use of crack<br />There will be no crack SWAG<br />
  7. 7. Agenda<br />Identifying Teams on Crack<br />Supporting Addictions with Tools<br />Meet your Dealer: Team Foundation Server<br />Your Addiction Supply Chain<br />Manage Your Stash<br />Plan Your Next Score<br />Take a Hit and See What Happens<br />See How Your Addiction Affects Loved Ones<br />How to Get your Fix<br />
  8. 8. Team Development on Crack<br />Happy<br />Energized<br />Synergized<br />Itching for More<br />
  9. 9. Visual Studio 2010<br />
  10. 10. Process<br />Your Addiction Supply Chain<br />
  11. 11. Process Guidance & Automation<br />Embedded into Team Foundation Server<br />Provides contextual guidance (documentation)<br />Delivered via Process Templates<br />Helps ensure predictability<br />Out of the Box, or get your own<br />Customize Nearly Everything<br />
  12. 12. Version Control<br />Manage Your Stash<br />
  13. 13. Key Concepts<br />Changesets<br />Integrated Check-in<br />Check-in Policies<br />Parallel Development<br />Shelving<br />
  14. 14. Changesets<br />Logical container of data related to check-in<br />File and branch information<br />Links to work items<br />Check-in notes<br />Comment<br />Policy compliance<br />Metadata (date, time, user)<br />Unit of atomic checkin<br />Uniquely identified<br />Numeric identifier<br />Incremental<br />Represents a point in time of source repository<br />
  15. 15. Integrated Check-in<br />
  16. 16. Check-in Policies<br />Requirements for Check-in<br />Overridable<br />Extensible<br />
  17. 17. demo<br />
  18. 18. Shelving: Share Your Stash<br />Set aside pending changes<br />Task branching w/ less overhead<br />
  19. 19. Compare/Diff/Merge<br />
  20. 20. Parallel Development<br />
  21. 21. Branch Visualization<br />Focuses on answering common parallel development questions<br />Where did this change come from?<br />Has my change made it over there?<br />How are these branches related?<br />
  22. 22. demo<br />
  23. 23. Work Item Tracking<br />Plan Your Next Score<br />
  24. 24. Bugs: What Do You Call Them?<br />
  25. 25. Work Item Tracking<br />
  26. 26. Plan Your Next Score<br />
  27. 27. More on Work Items<br />Title<br />Description<br />Assignment<br />State<br />Attachments<br />Links<br />History<br />
  28. 28. Work Item Report Generation<br />
  29. 29. demo<br />
  30. 30. Build Management & Automation<br />Take a Hit and See What Happens<br />
  31. 31. Build Automation<br />
  32. 32. Create a Supportive Build Workflow<br />
  33. 33. Gated Check-in<br />Edit Code<br />Check in<br />Build and Test<br />Did build succeed?<br />Fixavailable?<br />Find root cause<br />Yes<br />No<br />Yes<br />No<br />Teamblocked<br />Edit code<br />Gated check-in<br />Automated build<br />Did build succeed?<br />Commit Changes<br />Readyfor test<br />No<br />Yes<br />Before<br />Intercepts check-ins<br />Queues a server build to validate changes<br />Only changes that build successfully get committed<br />Definition of a “success” is customizable<br />Users can also queue a build of a shelveset for “opt-in” validation<br />After<br />
  34. 34.
  35. 35. demo<br />
  36. 36. Reporting<br />See How Your Addiction Affects Loved Ones<br />
  37. 37. Reporting<br />
  38. 38. Dashboards<br />Information-rich dashboards<br />Roll-up reports show KPI’s<br />Drill-down for further analysis<br />Quickly customizable<br />Easy interaction with developers<br />Web-based bug filing<br />Web-based feature requests<br />Track status of bugs / features<br />
  39. 39. Microsoft Confidential<br />36<br />
  40. 40. Microsoft Confidential<br />37<br />
  41. 41. How many bugs do we have?<br />Shows state of bugs over time and by priority<br />Bug Status<br />
  42. 42. How are the user stories tracking?<br />User Story Implementation<br />
  43. 43. What is the progress or our test plans?<br />Test Plan Progress<br />
  44. 44. Test Run Results<br />
  45. 45. TFS: A Big Addiction<br />Team Foundation Server<br />
  46. 46. How to Get Your Fix<br />Pick a Gateway<br />Version Control<br />Try it Out<br />G’head, the first one’s free<br />Do it Right<br />You’ll come back for more<br />
  47. 47. Needed Reminder?<br />This session is not about crack<br />I am not on crack<br />Microsoft does not condone the use of crack<br />There will be no crack SWAG<br />
  48. 48. Please Thank a Sponsor<br />