Managing Suspicious Requirements with Automatic Flagging

Managing Suspicious Requirements with Automatic Flagging

Dirty Flag / Suspect Link is a component of MR Services (formerly called MR Agent) that is used to identify work items that might be affected by the changing of a linked work item so that relevant stakeholders may review the impacted work items. For example, if a user story changes in the active states, then the related test cases would be marked as suspect.
 
The Suspect Link feature contributes to your project’s success by making the impact of Work Item changes both query-able and, generally, more noticeable. You can consider this feature as one method of doing an impact assessment on changing work items within your project.

How does Dirty Flag / Suspect Link work?

This feature works by allowing you to monitor Work Items which meet certain preconditions. When these Work Items change, the monitor feature will mark any linked Work Items as suspect.

Let’s consider an example:

User Story 1 has just been moved to the ‘Completed’ state. If the Suspect Link can be configured to trigger a flag if any changes are made to user stories in a “Completed” state (i.e. a change to a field such as ‘Description’).

This means that if User Story 1’s Description field is changed in the future, it will flag all of the requirements that are linked to it with a Dirty Flag.

This allows your team to easily identify if a requirement that matches a certain set of criteria (which you specify) changes. Once identified, the configured work items directly linked will be flagged by the Dirty/Suspect.

To continue with our example, if User Story 1’s Description field changed, we could Dirty Flag all of the directly linked Test Cases that might need to be changed to test the new criteria changes.

The Dirty Flags that get set on those Test Cases would take the shape of a Work Item tag.

Tags show up in the Standard Work Item editor of Azure DevOps. You can also personalize the Column Options in the Work Items and Backlogs module to view a group of Work Items in which some may be marked by the Dirty Flag.

In the case of the Dirty Flag tag that is set on Work Items, the tag that is applied includes both the changed Work Item’s ID, and revision, so that your team can easily identify which requirement was it that changed and fired the Dirty Tag / Suspect Link functionality.

Dirty Flag tags could be manually removed when relevant stakeholders have reviewed the impact and made necessary updates. The best practices we recommend here is to add another comment explaining that now the Dirty Flag is removed due to necessary updates have been accomplished or no updates are required.  

For more details and the configuration process of Dirty Flag/Suspect Link, please watch the video.

 
Try it Now!
Facebook Twitter Linkedin
Time to Read: 20 minutes

How to Make Your Requirement IDs More Descriptive and Distinctive Using Custom ID

How to Make Your Requirement IDs More Descriptive and Distinctive Using Custom ID

Modern Requirements4DevOps offers the functionality to add Custom ID’s to Work Items. The intent of this feature is to make a Work Item field more readable and recognizable. For example “PX-REQ-00001” for the first requirements work item in Project X.

Our Custom ID feature offers the same benefits alongside the added benefits of using the Custom ID in the Queries module.

Custom ID’s can be setup as a custom property that exists on each of your Work Items. The Custom IDs is not designed replace the work item ID, instead it complements it.

The Custom ID property offers an easy method of identifying several necessary information of a given Work Item all within one field. It also proves to be an incredibly useful tool for identifying a requirements source in cross-project queries.

By allowing you to consolidate the information into one field you make a Work Item more approachable to less involved users. The Custom ID capability adheres to the following guidelines:

Work Items can be assigned a unique code based on different Work Item types. For example, a Requirement Work Item type’s code could be REQ, a User story Work Item type’s code could be US, and a Bug Work Item type’s code could be BG.

You can create the starting number that your Work Item types will increment from thereafter. For example, you can dictate that User Story Custom ID numbering should start at 1 or 10000 and it will increment every User Story’s Custom ID by thereafter.

You can also add an optional project prefix for any Custom ID. For example, a project name such as “Project X” could have the prefix PX assigned to it.

Finally, you can choose to include the Scope of any Work Item. The ID number is not repeated in the scope; the scope can be Team, Project or Collection. Scope guarantees the custom ID will be unique within the scope.

Using the example covered in the above guideline, a Custom ID for the first (00001) Requirement Work Item in Project X would be “PX-REQ-00001” – which is a concatenation of the project prefix + Work Item type code + number.

For more details and the configuration process of Custom ID, please watch the video.

 
Try it Now!
Facebook Twitter Linkedin
Time to Read: 20 minutes

Digital Project Manager: An Overview of Modern Requirements4DevOps

