This is a dedicated training page

Meeting evolving stakeholder needs, managing tight budgets, and ensuring compliance and public accountability requires a modern approach to requirements management. Security, efficiency, and reliability are cornerstones of Modern Requirements4DevOps which is built on Microsoft’s leading Azure DevOps.

Modern Requirements4DevOps logo

Agile Use Cases

UC ID: A1.0

Agile product backlog and sprint schedule setup

Setting up a Product Backlog in Azure DevOps starts with setting up a Process Template.
Azure DevOps provides a flexible environment where teams can customize the Work Item Types and their properties to a great degree.
Once the Process Template is created, the next step is to setup the Dashboards and Sprints according to your Team’s needs. 

Video 1 - Setting up a Process Template

 

Video 2 - Setting up Dashboards and Sprints

 

UC ID: A1.1

Agile backlog story cards meet "Definition of Ready"

Agile teams need the ability to move requirements into the ‘Ready’ state. 
In Azure DevOps, preparing Agile requirements for an iteration requires the ability to build and import requirements quickly, add tags, make bulk edits, and move requirements to the current iteration easily. When building a review using Azure DevOps, teams need to be able to email requirements, use the discussion to facilitate change, and be able effectively enact those changes and move requirements into the appropriate States and Iterations. 

Video 3 - Adding and interacting with requirements

 

Video 4 - Reviewing requirements using native Azure DevOps

 

Video 5 - Importing requirements from Excel

 

UC ID: A1.2

Agile backlog story cards meet "Definition of Done"

Completing requirements requires the ability to work directly with your Agile team to complete the requirements. 
When working within Azure DevOps, this means your developers need to be able to create requirements tasks and move them through the life cycle. As requirements get broken down into tasks, developers need a reliable way to add bugs and test cases to requirements, and to connect with BA’s. Azure DevOps provides a simple interface to build tasks, test cases, bugs, and facilitate discussion.   

Video 6 - Moving a requirement's tasks through the life cycle

 

UC ID: A2.0

Reusing requirements in Azure DevOps projects

It is common for the requirements of one project to be a good fit for reuse in another project. 
Reusing requirements within Azure DevOps is simple, and is presented in three separate ways in the video below. Teams can choose to clone a requirement in the same project, copy a requirement directly to another project, or reuse an entire Baseline of requirements using the Modern Requirements4DevOps Baseline module. 

Video 7 - Reusing requirements in Azure DevOps

 

UC ID: A3.0

Agile product backlog restrict access

Azure DevOps allows administrators of projects to set up restrictions. 
The options provided for restricting access offer teams full control of their project at a granular level. 

Video 8 - Restricting access to your Azure Devops project

 

UC ID: A4.0

Agile product backlog out of the box and custom queries / reports

In Azure DevOps, the Query tool remains the most powerful feature teams can use. 
The built-in query tool allows teams to find and store information from a project and collection. The query tool is used extensively in Modern Requirements4DevOps, where we allow you to quickly output Smart Docs, do Document reviews, output work items, and build advanced reports to meet every need.

Video 9 - Report requirements from Azure DevOps

 

Waterfall Use Cases

*Some Use Case Videos have been reused as the process of completing that Use Case is the same for both Agile and Waterfall teams.*

UC ID: W1.0

Waterfall product backlog and sprint schedule setup

Setting up a Product Backlog in Azure DevOps starts with setting up a Process Template.
Azure DevOps provides a flexible environment where teams can customize the Work Item Types and their properties to a great degree.
Once the Process Template is created, the next step is to setup the Dashboards and Sprints according to your Team’s needs. 

For Waterfall Teams, the types of Work Items might vary to include Business Rules, formal Change Requests, and more. 

Video 1 - Setting up a Process Template

 

Video 2 - Setting up Dashboards and Sprints

 

UC ID: W1.1

Waterfall Project Requirements Workflow

Waterfall teams typically subscribe to a model of building the highest level of requirements, having them approved, and then breaking them down into lower level requirements. It is common for teams to consider the points of approval to be a “tollgate” that dictates the start of next stage of the requirements lifecycle. 

With Modern Requirements4DevOps, teams can control the approval of requirements by first having Stakeholders facilitate requirements change using comments, and then switching them to Approvers for final approval. The act of sending a group of requirements for Review or Approval can be done from the Native Azure DevOps Modules (Sprints, Backlog, Queries), as well as through Smart Docs and the Review module. 

Watch the video below to see how the review process can be created using Modern Requirements4DevOps. 

Video 3 - Building Reviews using Modern Requirements4DevOps

 

UC ID: W2.0

Waterfall Requirements Reusability

It is common for the requirements of one project to be a good fit for reuse in another project. 
Reusing requirements within Azure DevOps is simple, and is presented in three separate ways in the video below. Teams can choose to clone a requirement in the same project, copy a requirement directly to another project, or reuse an entire Baseline of requirements using the Modern Requirements4DevOps Baseline module. 

Video 4 - Reusing Requirements in Azure DevOps

 

UC ID: W3.0

Waterfall Project Setup Restrict Access

Azure DevOps allows administrators of projects to set up restrictions. 
The options provided for restricting access offer teams full control of their project at a granular level.

Video 5 - Restricting Access in Azure DevOps

 

UC ID: W4.0

Waterfall Out of the Box and Custom Queries / Reports

In Azure DevOps, the Query tool remains the most powerful feature teams can use. 
The built-in query tool allows teams to find and store information from a project and collection. The query tool is used extensively in Modern Requirements4DevOps, where we allow you to quickly output Smart Docs, do Document reviews, output work items, and build advanced reports to meet every need.

Video 6 - Report requirements from Azure DevOps

 

UC ID: W5.0

Waterfall - Use Case & Use Case Diagams

Building Use Case models can allow teams to easily recognize a process, system, or solution. 
For this reason we allow you to take two different approaches to building a Use Case. 
You can either write your Use Case as a textual narrative, or create a Use Case diagram that can be published as a textual narrative. 

Video 7 - Building Use Case models using the Use Case module

 

Video 8 - Building Use Case models using the Diagram module

 

UC ID: W6.0

Waterfall - Orphaned Requirements

Identifying orphaned requirements in Azure DevOps can be a simple task. 
Being able to properly manage these orphaned requirements quickly and effectively is another story. This is why we provide the ability to add your orphaned requirements into a traceability matrix and easily visualize what relationships need to be created. 

Video 9 - Managing orphaned requirements in Azure DevOps

 

UC ID: W8.0

Waterfall - Version Control in Azure DevOps

Azure DevOps excels at version control. 
By creating a version of work items anytime they are saved, Azure DevOps provides incredible traceability of work item changes. Without Modern Requirements4DevOps however, the changes are difficult to represent in a digestible manner. This is why we allow you to easily create Baselines of groups of requirements to identify, and manage, the changes that are happening in your project. 

Video 10 - Version control using the Baseline module