Domain 5: Traceability and Monitoring

Nguyen Xuan Tung,

Nov 05, 2016
1
Overview

This domain includes the tasks concerned with managing requirements

throughout the project as well as communicating requirements status to
stakeholders. Much of this domain is described in the Planining domain
with this domain focusing on the execution of those plans.

Wearehere!

2
Overview

The Traceability and Monitoring domain encompasses the business

analysis work of:
Keeping track of requirements
Reporting on their completion
Linking them to each other
and other project components
Assessing the impact of changes

Analysts monitor the solution scope and requirements throughout the

project life cycle and alert or warn the project manager if there are any
potential problems.

3
Why do we need Traceability & Monitoring?

There is one thing in projects (and in life in general) that is

inevitable the change

No matter how much planning, elicitation, review and approval of

requirements you perform as business analyst always expect and
be prepared for a change.

4
Why do we need Traceability & Monitoring?

5
Why do we need Traceability & Monitoring?
Tracing requirements results in many benefits for your project:
Traceability Provides a Double Check
Traceability Allows Impact Analysis
Traceability Keeps the Team Focused

The primary output of Traceability and Monitoring is confidence that

the requirements support the project objectives and will be delivered
in the solution.

6
Who is Involved in Traceability and Monitoring?

Stakeholders involved in Traceability and Monitoring:

1.Business SMEs (internal customers), product owner
2.Solution team (technical architect)
3.Tester
4.Project manager
5.Requester
6.Regulator
7.Sponsor

7
 Who is Involved in Traceability and Monitoring?
Business Analyst Solution team & Tester

1. Keepingtrackofrequirementand 1. Tracerequirementstotheir
reportingtheirstatus,underthe deliverables
directionoftheProjectManager 2. Andmaymaintainsomeofthe
2. Makingsurethatrequirementstieto tracingdetailsthemselves.
businessvalueandthatvalueis
achievedwiththesolution.Tracing
requirementstotheobjectivesthey
supportensurestheyareprovidingthe
businessvaluedesired.

8
Business Analysis Responsibilities in
Traceability and Monitoring
Refer to the business analysis plan to conduct traceability and monitoring
activities
Understand the value of traceabiltity
Share traceability information with the solution team and testers
Resolve requirements conflicts
Make sure all requirements are within the solution scope
Obtain approval and sign-off of requirements from approciate stakeholders
Baseline the solution scope and requirements according to the requirements
management plan
Initiate the change control process to review requests that are outside of scope
or submitted baselining
Perform impact analysis

9
Project Management Responsibilities in
Traceability and Monitoring
Traceability and Monitoring tasks provide business analysis status information
Project Manager assigns the requirement monitoring to business analyst and
ask to regular status reporting on progress
PM expects BA make sure all requirements are within the agreed-upon scope
PM & BA work together to evaluate requirements changes after baselining

Concentrateon: Overseetherequirementswork
Eliciting tobesureitisprogressing
Analyzing accordingtotheproject
Developing schedule.
Andtracingrequirement
Reportingprogress

10
Part 1 Traceability and Monitoring Tasks

The Traceability and Monitoring domain encompasses 5 tasks:

1. Trace Requirements
2. Monitor Requirement Status
3. Update Requirement Status
4. Communicate Requirements Status
5. Manage Changes to Requirements

11
Tasks 1 Trace Requirements

A useful way to view traceability is discovering and maintaining

relationships between important facets of requirements, such as:
Relation to business objectives
Relation of dependency to other requirements
Relation to team deliverables, such as use cases and test cases
Relation to solution components, such as design documents and development
modules
Documenting these relationships provides the following advantages:
1.Impact Analysis
2.Requirements Coverage
3.Requirements Allocation

12
Tasks 1 Trace Requirements

Inputs:
1.Requirements Managemet Plan
2.Requirements
Techniques:
1.Backlog Management
2.Issue (problem) Tracking
3.Requirements Traceability Matrix
Outputs:
1.Requirements Traceability Matrix (Updated)
All requirements should be documentes in the RTM and include information
such as dependencies and other attributes needed in order to effectively
manage and communicate requirements and their statuts.

13
Tasks 1 Trace Requirements

Consideration for Trace Requirements:

1.Relationships
- Subsets
- Implementation Dependency
- Benefit or Value Dependency
2.Requirements Management Tools
3.Adaptive (Agile) Project Approaches

14
Tasks 2 Monitor Requirement Status

Monitor requirements throughout their lifecycles using a traceabilty artifact

or tool in order to ensure the appropriate supporting requirements artifacts
(such as models, documentation, and test cases) are produced, reviewed,
and approved at each point in the lifecycle.

Business Analyst is responsible for ensuring that RTM contains the

information needed to support the requirements and the information
necessary to understand the status or the requirements throughout the
requirements and project lifecycle.

15
Tasks 2 Monitor Requirement Status

