Sessione "Team collaboration with visual studio alm 2012" tenuta da Matteo Emili nell'evento "ALM@Work" di DomusDotNet il 28/09/2012

1. Team Collaboration with Visual Studio ALM
2012
Matteo Emili
http://blogs.ugidotnet.org/j3r
http://mattvsts.blogspot.com
matteo.emili@domusdotnet.org
@MattVSTS

2. Grazie agli sponsor

3. Barriers among team components

4. Monitor
Operate
Working software
in production
Value realization

5. • Requirements changed on the run
• Priorities shifted from a customer
proposal
• Project Managers with no control
• Poor communication
• Long cycles of release
Customer dissatisfaction!
Warning

6. DEMO
Reducing churn in requisited and priorities
Backlog Management via Taskboard and Agile practices

7. Loss of focus
Losing focus leads to mistakes and uncertainty
Context switch is not just a code matter…
Is it going to be reflected in quality?
Warning

8. DEMO
Keeping context switches to the minimum
Team Explorer and Local Workspaces to the rescue

9. • Due to poor communication/involvement
with the stakeholder
• Pre-sales on fire!
Time and resource wasted
Warning

10. DEMO
Involving stakeholders in the process
PowerPoint Storyboarding and Feedback Client

11. • «...but it works on my machine!»
• «...he did that!»
• «I didn’t even touch it!»
Low quality, delay, stress!
Warning

12. DEMO
Quality enhancements with Agile
communication
Team Code Review in action!

13. Enabling direct communication
Team Foundation Server PowerTools
provides us a “Team Member tab”
Integrated with Lync, MSN Messenger (for
old sake)
Open Source project:
http://tfscollab.codeplex.com/

14. DEMO
Direct communication
Team Members