The Digital Project Manager: An Overview on Modern Requirements4DevOps

Detailed Overview & Explanation Of Requirements Management Features

What is Modern Requirements4DevOps?

What is Modern Requirements4DevOps? Read on to discover how Modern Requirements4DevOps works—what problems it can help you solve and who uses it, along with a tour of its features, pricing, and integrations.

I’ll also explain how Modern Requirements4DevOps compares to similar tools.

Read the full article on Digital Project Manager.

Facebook Twitter Linkedin

Now Released: Modern Requirements4DevOps 2020

Now Released: Modern Requirements4DevOps 2020

Details of Modern Requirements4DevOps 2020's Core Enhancements!

User friendly, short cycle times, ability to author requirements online, compliance reporting, and reduced development rework. These are just a few of the phrases that have been used by our customers to describe the aptitude of several modules within the Modern Requirements4DevOps application. New features and enhancements have been made to the modules with our 2020 release.

Here we will share a few highlights made to a few of our modules within Modern Requirements and some tool enhancements for your convenience. Modules that we will be outlining are:

  1. Rights Management
  2. Review Enhancements
  3. Smart Docs Enhancements
  4. Smart Reports Enhancements
  5. Baseline Enhancements
  6. MatCal (New!)

 

1. Rights Management: You asked, and we listened. You can now manage User Access. A user (must have collection/project Admin) rights can now manage user access to both modules of Modern Requirements4DevOps, and the features within each module. Setting these permissions is as easy as one-two-three… steps to set permissions:

  • Access your project
  • Go to Project Settings
  • Scroll down to Extension > click on Modern Requirements4DevOps

This is what you will see:

From this screen, you will be able to set the *Group and/or *Team permissions (located on the left panel). There are two ways to set permissions, you can either do it in the “*Common Settings” or within “*Modern Requirements4DevOps Modules” individually (located on the right panel of the permissions tab). Here you can set permissions for the features of each modules.

The permission options available are:

  1. Create/Edit Folder
  2. Delete Folder
  3. Create/Update Artifact
  4. Delete Artifact
  5. Create/Update Meta Template
  6. Save as Template
  7. Smart Reporting
  8. Report Designer

Currently, Rights Management is supported for three modules: Smart Docs, Baseline and Reporting.

Rights Management Video

For further details on what’s new in Rights Management and its functionality please refer to the video.

 

2. Review Enhancements: The Review module allows you to communicate, review, and approve within the project environment and facilitate change when necessary. Enhancements have been made to Review module. Here is a list of a few of the new features:

  • Read-only rights to non-participants of review
  • Auto Bulk generation of review Audit Reports
  • Audit Reports Format- Word/PDF

Read-only rights to non-participants of review: With this enhancement you now have the ability to configure rights for non-participants where they can view review details in read-only mode.

Non-participants users: Users that are neither the approver nor the reviewer.

Auto Bulk generation of review Audit Reports: This enhancement will allow you to generate Audit Reports of all reviews in a project at once in bulk or project wise from admin panel.

You can select project(s) and provide details here to generate the audit reports of their existing reviews automatically

Audit Reports Format – Word/PDF: System now gives you the ability to select format in which you want to generate the audit reports in. You can select either word or PDF version.

The purpose of Approval Audit report is to provide details of all the work items in a Review. It provides complete status regarding who has approved or rejected the review work items along with the comments and decisions

How to configure settings:
  • Go to Admin/Collections Setting
  • Scroll down to Extensions
  • Choose Modern Requirements4DevOps2020
  • Go to Review tab (look for the option you want to make the changes to)
Note: For a detailed list of enhancements and new features please refer to “Modern Requirements4DevOps 2020 Release Notes” under Review Management (page 10).

Review Management Video

For further details on what’s new in Review Management and its functionality please refer to the video.

 

3. Smart Docs Enhancements: Smart Docs is a tool that bridges the gap between document and information management by authoring requirements in a document view online. New features have been added to Smart Docs, some of the highlights are as follows:

  • Full Screen Support
  • Right Panel UI Update
  • Inherit Parent Properties Update

Full Screen Support: In order to have a better user experience and larger display you can now view Smart Docs in full screen mode.  Which means a better view when building your online requirement documents.

