Requirement Management

Introduction to Requirement Management

• Requirement is a process of documenting, analyzing, tracing, prioritizing actions and needs to meet certain business objectives. 

• The purpose of requirements is to ensure that the organization validates and meets the needs of its customers.  A Requirement can be created from an Idea, Demand, Portfolio, and from a Task within a Project. 

• Requirements are group of tasks or conditions that must be completed to finish the project successfully. 
  The requirement life cycle is described below:
  1. Begins with the representation of specific business needs.
  2. Continues through the development of a solution.
  3. Ends with a solution that represents it.

Diagrammatic Representation of Requirement Life Cycle 

Create a Requirement from Demand Management

1. Log in to Fusion Agility Suite and navigate to Create tab. 
2. Click on Create >Demand. Follow Demand Management for more information.

3. Once Demand is created open the Demand. Requirement console will be displayed click on “+ Add Requirement”. 

   
   

   
   

4. Enter the field parameters:

   Field	Description
   Summary (required)	Enter a Summary of the Requirement which can describe the purpose behind a Requirement.
   Description	Describe the Requirement with more details. This is a special type of field which supports basic formatting, images, tables, hyperlink.
   New Business Impact (required)	Values are: High, Medium, Low, n/a (Not Applicable)
   Customer Impact	Values are: High, Medium, Low, n/a (Not Applicable)
   Type (of requirement)	Values are: Functional, Issue, Bug “Functional” - Functional change “Issue” - A change is requested from an issue “Bug” - A change that gets raised by a customer which turns into a requirement
   Priority	Defines the priority of Requirement Values are: Critical, High, Medium, Low
   Demand	“Demand Name” will be displayed from which the Requirement will be derived.
   Required Skill	Architect, Developer, Manager, Tester (These are examples and are configurable as per business needs.)
   Estimated Effort (h)(required)	Tentative efforts that are required for completion.
   Attachments	Can associate attachments, videos for a better understanding of the requirement.
   Benefits	Some advantages of implementing the Requirement can be added. This is a special type of field which supports basic formatting, images, tables, hyperlink.
   Problem Solved	Some problems that will be solved from this requirement can be added. This is a special type of field which supports basic formatting, images, tables, hyperlink.

5. Click on the save action button to save the requirement. A new requirement will be created and it will appear on the corresponding Demand - Requirements tab.

6. Added requirements are displayed below:

   

   
   

Edit a Requirement from Demand

1. Click on the Requirement from the Demand - Selected Requirement will be open in Edit mode.
2. Click on Edit button highlighted below.
   
   
   
   

3. Fields that can be edited are:

   Field	Description
   Summary (required)	Enter a Summary of the Requirement which can describe the purpose behind this Requirement.
   Status	This is a Selection field where a list of all status values will be displayed. Demand Manager has control over this field. Based upon the data which will be entered for the Requirement Status life cycle will proceed.
   Description	Describe the Requirement with more details. This is a special type of field which supports basic formatting, images, tables, hyperlink.
   Problem Solved	Some problems that will be solved from this requirement can be added. This is a special type of field which supports basic formatting, images, tables, hyperlink.
   Benefits	Some advantages of implementing the Requirement can be added. This is a special type of field which supports basic formatting, images, tables, hyperlink.
   Attachments	Can associate attachments, videos which for a better understanding of the requirement.
   Customer Impact	Values are: High, Medium, Low, n/a (Not Applicable)
   Required Skill	Architect, Developer, Manager, Tester (These are examples and are configurable as per business needs.)
   New Business Impact	Values are: High, Medium, Low, n/a (Not Applicable)
   Estimated Effort(h) (required)	Tentative efforts that are required for completion.
   Type of requirement	Values are: Functional, Issue, Bug
   Priority	Values are: Critical, High, Medium, Low

4. Click on the Save action button to save the changes.  

Create a Requirement from Portfolio

1. Go to the Portfolio console as a Portfolio Manager to add new requirements. Click on “+Requirement” to create requirement(s).
   
   
   
   

2. Fields to be added are:

   Field	Description
   Summary (required)	Enter a Summary of the Requirement which can describe the intention behind this Requirement.
   Description	Add details of the Requirement. This is a special type of field which supports basic formatting, images, tables, hyperlink.
   New Business Impact	High, Medium, Low, n/a (Not Applicable)
   Customer Impact	High, Medium, Low, n/a (Not Applicable)
   Type of Requirement	Functional, Issue, Bug
   Priority	Critical, High, Medium, Low
   Portfolio	The name of the Portfolio will be displayed. e.g. Service Desk & Asset Management
   Required Skill	Architect, Developer, Manager, Tester (These are examples and are configurable as per business needs.)
   Estimated Effort(h)	Tentative efforts are required for completion.
   Attachment	Can associate attachments, videos that will be used to understand the requirement.
   Benefits	Some advantages of implementing the Requirement can be added. This is a special type of field which supports basic formatting, images, tables, hyperlink.
   Problem Solved	Some problems that will be solved from this requirement can be added. This is a special type of field which supports basic formatting, images, tables, hyperlink.

