agile project management with visual studio tfs 2013 - my presentation at regional scrum gathering...
DESCRIPTION
This presentation is to give overview of Agile Planning for continuous delivery for value, Agile Project Management dashboard, Sprint Planning, Burn Down Charts. Distributed project team collaborate using Team Room, Task board update for all work and used during Daily Stand Up meeting. Out of box (OOB) template for CMMI, Agile and Scrum. The main distinctions between the three default process templates are in the work item types they provide for planning and tracking work. Visual Studio Scrum is the most light-weight and MSF for Capability Maturity Model Integration (CMMI) provides the most support for formal processes and change management. 1. Microsoft Visual Studio Scrum 2013 - Choose Visual Studio Scrum if your team manages bugs along with product backlog items during sprint planning. 2. MSF for Agile Software Development 2013 - Choose Agile if your organization triages bugs separately from the product backlog and resolves work items before closing them. Also, choose Agile if your team allocates time for bugs with each sprint. 3. MSF for CMMI Process Improvement 2013 - Choose CMMI if your organization triages bugs separately from the product backlog, resolves work items before closing them, and tracks changes to requirements formally. The CMMI template is designed to support formal change management processes.TRANSCRIPT
Agile Project Management -Visual Studio Team Foundation Server 2013
Om Prakash Bang, PMP, PMI-ACP, CSM, CSP, PSM1
Why Agile? Agile Planning How do you do it ?
Why Agile?
Copyright © Microsoft Corporation 2014
Agility #1
% of respondents indicating their firms strategy is based on …
http://www.mckinsey.com/insights/strategy/putting_strategies_to_the_test_mckinsey_global_survey_results
How well a firm executes business strategies is tied to
how good it is at creating and managing applications.
David Chappell
BUT
Custom software development is difficult, takesa long time, costs a lot of money and often fails!
The Voice of Experience
BACKLOG
REQUIREMENTS
Connect Teams. Create Value. Transform Delivery.
Most Value
Minimal Planning
Highest Value
Features
Minimum Viable ProductMinimal Risk
Manage Demandand Define Requirements
Continuous cadence of value delivery
Value
Time spent on planning
Conventional Planning
Value
Time spent on planning
Increased value
over time
Agile Planning
Connect with Customers where they’re at | Help them to transform to agile
OOB Process Templates (CMMI, Agile and Scrum)
