Process Template

BABOK

The BABOK process template was developed in collaboration with IIBA in order to align with the practices outlined in their BABOK V3 guide. It is designed to support multiple levels of TFS work item types (WITs), including: Business Requirements, Stakeholder Requirements, Functional, Non-Functional and Transitional Requirements. It helps users to plan, track, and link their requirements, tasks, tests, bugs, feedback, and code review.

These work items and other related work items with their associated properties, are all instantiated when you create a team project using the BABOK process template. This template provides a rich environment in which Business / Systems analysts can create, manage and collaborate on requirements, following guidelines suggested in IIBA’s BABOK V3 guide.

Scrum

Choose Scrum when your team practices Scrum. This process works great if you want to track product backlog items (PBIs) and bugs on the Kanban board, or break PBIs and bugs down into tasks on the task board.

This process supports the Scrum methodology as defined by the Scrum organization.

Tasks support tracking remaining work only.

Agile

Choose Agile when your team uses Agile planning methods, including Scrum, and tracks development and test activities separately. This process works great if you want to track user stories and (optionally) bugs on the Kanban board, or track bugs and tasks on the task board.

You can learn more about Agile methodologies at the Agile Alliance.

Tasks support tracking Original Estimate, Remaining Work, and Completed Work.

CMMI

Choose CMMI when your team follows more formal project methods that require a framework for process improvement and an auditable record of decisions. With this process, you can track requirements, change requests, risks, and reviews.

This process supports formal change management activities. Tasks support tracking Original Estimate, Remaining Work, and Completed Work.

Top