Right Panel UI Update:

  • For your convenience a cross icon has been added to the right panel UI. Which means you can now close the right panel directly through the panel itself.
  • If this was not enough, we have also added expand/collapse capability to the “*find” query area for a better user experience.
  • Also, in order to provide more space to show more work items, “Add child/sibling” and “Select all/ unselect all” buttons have been removed. Remember, you can still drag and drop your work items into the document section.

Inherit Parent Properties Update: This is an update with which by default, the check box to inherit parent work item properties in child work item will be shown ‘un-checked’. 

Note: If no properties are selected from the drop-down option, then no properties will be inherited in the child work item.

Smart Docs Video

For further details on what’s new in Smart Docs and its functionality please refer to the video.

 

4. Smart Reports Enhancements: Smart Report enables users to format their reports according to the work items structure. It is accessible from many of the ADO and Modern Requirements4DevOps modules. Here is a list of some of the tool enhancements made to Smart Report module:

  • Upload macro-enabled Word template
  • Retain selection of last uploaded Word template
  • Retain selection of last Smart Part

Upload macro-enabled Word template: Smart Report now allows you to upload and execute Macro-Enabled Word document (.docm) as well as Macro-Enabled Word Template (.dotm) files in Smart Report through “Upload word template”. It will make your user-friendly option of uploading word templates even more of a breeze.

Retain selection of last uploaded Word template: Guess what… Smart rReport has now become smarter, it will now retain the last selection that you made while uploading your word template. 

Retain selection of last Smart Part: Well we did not stop at remembering the last selection for the word template… Enhancements have been made where the system will now also retain the selection of your last Smart Report Part as well. Well, it is winning all the way for report creators.

Smart Report Video

For further details on what’s new in Smart Reports and its functionality please refer to the video.

 

5. Baseline Enhancements: Baseline allows you to take a snapshot of your requirements at a point in time to allow better control and track changes. Here is how it will make your work experience even better:

  • Retain work item selection on tab switching
  • Comparison ID on Baseline comparison

Retain work item selection on tab switching: System will now remember the last work item selection when navigating between different tabs within baseline. What does that mean?  Well, while working with a baseline (specially with a large one), navigate to Compare or Detail tab and back to View tab if you have forgotten which work item you were working with…  Worry no more, because the system will remember it for you.

Comparison ID on Baseline comparison: Enhancements have been made so you can now view work item revisions only where work items exist within both baselines being compared. For example: if a work item doesn’t exist in one of the baselines, no revision ID will be displayed, instead “-” will be displayed in Rev.ID or Comp.Rev.ID column. This rule will also be applied in the difference report.

Baseline Video

For further details on what’s new in Baseline and its functionality please refer to the video.

 

6. MatCal (New): A new feature has been introduced to Modern Requirements to perform mathematical and logical expressions. Sounds exciting? Well, we are excited about it. Here’s why:

  • It will allow you to have work items field(s) automatically calculated based on input of other field(s) of the same work item(s)
  • It can be applied to any work item fields, including numerical, Boolean, and textual types of work item fields

What you need to do: Provide your formulas to a Modern Requirements Customer Success team member and we will be happy to configure it on your behalf.

MatCal Video

For further details on MatCal and its functionality please refer to the video.

 

 

 

 

 
For a detailed list of all enhancements and features please made in 2020 release, please refer to Modern Requirements4DevOps 2020 Release Notes.

We are excited to announce that Modern Requirements4DevOps 2020 is now available for download!

Introduction to Rights Management

Introduction to Rights Management

What is Rights Management?

Rights Management is a new feature in MR2020 Release to control user access. The project administrator can grant or deny a group of users from accessing an MR module and its functionalities. Currently, Rights Management is available for three MR modules: Smart Docs, Baseline, and Reporting.

The Benefits of Using Rights Management

Flexible and customizable permissions allow project teams to maintain the appropriate balance of collaboration and control.

Whenever a permission change takes place, it will immediately impact every user team/group that is assigned the permissions. This ensures that permission settings can easily be updated and maintained as projects progress and teams change roles.

How to Access Rights Management

Rights Management can be accessed from the Modern Requirements4DevOps extension under Project Settings.

Group Features

The available features which you can set permissions for varies from module to module.

The available Group Features are as follows:

  1. Create /Edit Folder
  2. Delete Folder
  3. Create/Update Artifact
  4. Delete Artifact
  5. Create/Update Meta Template
  6. Save As Template
  7. Smart Report Generation
  8. Smart Report Designer

