Professional Team Foundation Server 2012

Chapter 13

Managing Teams and Agile Planning Tools

What's in this chapter?

Defining and managing your product backlog

Planning an iteration while balancing resource capacity

Tracking your work using task boards

Understanding options for customizing the agile planning and tracking tools

Discovering how the development team can request feedback from stakeholders on specific features or requirements

Learning how project stakeholders can use the Microsoft Feedback Client to provide rich feedback about your software

 

The Agile Manifesto defines several guiding principles that have implications on the ways in which teams manage projects. Instead of attempting to define an entire project schedule up front, as with a waterfall methodology, an agile team allows the plan to evolve over time. Work is broken down into multiple successive iterations, each of which might last between one and four weeks.

Teams practicing an agile development methodology tend to embark upon a journey of mutual discovery with their customers to determine new work dynamically, based on changing business priorities or on feedback from work done in previous iterations. The customer, or at least a proxy for the customer, is considered a virtual member of the team and participates in defining and prioritizing (and often re-prioritizing) work over time.

The pursuit to embrace agile development, with dynamic schedules and evolving requirements, has meant that many of the tools and techniques used for traditional project ...