Professional Application Lifecycle Management with Visual Studio 2013

Chapter 12Agile Planning and Tracking

What's in this chapter?

• Defining and managing the product backlog
• Planning an iteration while balancing resource capacity
• Tracking work using task boards
• Understanding options for customizing the agile planning and tracking tools

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 should last no more than 30 days.

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 completed 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 ordering (and often reordering) 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 management are no longer sufficient. Agile practitioners have needed to look for different ways of capturing work, balancing resource capacity, tracking status, and so on.

Scrum, which is by far the most popular agile development practice in use today, ...