Permissions Selections

There are typically three types of permission access to choose from for each group feature:

“Allow”

“Deny”

“Not Set”

  1. “Allow”: Explicitly grants users the permission to access a group feature in MR module(s).
  2. “Deny”: Explicitly restricts users from accessing a group feature in MR module(s).
  3. “Not Set”: Implicitly denies users the ability to access a group feature in MR module(s).

Inherited Permissions

Teams/Groups can automatically inherit permission settings from parent Teams/Groups. Permissions Settings explicitly changed in the child teams/groups may override permissions inherited from parent Teams/Groups. Keep the following rules in mind:

  1. Inherited “Allow” values can be overridden to “Deny”.
  2. Inherited “Not Set” value can be overridden to “Allow” or “Deny”.
  3. Inherited “Deny” value cannot be overridden to “Allow”.

Permission Conflicts

When same user exists in more than one teams/groups, the following rules apply:

  1. “Deny” has preference over “Allow”.
  2. “Deny” has preference over “Not Set”.
  3. “Allow” has preference over “Not Set”.

Please watch the detailed tutorial video on Rights Management!

If you have any questions or thoughts about Rights Management, please contact your Customer Success Representative of Modern Requirements and we will be happy to work with you to explore this feature.
Facebook Twitter Linkedin
Time to Read: 10 minutes

Using MatCal to Perform Mathematical and Logical Calculations in Modern Requirements Management

Using MatCal to Perform Mathematical and Logical Calculations in Modern Requirements Management

What is MatCal?

MatCal is a feature in Modern Requirement4DevOps used to perform mathematical and logical expressions on work items.

Why we need MatCal in Requirements Management

To manage the relationships between work item properties in a smarter way! It eliminates the manual efforts of doing the calculation outside the project environment and avoids risks of introducing incorrect calculation results to your projects.

Let’s look at a simple example here to illustrate a relationship between work item properties.

Business Value and Priority are properties of work item Feature.  Normally, high Business Value leads to high Priority.

With the right configuration, MatCal could help you manage the relationship by automatically assigning Priority value based on the Business Value input.

Industry Use Scenarios

Scenario 1: Automotive Safety Integrity Level (ASIL) in ISO 26262

Scenario 2: Risk rating is automatically assigned according to Severity score and Occurrence score

Scenario 3: Priority rating is automatically assigned according to Severity score and Likelihood score

Please watch the video for extra usage scenarios and tutorials on MatCal!

Facebook Twitter Linkedin
Time to Read: 10 minutes

Reusing Requirements

Requirements Reuse: An Effective Way to Facilitate Requirements Elicitation

Learn how to Reuse Requirements in Azure DevOps

Azure DevOps is an incredible platform that provides a single-source of truth. 
For many teams that statement alone is enough to consider using the world’s leading ALM platform for their requirements management. Being able to tie development tasks to requirements, and those to Test Cases is hard to pass up. 

But what if you don’t need all of the features of a full ALM platform?
What if you only need a solution for your Requirements Management needs? 

You can use all of the rich features of Modern Requirements4DevOps to turn your Azure DevOps project into a full-featured Requirements Management solution. One of these features is the ability to reuse requirements across different projects, collections, and servers using the Modern Requirements4DevOps Reuse tool.

Looking to reuse requirements? 
You’re in the right place. 

What you’ll learn in this short article:

  1. Benefits of reusing requirements
  2. The two types of reusing requirements
  3. How reusing requirements can be used effectively

The Benefits of Reusing Requirements

When we talk about the benefits of requirements reuse there is one thing that needs to be addressed first.

The most common question I get from hardware teams is “How could this possibly benefit teams who aren’t software-related?”

So before we begin, requirements reuse is not just for software teams.

Requirements reuse is a topic that often catches people’s attention.

This is because in the world economy we are seeing companies focusing on given domain or areas within given industries. This leads to companies building products within a specific domain, or around a given solution, and really narrowing in on the few things they can be really successful at.

This means that as you build projects, solutions, or systems, often a team can reuse elements of a previous project. This is where requirements reuse fits into the picture.

By enabling a team to reuse those requirements in the next project they are able to reduce the amount of overhead required in getting started in a new project.

For some people this might already be obvious.