Inputs:
1.Requirements Managemet Plan
2.Requirements
Techniques:
1.Backlog Management
2.Issue (problem) Tracking
3.Requirements Traceability Matrix
Outputs:
1.Requirements Traceability Matrix (Updated)
All requirements should be documentes in the RTM with reference to related
requirements, business analysis work products, project team deliverables, and
information on outstanding issues.

16
Tasks 2 Monitor Requirement Status

Consideration for Trace Requirements:

1.Progressive Elaboration
2.Business Analysis Work Product
3.Team Deliverables
4.Issue and Problem Tracking

17
Tasks 3 Update Requirement Status

Update a requirements status as it moves through its lifecycle states by

communicating with appropriate stakeholders and recording changes in the
traceability artifact or tool in order to trace requirements toward closure.

One element of keeping the requirements current is being proactive in

working with the project team and stakeholders to monitor the status so
updates can be made in a timely manner.

18
Tasks 3 Update Requirement Status

Inputs:
1.Requirements Managemet Plan
2.Requirements
Techniques:
1.Backlog Management
2.Issue (problem) Tracking
3.Requirements Traceability Matrix
Outputs:
1.Requirements Traceability Matrix (Updated)
All requirements should be documentes in the RTM with statuss and inculde
reference to related requirements, business analysis work products, project
team deliverables and information on outstanding issues.

19
Tasks 3 Update Requirement Status

Consideration for Trace Requirements:

1.Requirements Status
- Open statuses: Proposed, Approved, In Progress, Completed
- Closed statuses: Rejected, Cancelled, Deferred, Implemented
2.Requirements Lifecycle State Diagram
The requirement state is usesed when reporting requirement status to project
stakeholders.

20
Tasks 4 Communicate Requirements Status

Communicate requirements status to the project manager and other

stakeholders using communication methods in order to keep them
informed of requirements issues, conflicts, changes, risks, and overall
status.

Proactively communicating requirements status will ultimately make the job

of the business analyst easier.

21
Tasks 4 Communicate Requirements Status

Inputs:
1.Requirements Managemet Plan
2.Requirements
Techniques:
1.Backlog Management
2.Issue (problem) Tracking
3.Requirements Traceability Matrix
Outputs:
1.Requirements Communication
Communication regarding requirements including status, issues, risks, and
conflicts disdeminated to apporiate stakeholders at the appropriate level of
detail as determined in the Requirements Management Plan plus any needed
adaptations to those plans.

22
Tasks 4 Communicate Requirements Status

Consideration for Trace Requirements:

1.Communication Plan: Who, What, and How
2.Communication by Role
- Executive Management and Executive Sposors
- Project Sponsor
- Business Stakeholders
- Quality Assurance
- Project Manager
- Subject Matter Experts (SMEs)/Technologist

23
Tasks 5 Manage Changes to Requirements

What is a change request, change control process, change control

board?
A change request is the formal proposal for a change as simple as this. Because we need to
control the changes made to the product scope, we need an established process for this
change control process. And because we need an authorized body to review, evaluate,
approve, delay, or reject changes to the project we need the change control board (quite often
referred to as CCB).

How business analysis relates to change management?

Change management is of interest to both PM and BA. The PM is concerned with all things
associated to project scope, while the BA is concerned with product scope maintaining the
integrity of the requirements and associated deliverables and to ensure that each new
requirement aligns with the business need and project objectives. However, both roles should
work collaboratively and communicate frequently regarding the proposed changes.

24
Tasks 5 Manage Changes to Requirements

A strong project manager and business analyst team has a plan for:
Accepting changes from stakeholders
Analyzing their impact
And helping the sponsor make rational decisions about how to address them

Steps of a Typical Change Management/Change control process:

1.Request the change (any stakeholders)
2.Analyze the impact of the change (BA)
3.Report costs and benefits of change (BA and solution team)
4.Approve or deny the change (PM, sponosor, or change control board)
5.Incorporate approved chagnes into the solution design and test cases (BA,
solution team, and tester)

25
Summary of Traceability and Monitoring

Tracing and Monitoring requirements helps to ensure the solution is delivered on

time, within budget, and meets the business need.
Note 1:
Make sure your requirements support the project and business objectives
Make sure the approved requirements are implemented in the solution
Dont allow scope creep!
Note 2:
Business objectives are usually long term, strategic goals, while project objectives
are specific expectations for the solution developed by the project team
Your solution should satisfy project objectives, which should support business goals
and objectives

26
Part 2 Techniques for Traceability and
Monitoring
The tools that you can use to perform traceability and monitoring depend on your
organizational practices and the available software.
Requirements Traceability Matrix. Common attributes of the matrix include:
Requirements ID (also Requirement Parent ID) and Description
Version, Priority, Owner
Status
Use Case IDs
Reference Documents
Class/ Method/ Function/ Procedure
Test Case Number
Tester/Developer

27
Part 2 Techniques for Traceability and
Monitoring
CRUD (Create, Read, Update, Delete):
Shows how each data element is created, read, updated, and deleted by each
process
Make sure asked all the necessary questions about the business data and
processes
Make sure dont miss a business process
Usefull for the DB designer and solution team.

28