3. Save action button saves the New requirement. The Requirement is created it is displayed in Portfolio - Requirement console below:
   
   
   
   

Edit Requirement from Portfolio

1. Click on requirement ID to edit. Once you click on requirement ID requirement will open in the detail pane.
2. Click on the Edit link requirement to open in Edit mode like below:
   

3. Fields to be updated:

   Field	Description
   Summary (required)	Enter a Summary of the Requirement which can describe the intention behind this Requirement.
   Status	Status of Project
   Description	Enter details of the Requirement. This is a special type of field which supports basic formatting, images, tables, hyperlink.
   Benefits	Enter benefits of Requirement. This is a special type of field which supports basic formatting, images, tables, hyperlink.
   Problem Solved	Add problems that will be solved from this requirement. This is a special type of field which supports basic formatting, images, tables, hyperlink.
   Attachment	Can associate attachments, videos that will be in use to understand the requirement.
   New Business Impact	High, Medium, Low, n/a (Not Applicable)
   Customer Impact	High, Medium, Low, n/a (Not Applicable)
   Type	Functional, Issue, Bug
   Priority	Critical, High, Medium, Low
   Required Skill	Architect, Developer, Manager, Tester (These are examples and are configurable as per business needs.)
   Estimated Effort (h)(required)	Tentative efforts are required for completion.

4. Save action button will save the changes made to the requirement.

Create Requirements from Project - Tasks in Sprints

1. Create Project>Once Project is in Plan/Prepare state, Sprints, and Tasks can be added.
2. Add Sprints. After adding Sprint – Select the Sprint and click "+New Task".
   
   
   
3. Create Task dialog is displayed as below: 
   
   
   
4. It provides users the flexibility to create New Requirement from the "Create Requirement" field with selection options - Yes/No. If you select "Yes”, an automatic process is triggered in the background where a new requirement corresponding to that task gets added successfully. This can be visible in the  "Tasks in Sprints" tab like below:
   
5. Click on the Requirement ID to open the requirement in the details section. Click on Edit as highlighted, to open the requirement in edit mode.
   

6. Fields that can be updated are:

   Field	Description
   Summary (required)	A summary which will have details about the requirement
   Status	Status of Project
   Description	Add details of the Requirement. This is a special type of field which supports basic formatting, images, tables, hyperlink.
   Benefits	Add benefits of Requirement. This is a special type of field which supports basic formatting, images, tables, hyperlink.
   Problem Solved	Add problems that will be solved from this requirement. This is a special type of field which supports basic formatting, images, tables, hyperlink.
   Attachment	Can associate attachments, videos that will be in use to understand the requirement.
   Customer Impact	Values are: High, Medium, Low, n/a (Not Applicable)
   Required Skill	Architect, Developer, Manager, Tester (These are examples and are configurable as per business needs.)
   New Business Impact	Values are: High, Medium, Low, n/a (Not Applicable)
   Estimated Effort	Tentative efforts required for completion
   Type	Values are: Functional, Issue, Bug
   Priority	Values are: Critical, High, Medium, Low

7. Save action button will save the changes. 
8. Project Manager can" View Portfolio" and "View Task" by clicking on the highlighted links:
   

Life Cycle of Requirement based on Idea, Demand and Project Task

If Requirement is created from Idea:

• If a requirement is created from Idea, it is tracked as a part of the Portfolio.
  This requirement is displayed in Portfolio – Requirement tab where the Portfolio is in the “Ramp up” state.
• From this stage of the Portfolio, using the requirement console a new Task will be created, which takes requirement In Backlog state.
• Tasks are now associated with Sprints.
• Resources aligned for the corresponding tasks start respective work and puts the Task “In Progress” which takes the requirement “In Project” state.
• Once all the the Tasks are Done, Sprint and Requirement automatically goes in the Completed state.

If Requirement is created from Demand:

• If a requirement is created from Demand, it is tracked as a part of Portfolio which is created once the Demand is in an approved state. This requirement is displayed in Portfolio – Requirement console where the Portfolio is in the “Ramp up” state.
• From this stage of the Portfolio, from the requirement console, a new Task is created, which takes the requirement In the Backlog state.
• Tasks are now associated with Sprints.
• Resources aligned for the corresponding tasks start respective work and puts the Task “In Progress” which takes the requirement “In Project” state.
• Once all the Tasks are Done, Sprint and Requirement automatically goes to the Completed state.

If Requirement is created from Task - Project:

• For a requirement to be added from Task, first a new Project should be created with the Project Manager assigned and Project should be in Plan/Prepare state for Sprints and Tasks to be added.
• Once Sprints are added Tasks are added and while creating Tasks, we have the option to Create New requirement. If Yes is selected New requirement is created successfully.
• Tasks are associated with “Selected for Sprint” which automatically takes the requirement to the “In Backlog” state.
• Resources aligned for the corresponding tasks start respective work and marks the Task “In Progress” which takes the requirement “In Project” state.
• Once all the Tasks are Done, Sprint and Requirement automatically goes to the Completed state.