SlideShare a Scribd company logo

Ag04 gestire gruppi di lavoro, team multipli e progetti con visual studio alm

•Download as PPTX, PDF•
•
DotNetCampus
DotNetCampus

This document discusses tools for agile development and managing projects in Visual Studio ALM 2013. It advocates finding a balance with tools by using them to provide a single source of truth while not over-relying on processes or standardization. Visual Studio ALM 2013 supports agile planning, work item tracking, boards for tracking progress, and portfolio management across multiple teams and projects.

1 of 33
Template designed by Gestire gruppi di lavoro, team multipli e progetti con Visual Studio ALM Matteo Emili Microsoft MVP – Visual Studio ALM http://mattvsts.blogspot.com http://twitter.com/MattVSTS matteo.emili@live.com
brought to you by
Microsoft MVP – Visual Studio ALM Microsoft Certified Technology Specialist – Team Foundation Server Professional Scrum Master I I work at Dell Software UK (Engineering Advisor) Communities! • DomusDotNet GetLatestVersion.it • London ALM UG Taunton Developers Meetup Who am I?
Manifesto for Agile Software Development New and better ways of developing software by doing it and helping others do it. Through this work we have come to value: • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left, and the related tools, more.
Specifically…Tools • The Agile community has often been skeptical of tooling solutions • May get in the way – easier with pen and post-its! • Often don’t respond fast enough • Standardization of tools across an enterprise may kill self-organization • May be used to squash core concepts in agile – responding to change, self-organization, empirical process control
Agile + Tools • Can we find some sort of happy medium? • One source of the truth – stop the Post-Its vs. the tools! • Ease of use – I don’t want to build a burndown manually! • Don’t use the tool for evil! Shut down/ignore things like • Fine-grained, single-employee-centric capacity planning • Long-term planning gone wrong (where Release Burndown = Gantt Chart  ) • Agile to PMI-style PMO bridges
Visual Studio ALM 2013 fast. forward. thinking.
Continuous Value Delivery
Stakeholder Involvement
Developer Team Productivity
DevOps
Continuous Value Delivery • Agile Planning
We can shape Teams inside Team Foundation Server, describing their hierarchy and permissions They are not security groups: • A Team Project can have zero or more teams • A Team contains one or more members • A member does not need to be in a Team Team Foundation Server helps us
Work Item Tracking to the rescue • All you need for Agile Planning and Execution leverages on the Work Item Tracking features • Work Item Tracking primer – a Work Item is a description of a certain activity in a XML format, parsed by Team Foundation Server and shown with a UI
Back to a Single Source of Truth for TFS! fast. forward. thinking.
Agile Planning, Boards and Capacity Planning
Reports
Let’s go one step ahead – can we manage programs/portfolios with TFS’ Agile tools? Yes, we can  TFS 2013 introduces the Agile Portfolio Management, which enables organizations to go over the single Team Project Agile Portfolio Management
Themes and Epics Themes are big containers in the Product E.g.: a major (part of a) release -> MyProduct 3.0 / Media Center for Windows Epics are common topics in the Product E.g.: a big, marketable feature -> Ecommerce roundtrip Theme Epic User Story User Story Epic User Story
A little more on Epics • They act as a buffer for the management, providing an high level overview of what is going on • They provide a better visualization for the Product Backlog, which is easier to understand at the first sight • More information for the User Stories – you can figure out how are they linked together
“A common problem” • User Stories to big to fit into a sprint • Sometimes is hard to split them correctly • Effort estimation can be difficult with big user story
The Problem
Portfolio Backlogs
Backlog Linking
Backlog Linking
Backlog Linking
Ag04 gestire gruppi di lavoro, team multipli e progetti con visual studio alm
Autonomy
Autonomy
It is just a detail in the picture… Often you can find other levels above
Ag04 gestire gruppi di lavoro, team multipli e progetti con visual studio alm
Agile Portfolio Management in practice
Grazie a tutti per la partecipazione Riceverete il link per il download a slide e demo via email nei prossimi giorni Per contattarmi matteo.emili@live.com http://twitter.com/MattVSTS Thanks! 

More Related Content

Ag04 gestire gruppi di lavoro, team multipli e progetti con visual studio alm

  • 1. Template designed by Gestire gruppi di lavoro, team multipli e progetti con Visual Studio ALM Matteo Emili Microsoft MVP – Visual Studio ALM http://mattvsts.blogspot.com http://twitter.com/MattVSTS matteo.emili@live.com
  • 3. Microsoft MVP – Visual Studio ALM Microsoft Certified Technology Specialist – Team Foundation Server Professional Scrum Master I I work at Dell Software UK (Engineering Advisor) Communities! • DomusDotNet GetLatestVersion.it • London ALM UG Taunton Developers Meetup Who am I?
  • 4. Manifesto for Agile Software Development New and better ways of developing software by doing it and helping others do it. Through this work we have come to value: • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left, and the related tools, more.
  • 5. Specifically…Tools • The Agile community has often been skeptical of tooling solutions • May get in the way – easier with pen and post-its! • Often don’t respond fast enough • Standardization of tools across an enterprise may kill self-organization • May be used to squash core concepts in agile – responding to change, self-organization, empirical process control
  • 6. Agile + Tools • Can we find some sort of happy medium? • One source of the truth – stop the Post-Its vs. the tools! • Ease of use – I don’t want to build a burndown manually! • Don’t use the tool for evil! Shut down/ignore things like • Fine-grained, single-employee-centric capacity planning • Long-term planning gone wrong (where Release Burndown = Gantt Chart  ) • Agile to PMI-style PMO bridges
  • 7. Visual Studio ALM 2013 fast. forward. thinking.
  • 13. We can shape Teams inside Team Foundation Server, describing their hierarchy and permissions They are not security groups: • A Team Project can have zero or more teams • A Team contains one or more members • A member does not need to be in a Team Team Foundation Server helps us
  • 14. Work Item Tracking to the rescue • All you need for Agile Planning and Execution leverages on the Work Item Tracking features • Work Item Tracking primer – a Work Item is a description of a certain activity in a XML format, parsed by Team Foundation Server and shown with a UI
  • 15. Back to a Single Source of Truth for TFS! fast. forward. thinking.
  • 16. Agile Planning, Boards and Capacity Planning
  • 18. Let’s go one step ahead – can we manage programs/portfolios with TFS’ Agile tools? Yes, we can  TFS 2013 introduces the Agile Portfolio Management, which enables organizations to go over the single Team Project Agile Portfolio Management
  • 19. Themes and Epics Themes are big containers in the Product E.g.: a major (part of a) release -> MyProduct 3.0 / Media Center for Windows Epics are common topics in the Product E.g.: a big, marketable feature -> Ecommerce roundtrip Theme Epic User Story User Story Epic User Story
  • 20. A little more on Epics • They act as a buffer for the management, providing an high level overview of what is going on • They provide a better visualization for the Product Backlog, which is easier to understand at the first sight • More information for the User Stories – you can figure out how are they linked together
  • 21. “A common problem” • User Stories to big to fit into a sprint • Sometimes is hard to split them correctly • Effort estimation can be difficult with big user story
  • 30. It is just a detail in the picture… Often you can find other levels above
  • 33. Grazie a tutti per la partecipazione Riceverete il link per il download a slide e demo via email nei prossimi giorni Per contattarmi matteo.emili@live.com http://twitter.com/MattVSTS Thanks! 