What might not be obvious, however, is that reuse can also be a great way of handling requirements that are scoped above the project level. This would include non-functional requirements, or risks that need to be considered as a company-wide mandate. This would even go so far as to allow your team to reuse requirements whose purpose is strictly regulatory or compliance-centric. This functionality can be extended to software and hardware teams alike and can even help teams product teams devoted to a physical component or deliverable.

 

The Two Types of Reusing Requirements

Reusing Requirements by Reference

Reusing requirements by reference is a quick way to introduce existing requirements to your project by simply building links with them. By doing this, you could have direct access to those work items and review all the associated content, links, and attachments without actually copying them within or across projects.

Reusing Requirements by Reference

 

Reusing Requirements by Copy

In Azure DevOps there is very limited functionality for copying requirements, or other work items, from one project to another. But when you add Modern Requirements4DevOps into your Azure DevOps environment, requirements reuse meets its full potential.

When discussing the Reusing Requirements by Copy, there are three major approaches to consider.

Reusing Requirements by Copy

 

How to Reuse Requirements Effectively

After watching the above videos it is obvious that the Modern Requirements4DevOps Reuse tool is effective for reusing requirements.
It offers full control over the requirements you are choosing to reuse, allows you to apply customization to those requirements, and allows you to link the requirements to the source work item.

This means no matter where you want to send requirements, you can do so using the Modern Requirements4DevOps Reuse tool. But there are some ways that you can use the Reuse tool more effectively. 

The first notable mention is by pairing the reuse tool with the Modern Requirements4DevOps Baseline tool. 

What is a Baseline?
Many teams use Baselines of requirements and don’t even realize they do.

A Baseline is a snapshot of Work Items at a given point in time. 
For many teams they simply use Microsoft Word document versions as a baseline. 

When talking about capturing requirements at a given time, there are many reasons why the Modern Requirements4DevOps feature is better than the traditional Microsoft Word approach. With Modern Requirements4DevOps Baselines, you are able to capture a set of, work items as they were on any date of your choosing.

This means if you want to capture your requirements as they are two weeks ago, you can easily create a Baseline for those requirements on that date. This lends itself directly to the benefits of the Reuse tool added by Modern Requirements4DevOps.

By combining the Reuse tool with our Baseline, you can not only choose the set of requirements you want to reuse but also the version of those requirements as well. This allows you to take the best and most applicable version of your requirements forward to your next project. 

The next notable mention is to use the prefix / postfix / and other operations effectively when reusing requirements.

When reusing requirements, the Modern Requirements4DevOps Reuse tool allows you to customize how the requirements being reused will appear in their destination project. 

The screen which allows you to do this can be seen below:

 

Using the above feature will allow you to easily add a prefix or postfix to the requirements once they reach your chosen destination project. As seen above, you can also choose to send these requirements to a specific area path (like hardware or software for instance), or even into a given iteration so you can decide when these requirements get handled. 

The most commonly used feature in the field options, however, is the ability to add a tag. 
Often when you are sending requirements from one project to another you want to be able to easily identify and trace those requirements in your destination project. Adding a Tag will allow you to do this.

What is the link with Source Work Item Option?

This option allows you to establish a link between the work item you are reusing and the work item you create in your destination project. 

What link does it create? 
It links your new destination work item to your original work item via the “Related” link or any link type that you have configured in the admin area.
In the below image you can see a Test Case I have copied from project to project, using both the prefix “CL- ” and the “Link to source work item” options set.

 

Using the “Link to source work item” feature allows you to easily trace requirements back to where they were pulled from. While there are many use cases for this feature when moving requirements directly from project to project, this more advanced use cases are for when you are moving requirements from a library or repository into a project instead. 

How to merge copied baselines?

Baseline is a very useful tool no matter you want to reuse a single work item or a long list of work items from your source project/library. In Modern Requirements, you could create links between your source and copied works items so that you could locate the origins of these copied work items.

Although there are links in between, the copied work items are still considered to be independent of the source work items, which means any changes you make to either the copied or source work items will not impact their counterpart.

You might want to ask: how to synchronize the changes when necessary? Assume you have a library where all your design specification work items are saved, and you have reused them in 5 different projects. If now you have to modify some designs in the library, and you want all copied design specifications to be synchronized, you can simply use the Merge functionality, which is located under Source Copied Baseline(s) or Target Copied Baseline(s) in the Details tab of the Baseline module.

