BABOKAzure DevOps Server Process Template



TFS 2017 |Azure DevOps Server 2015

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 ofAzure DevOps Server 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 user 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.

Process Area BABOK
Workflow States
  • Proposed
  • Active
  • Resolved
  • Closed
Portfolio Backlog (1)
  • Business Requirement
  • Stakeholder Requirement
Requirement Backlog (2)
  • Functional Requirement
  • Non-Functional Requirement
  • Transitional Requirement
Task and iteration planning (3)
  • Task
Bug backlog management
  • Bug
Project management
  • Issue
  • Risk
  • Review
  1. User can define Business Requirement and Stakeholder Requirement WITs using the Portfolio Backlog. The Portfolio Backlog page shows a single view of the current backlog of work that can be dynamically re-ordered and grouped. With portfolio backlogs user can define a hierarchy of backlogs to understand the scope of work across several teams and see how that work rolls up into broader initiatives.
  2. User can create Functional Requirement, Non-Functional Requirement or Transitional Requirement WITs and link them to backlog items to manage the portfolio backlog. Product Owners can quickly prioritize work and outline dependencies and relationships
  3. User can define tasks using the Sprint backlog and task board. The sprint backlog page reflects—in real time—the data user input. Data includes work items assigned to the iteration path, remaining work, individual work capacity, and work interruptions both for the team and individuals. Teams can get instant feedback on the rate of burndown and where they are over capacity.
Fill out my online form.

By submitting this form, you agree to receive emails from Modern Requirements. You understand that you will be subscribed to the Modern Requirements monthly inbound marketing newsletter and periodic offers for additional content and/or services. Your consent can be withdrawn at any time using the links provided in every email.
All information is confidential and for company use only.