ALM@Work - Team collaboration with visual studio alm 2012

15
@ Team Collaboration with Visual Studio ALM 2012 Matteo Emili http://blogs.ugidotnet.org/j3r http://mattvsts.blogspot.com [email protected] @MattVSTS

description

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

Transcript of ALM@Work - Team collaboration with visual studio alm 2012

Page 1: ALM@Work - Team collaboration with visual studio alm 2012

@Team Collaboration with Visual Studio ALM 2012

Matteo Emilihttp://blogs.ugidotnet.org/j3rhttp://mattvsts.blogspot.com

[email protected]@MattVSTS

Page 2: ALM@Work - Team collaboration with visual studio alm 2012

Grazie agli sponsor

Page 3: ALM@Work - Team collaboration with visual studio alm 2012

@Barriers among team components

Users/Stakeholders

Development Testing OperationsCost increase

Time waste

Negative feedbacks

Page 4: ALM@Work - Team collaboration with visual studio alm 2012

@REQUIREMENTS

PRODUCTBACKLOG

OPSBACKLOG

MonitorImplement

WORKING SOFTWARE

DefineIdeation

DevelopIdea to working software

Unmet userexpectations

Can’t get actionable feedback

Non consistent tool• Ops readiness requirements are not met

Production incidents hard to debug and resolve

No KB management

OperateWorking software in productionValue realization

Users/Stakeholders

Development & testing

OperationsMisunderstoodrequirements

Churn in requirementsand prioritiesQuality afterthoughtNo traceabilityLoss of focus

Page 5: ALM@Work - Team collaboration with visual studio alm 2012

@• Requirements changed on the run• Priorities shifted from a customer

proposal• Project Managers with no control• Poor communication• Long cycles of release

Churn in requirements and priorities

Warning

Customer dissatisfaction!

Page 6: ALM@Work - Team collaboration with visual studio alm 2012

@DEMO

Reducing churn in requisited and priorities

Backlog Management via Taskboard and Agile practices

Page 7: ALM@Work - Team collaboration with visual studio alm 2012

@Loss of focus

Warning

Losing focus leads to mistakes and uncertainty

Context switch is not just a code matter…

Is it going to be reflected in quality?

Page 8: ALM@Work - Team collaboration with visual studio alm 2012

@DEMO

Keeping context switches to the minimum

Team Explorer and Local Workspaces to the rescue

Page 9: ALM@Work - Team collaboration with visual studio alm 2012

@• Due to poor communication/involvement with the stakeholder

• Pre-sales on fire!

Unmet user expectations

Warning

Time and resource wasted

Page 10: ALM@Work - Team collaboration with visual studio alm 2012

@DEMO

Involving stakeholders in the processPowerPoint Storyboarding and Feedback Client

Page 11: ALM@Work - Team collaboration with visual studio alm 2012

@• «...but it works on my machine!»• «...he did that!»• «I didn’t even touch it!»

Operational requirements not met

Warning

Low quality, delay, stress!

Page 12: ALM@Work - Team collaboration with visual studio alm 2012

@DEMO

Quality enhancements with Agile communication

Team Code Review in action!

Page 13: ALM@Work - Team collaboration with visual studio alm 2012

@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/

Enabling direct communication

Page 14: ALM@Work - Team collaboration with visual studio alm 2012

@DEMO

Direct communicationTeam Members

Page 15: ALM@Work - Team collaboration with visual studio alm 2012