Baseline is a very useful tool no matter you want to reuse a single work item or a long list of work items from your source project/library. In Modern Requirements, you could create links between your source and copied works items so that you could locate the origins of these copied work items.

Although there are links in between, the copied work items are still considered to be independent of the source work items, which means any changes you make to either the copied or source work items will not impact their counterpart.

You might want to ask: how to synchronize the changes when necessary? Assume you have a library where all your design specification work items are saved, and you have reused them in 5 different projects. If now you have to modify some designs in the library, and you want all copied design specifications to be synchronized, you can simply use the Merge functionality, which is located under Source Copied Baseline(s) or Target Copied Baseline(s) in the Details tab of the Baseline module.

Still remember the definition of a baseline? A snapshot of selected work items at a point in time. So no matter what changes we have made to the baselined work items, the saved snapshot won’t change. So even if we have merged the baselines, the changes are done against the latest versions of the work items, not to the baselines themselves. Sounds like a little bit hard to understand?

Please watch the 5-minute Merge Copied Baselines video.

Merge Copied Baselines

 

Want to experience reuse's full potential?

Try Modern Requirements4DevOps for free today.

We offer you the ability to try our Requirements Management solution in your own Azure DevOps environment, or in an environment we supply that includes sample data. 

Try it today!

Importing Requirements to Azure DevOps

Importing Requirements into Azure DevOps

Learn how to easily import requirements (and some assets) into your ADO project

When moving to Azure DevOps, or when working offline away from your existing Azure DevOps project, you need a way to bring your newly created requirements into Azure DevOps.

Many teams face the issue of getting the requirements they have created in Excel, Word, and elsewhere into Azure DevOps. Luckily there are a few simple ways to do this without having to worry about adding a lengthy copy/paste session to your process! 

In this article, we’ll cover a few different ways to import requirements.

One of these options is free, and some are features provided by adding Modern Requirements4DevOps to your Azure DevOps project. 

The topics in this article are as follows:

  1. Importing Requirements from Microsoft Excel
  2. Importing Requirements from Microsoft Word
  3. Importing Diagrams and Mockups into Azure DevOps

Importing Requirements from Microsoft Excel

Whether you have all or some of your existing requirements in Excel, or you are looking to export requirements from an in-house tool to a .csv file, there is a free way to import your requirements to your Azure DevOps project. 

This is a free solution – provided you already have Azure DevOps and Excel.

The first step is to make sure you have the Microsoft Excel add-in called “Team tab.”

You can download this add-in directly from the link below:
https://visualstudio.microsoft.com/downloads/#other-family

(On the aforementioned page, Azure DevOps Office® Integration 2019 is listed under the Other Tools, Frameworks, and Redistributables section. )

If you clicked the link above, you will have the ability to turn on your Excel team tab. 

When enabled, this extension allows you to connect an Excel sheet directly to a given project in your Azure DevOps Organization. 

When you enable it you will have two primary functions available to you:
1) You will be able to publish requirements to your project from Excel
2) You will be able to pull requirements from your project to Excel

This means you can work on your requirements from either interface and connect the changes to your project. i.e. if you pull requirements into Excel and make changes, you can publish those changes backup to your requirements in your project. 

After you have run the installer you downloaded you are ready to enable the extension.

Enabling the Team tab in Excel:

  1. Open Excel
  2. Create a Blank Sheet 
  3. Click File
  4. Click Options
  5. Click Add-ins
  6. Choose COM Add-ins from the drop down near the bottom of the window
  7. Select “Team Foundation Add-In and select Okay. 
If you have issues with this process, follow this link.
 
If you now see the Team tab in Excel, you’re ready to import requirements! 

Using the Excel Team tab

In this video, we cover how your team can use the Import capabilities provided by the Excel Team tab Add-in.

 

Importing Requirements from Microsoft Word

The second way to import requirements into your project is through Microsoft Word. 

This feature is a “Preview Feature” available with any Enterprise Plus Modern Requirements4DevOps license. This means any user in your organization with an Enterprise Plus license will be be able to access and use the Word Import Feature. 

If you aren’t currently using Modern Requirements4DevOps, you can try this Word Import Feature by trying Modern Requirements4DevOps today!

Give it a try!

So how does Word Import work? 

Warning: As a Preview Feature, you should expect that this might not be prettiest solution, and will typically require some coding knowledge. But not much – and if you can borrow a developer familiar with xml (or any other scripting language) for 20 minutes, you should be just fine.

