1. Prepare the virtual environment on a single laptop
  2. Explain this isolated virtual environment
  3. Show the target web site
  4. Remote to the web server and show the environment settings
  5. Damage the site (delete some files and change some IIS settings, etc.)
  6. Show the damaged site (and errors showed)
  7. Open 2 work items for the issue (one Bug and one Task) – One for velocity and one for burn down
  8. Show source code branches and explain briefly about the branching strategies
  9. Modify the page (put current date time on it to illustrate the changes)
  10. Check In, without associate any work items to show the error and check in policy
  11. Check in, associate a work item this time and explain what will happen next
  12. Check-In => Build => Virtual Env => Deploy => Automatic Tests => Notification
  13. Explain notification is handled by TFS event handling process
  14. TFS Event => SOAP message => Web Service => Folder Monitor => Event Handlers => Emails
  15. Explain utilization of MS Workflow + Activities implementation
  16. Show reports of Velocity and Burn down
  17. Show SharePoint portal for dashboard and Wiki
  18. Update work items’ Remaining Work and Assign To and show the linked changesets from history
  19. Check/Show the build progress
  20. Check emails through web interface (WOA)
  21. Emphasize again about the isolated domain setting (DC + Exchange +  TFS + VMs,…)
  22. When emails are received, show the “fixed” web site
  23. Show the recovered IIS settings
  24. Update/Close work items as they are passed by our QA
  25. Run web services to update DW & SSAS
  26. Show the updated burn down chart (velocity is grouped by date, we may not able to show it tight away unless modifying the report that way)
  27. Show some SCM specific reports
  28. Done – Q & A