Word Import works by having a well-formatted Word document which uses different Headings to represent the different Work Items / Requirements and their properties in your document. 

For example, let’s take an example of a BRD you might already have in Word format.

You likely have your Introduction, Overview, Scope, and other context elements using the style of Heading 1. 

You might then have your Epics, Features and User Stories in this document as well. Your document might look like this:

Heading 1 – Introduction
-> Paragraph – All of the text for the Introduction goes here…

Heading 1 – Overview
-> Paragraph – All of the text for the Overview goes here…

Heading 1 – Scope
-> Paragraph – All of the text for the Scope goes here…

Heading 1 – Requirements
-> Heading 2 – Name of Epic
–> Heading 3 – Name of Feature
—> Heading 4 – Name of User Story
—-> Paragraph – Description of the User Story above

Now, your document might be a little different but that’s okay. The principles you are about to learn are the same. 

Word import requires a document (shown above) and a ruleset (explained below).

Typically an admin will create a ruleset that your team will use for importing documents, and it will only have to be done once. So if you have a document already created and your admin has created a ruleset you’re good to go. 

If your admin needs to create a ruleset, read on. 

Creating a ruleset is incredibly simple and is done by editing an XML file. 
The XML file you create will determine how the Word Import tool parses your document for:
1) Which pieces of the document are work items?
2) Which pieces of the document are properties of a given work item?

If you are working through this in real-time, it might help to download this ruleset file as a starting point and watch the following video:

Using the Sample Ruleset to Start

In this video, we cover how to use the sample ruleset file to import a simple requirements document. Please remember creating a ruleset is typically a one-time process. 

 

Importing Diagrams and Mockups into Azure DevOps

Diagrams, Mockups, and Use Case models can be incredible tools for authoring and eliciting requirements. 

This is why with Modern Requirements4DevOps, your team can easily build all of these visualizations directly from within your project. This allows you to benefit from a single-source of truth model where everything is built into your project. 

But maybe you already have Diagrams and Mockups that you would like to add to your Azure DevOps project and connect to requirements. Is it possible to import these assets?

The answer is yes.

Both our Mockup tool and our Diagram tool will allow you to easily bring existing Mockups or Diagrams into your Azure DevOps project. 

To do this, simply save your asset as a .png or .jpeg file from your chosen Mockup/Diagram tool. 
You can then upload your created asset to either the Modern Requirements4DevOp Simulation tool (mockups) or Diagram tool (diagrams). 

You might be thinking, but if we upload it as .png or .jpeg then how can we edit our Diagrams and Mockups? Well, you can’t. But there’s a reason you should do this even still. 

If you want to connect a single Diagram to 25 requirements without using Modern Requirements, you will have to open all 25 requirements and connect them to each individual requirement. 

When you update your Diagram in the future, you will have to reopen all 25 requirements and change the attachment. 

With Modern Requirements4DevOps however, you are able to create a Diagram work item that you can link all of your necessary requirements directly to using the right panel. This means you will be able to have your Diagram in one place, and when that Diagram needs updating, you can easily add in your updated image, and connect your attachment to that single work item. 

Conclusion

In this article we covered three distinct ways that you can import both requirements and their assets to your Azure DevOps project. 

You can import requirements through Excel or Word, or import your existing Diagrams and Mockups. 

If you are interested in using Modern Requirements4DevOps to support your requirements management process, consider giving our product a try here!

Facebook Twitter Linkedin
Time to Read: 10 minutes

The FAQ Module

The FAQ Module

The solution for upfront requirements gathering

In this article we cover the features and benefits of the FAQ module.

This module was designed to help teams who gather requirements at the start of their requirements management process. By creating question lists teams can easily capture and reuse their knowledge of the elicitation process to ask the right questions that yield the best requirements.

What is the FAQ module?

The FAQ module is a repository of question lists that your team can construct, edit, change, template, and use to elicit requirements. By using the FAQ module to build up a knowledge base for your team, you can be confident that any team member can engage with stakeholders in an effective manner.

By building the best set of questions on that domain, your team can ensure that they are always eliciting the best possible set of requirements.

The main benefit of this module is that it allows your team the opportunity to build up a knowledge base that can be used by both experienced BA’s, as well as by those who might need to elicit requirements in an unfamiliar domain. The FAQ module comes already stocked with over 3000 questions that cover many different topics.

These topics include multiple ISO Compliance templates, as well as templates on Non-Functional Requirement topics such Scalability, Reusability, or Operability that can be used for elicitation.

For many teams this module will replace their Excel-based question lists they may have used in the past.

To stay in line with the other modules in the Modern Requirements toolset, the FAQ module takes what used to be a disconnected process and connects it directly with your project. This means your teams can easily add requirements into your project simply by supplying answers to the questions in your FAQ question list.

What Value does the FAQ module offer?

The value of our FAQ module can be described in two simple points.

  • The FAQ module helps create better requirements by guiding the elicitation process, leading to a greater likelihood of project success.
  • The FAQ module reduces the time spent on elicitation throughout your project, allowing your team to get started building sooner.

By using the valuable knowledge of experienced BA’s, you can create domain-specific question templates that help structure the elicitation process. This means you can send any BA of any experience level into a room with a stakeholder and feel confident they will create complete and actionable requirements.

By no longer needing to construct question templates and then copy elicited requirements to your RM tool, your team can move through the elicitation process faster. This means more time spent iterating on more accurate requirements and less time spent copy and pasting user stories that are likely to need more work.

What are the Use Cases for the FAQ module?

When we talk to our community about their use of the FAQ module, they often describe the ways in which this module has streamlined their process and made the elicitation phase of projects easier to navigate.

Even with teams who traditionally don’t use question lists, after joining our community they will tell us how much added value they see from being able to consolidate the knowledge of everyone on their team into one cohesive list.

Here are the Use Cases we have seen for the FAQ module.

USE CASE 1

My team currently gathers requirements up front and moves iteratively through our project thereafter. We currently use Excel during the requirements gathering phase, but it means that we are copying requirements to our tool of choice afterwards.

By being a team who gathers requirements up front, this provides a perfect opportunity to use a question list designed for that domain. But using Excel as a means of facilitating this question list is a recipe for a long copy-paste process later down the road. 

Copy/paste processes are generally error-prone and lengthy. It is often during these already long copy/paste processes that a team member will recognize they have missed a property of a work item that they need stakeholder input on.

In this case, using the FAQ module means you will have the question list in your Azure DevOps project already. When you ask your Stakeholder your question you will be able to answer that question in your FAQ question list and it will automatically create a requirement for you.

You can then open that requirement directly and pursue any follow up questions that you might have while you are still with your Stakeholder. This saves time and makes the elicitation process more thorough, while preventing your team from missing opportunities to get the right information at the right moment.

USE CASE 2

My team works in a compliant/regulated space and we need to ensure we are building the full set of requirements to remain compliant and auditable.

One of the best features of the FAQ module is that you can use many of our pre-built compliance-related templates to elicit requirements. Our pre-built templates have been created in partnership with many of our existing customers, as well as through partnerships with thought-leaders in these spaces.

In this case, teams with access to the FAQ module can speak to domain experts and consultants and build the question list that will help them create all the requirements necessary for compliance and regulation. Once created, these question lists can be reused in several projects and can be deployed again and again.

 

How do I use the FAQ module effectively?

The FAQ module provides incredible benefits for teams inside the elicitation phase of their project. Here are some of the ways you can use the module to facilitate project success.

 

Use the Pre-built Question List Templates

When users need a template on either Non-Functional Requirements, or on ISO topics, they can get started quickly by using one of our built-in templates. These templates already contain many of the most important questions about these topics. Users can start with a pre-built template and remove questions that are not relevant and/or add in new questions that necessary.

Build your own Question List Templates

If one of our pre-built templates does not satisfy your need, teams can easily build question lists from scratch. By starting with a blank template, your team can easily build up a comprehensive set of questions that make eliciting requirements a simple and more efficient process.

Once a question list is built it can be reused across projects to help with your elicitation phase down the road.

Build Question Lists that less experienced members of your team

By building question lists you are effectively providing guidance for any member who might be less familiar with a domain, solution, or system. These lists are then a great tool for guiding newer BA’s, or experienced BA’s from a different domain, during the elicitation phase. Teams understand that the quality of the questions we ask at the start of a project directly reflect in the quality of the requirements we elicit.

By building question lists with our FAQ module, you can ensure that you are getting the best possible requirements the first time.

Facebook Twitter Linkedin
Time to Read: 5 minutes