Requirements Management

This report explores the project that has been assigned by Peters company to Corwins for research, development and testing of its new rubber products. The project would involved 30 tests that would be run.

Requirements Management
Student Name
[Student No]

Requirements Management
Contents
Introduction...........................................................................................................................................2
Requirements management plan (RMP)................................................................................................2
Project Overview...............................................................................................................................2
Requirement Gathering......................................................................................................................2
Roles & Responsibilities....................................................................................................................3
Tools..................................................................................................................................................3
Requirements Traceability Matrix.....................................................................................................3
Change Control..................................................................................................................................4
Requirements Documents......................................................................................................................4
Business Requirements for Peters......................................................................................................4
Business Recruitments for Corwins...................................................................................................5
Stakeholder Requirements.................................................................................................................5
Solution Requirements......................................................................................................................6
Project Requirements.........................................................................................................................6
Transition Requirements....................................................................................................................6
Project Scope.........................................................................................................................................7
Scope Statement................................................................................................................................7
WBS..................................................................................................................................................7
WBS Dictionary................................................................................................................................8
Scope Validation.................................................................................................................................13
Conclusions.........................................................................................................................................14
References...........................................................................................................................................15

Requirements Management
Introduction
This report explores the project that has been assigned by Peters company to Corwins for
research, development and testing of its new rubber products. The project would involved 30
tests that would be run. This document contains the detailed plan of how requirements of the
project would gathered and documented using appropriate project management tools. It also
presents a WBS and a dictionary defining its work packages.
Requirements management plan (RMP)
Project Overview
This project has been taken by Corwins from Peters company that needs its Research and
Development operations to be taken by Corwins for a project which would need 30 tests to be
conducted on the special product. The project has been assigned a budget of $231,000 and
has to be completed within 6 months.
Requirement Gathering
The requirements of the project have been gathered by marketing VP, Gene Frenel of Corwin
from one of the key stakeholders of the Peters company named Frank Delia who is the
marketing VP of his company. An initial interview have been conducted and thereafter the
specification sheet had been sent by Peters company to Gene over email with detailed
requirements on five tests to be conducted. For the remaining tests, a mutual agreement
between two companies would be arrived at after discussion (C.R & Thomas, 2011).
The high level requirements of the project were identified by interviewing the major
stakeholders of the Peters company and these included:
 The project would have to research and develop rubber products and conduct tests for
them
 There would be 30 tests to be conducted in 6 months
 The 5 tests have to be run according to the specification sheets provided by the client
 The 25 tests would be mutually decided between Peters and Corwins company
considering the needs for the product and the market
 The team would need to conduct a research on rubber materials and then develop
them before testing would follow

Requirements Management
Roles & Responsibilities
The key people who are responsible for managing the project include marketing VP who has
initiated the project, Royce who took the bidding decision, Dr. Reddy who would help in the
resource planning and Dan West who would be the project manager of the project.
Name Role Responsibility
Gene Fremel Marketing – VP Project Acceptance
Royce Engineering - VP Bidding decision
Dr. Reddy R&D – Director Project Resource Planning
Dan West R&D – Scientist Project Management
Tools
For the management of the project, a number of project management tools would be used
including responsibility traceability matrix, work breakdown structure, WBS dictionary, and
project requirement documentation.
Requirements Traceability Matrix
Each requirement defined by the client would be recorded in the traceability matrix which
would identify how they would be fulfilled including the source of request, department
responsible, business need it would justify, WBS deliverable it would be connected to, test
strategy to use, responsible person and as the project progresses, the status would keep
getting updated. A sample matrix is provided below which illustrates how requirements of the
project would be recorded (Leroy, 2012)
Requirem
ent
Descriptio
n
Sour
ce
Departme
nt
Business
Need
WBS
Delivera
ble
Test
Strategy
Responsibi
lity
Status
5 tests to
be
completed
as per the
test sheets
provided
Patri
k
Ray
Project
Managem
ent
Test the
product
for its
market
value
Testing Validate
as per
specificati
on sheet
Project
manager
Yet to
begin
Project to Gene Marketing Project Project Plan to be Project In

Requirements Management
be
completed
within 6
months
Frem
el
needs to
be
planned
appropriat
ely so that
it can be
completed
in desired
timeline
planning validated
by the
project
stakehold
ers on
scope
manager –
Dan West
progre
ss
(BIS,
2010)
Change Control
Change is inevitable and as the project progresses, changes are required. If there are major
changes made in deliverables of the project then it could affect the project constraints,
performance, as well as the viability of the project. Thus, it is important that changes are
carefully managed such that only those changes are made that are good for the project. Thus,
it is essential to keep in place a change control policy such that unviable changes are not
executed. For controlling change, an organized process would be used in which every change
need sensed by any project team member would be formally placed to the project manager
who would be evaluating the change requirements to see how it would affect the project. This
assessment would involve review of the impact of change on project deliverables and
constraints (Jainendrakumar, 2016). The changes requested would be recorded in a log and
the decisions made on whether to accept the change or not would be updated in the log.
Impacts of the change would be on cost, timeline, resource requirements, and project risks or
issues. The result of change request can be acceptance, acceptance in special conditions,
rejection or deferment in which change is rejected for the time being but is kept for
consideration. If a change is approved, it is implemented and the implementation is reviewed
to again assess the actual impact caused.
Requirements Documents
Business Requirements for Peters
The company has been facing a shortage of workforce as most of the workforce is already
involved in the existing R&D work and thus, needs an external company to take care of their
new project’s Research and development as well as production for which Corwins have been

Requirements Management
approached. The project is required to be profitable for the company and thus, has to be
completed within $250,000 in six months with un-front payment of $125,000 paid and rest to
be paid after completion. The R&D project would need 30 tests to be conducted out of which
test conditions for first five projects have been specified by Peters Company.
Business Recruitments for Corwins
The company had estimated the cost of conducting test and expecting $19,000 as profits and
thus, the aim of the company is to ensure that project is completed within the desired estimate
as planned. The company needs to have the right professionals assigned the work of project
completion. And should be able to complete the project within 6 months as given by the
client. The total cost of labour should not be more than $30,000 while each test would cost
$2000 with overheads of $90000, material costs of $30,000, and administrative expenses of
$21,000, totalling the cost of project to $231,000 (SAEO, 2015).
Stakeholder Requirements
Stakeholders are the key people associated with the project in some ways such that they
either affect the project or are influenced by the project. Every stakeholder would have
different levels on influence on the project and interest. Their requirements have to be
understood and collected for the project deliverables and acceptance criteria’s to be
developed. From the interviews conducted with the key stakeholders of the project, some key
requirements have been identified as listed in the table below (Baguley, 2008):
Stakeholder Rols & Responsbility Influence/Interest
Frank Delia Marketing – VP High, high
Patrick Ray In-house
representative
High, high
Gene Fremel Marketing Moderate, high
Royce Engineering Moderate, high
Dr. Reddy Direct project High, Moderate
Customers Buy rubber products Moderate, Moderate
Suppliers Sell rubber material High, Moderate

Requirements Management
Solution Requirements
Based on the requirements identified by different groups of stakeholders, some requirements
for the solution that is research, development, and testing of the rubber products have been
identified as follows:
 Research has to be conducted on the rubber materials needed for the manufacturing of
the new products
 Products have to be developed using the rubber material for Peters company
 The testing has to be conducted on the rubber products so that the products tested
positively can be launched in the market
 Products are required to be tested positively in order to get passed for the mass
production (Berbec, 2014)
Project Requirements
The project involving research, development and testing of the rubber products for Peters
company would have the following project requirements:
 Project needs to be completed within 6 months
 The materials are required to be procured for the procedure in bulk
 30 tests have to be conducted on the rubber products
 The tests conducted should be mutually approved between Peters and Corwins
company (C.R & Thomas, 2011)
Transition Requirements
In order to proceed with the project Corwin would need to deploy its team taking from other
projects to the Peters project which would need a time for transition from one project
environment to another. Also, the Peters company would be outsourcing its research and
development process for the new rubber products and thus, would have to now depend on the
Corwin team for development. The Corwin company has deployed its Engineer as the project
manager while an in-house representative has been assigned by Peters company to coordinate
with the project manager of the project. Based on the project needs, certain transition
requirements could be identified such as:
 The teams from Corwin and Peters have to be able to effectively coordinate and
complete the project tasks on time

Requirements Management
 Both companies representatives need to understand the working culture of the partner
as well as the working style and leadership styles of each other (Clements & Gido,
2006)
Project Scope
Scope Statement
The project involves planning, research, development, and testing for the new rubber
products that are to be manufactured for the Peters company. The activities that are within the
scope of the project include –
 Research on rubber material with potential for new product creation
 Development of rubber material for the new products
 Conducting 30 Testing procedures on new products on multiple parameters
The activities that are excluded for this project include:
 Mass manufacturing of the positively tested products (FME, 2014)
WBS
1.0 Project Planning
1.1 Project management
1.1.1 Stakeholder management
1.1.2 Human Resource Management
1.1.3 Scheduling
1.1.4 Budgeting
1.1.5 Project Scope Management
1.2 Requirement gathering
1.2.1 Interviews with stakeholders
1.2.2 Specification sheets
1.2.3 Requirement Tracing
1.3 Contract Signing
1.3.1 Performance Specifications
1.3.2 Fixed price contract
2.0 Research
2.1 Rubber Material Research
3.0 Development

Requirements Management
3.1 Rubber Material Development
4.0 Testing
4.1 Test planning
4.2 Testing
4.3 Results analysis
5.0 Project Closure
5.1 Deliverables
5.2 Acceptance of deliverables
5.3 Project Sign-off (Devi & Reddy, 2012)
WBS Dictionary
WBS dictionary can be used for defining various tasks and related details can be covered. For
the rubber material research and development project, a WBS dictionary can be prepared for
every task identified in the WBS as follows:
WB
S
ID
WBS
Element
Name
Description Accountabi
lity
Acceptance
Criteria
Assumpti
ons
Constraints
1 Project
Planning
1.1 Project
manageme
nt
1.1.
1
Stakeholde
r
manageme
nt
Gathering
stakeholder
requirement
s and
planning
communicat
ion with
them
Project
Manager
Requiremen
ts validated
by
stakeholder
s
Stakehold
ers know
the needs
of the
project
Stakeholders
are not
always easily
available and
thus, plan has
to be adjusted
to their
availability
1.1.
2
Human
Resource
Manageme
nt
Forming
the project
team and
managing it
Project
manager
Roles and
responsibilit
ies a
identified
Project
team has
sufficient
skills to
There are
limited
number of
resources that

Requirements Management
and
assigned
conduct
the project
can be
utilized
1.1.
3
Scheduling Identifying
timeline and
assigning it
as per WBS
Project
manager
Timelines
are feasible
and
validated by
team
The
project
can be
completed
within
given
schedule
Project has to
be completed
within 6
months
1.1.
4
Budgeting It involves
approval of
total cost of
the project
and
planning of
how the
approved
budget
would be
utilized
throughout
the project
Project
Manager
Creating
and
controlling
budget
Project to
be
completed
within
budget
Budget
cannot be
exceeded
1.1.
5
Project
Scope
Manageme
nt
Project
scope
includes all
the activities
and
deliverables
that are
included in
the scope of
the project
Project
Manager
Defining
scope,
monitoring
project
progress,
and
managing
scope
Project
scope is
clearly
defined
No out of
scope activity
can be done
1.2 Requireme
nt
Project
requirement
Project Collecting
requirement
All key
stakehold
Resources are
available to

Requirements Management
gathering s are
collected
from
stakeholders
Manager s from
stakeholder
s
ers
involved
meet
requirements
1.2.
1
Interviews
with
stakeholder
s
Project
requirement
s are
collected
from
stakeholders
through
interviews
Project
Manager
Collecting
requirement
s from
stakeholder
s
All key
stakehold
ers
involved
Resources are
available to
meet
requirements
1.2.
2
Specificati
on sheets
Details of
the tests to
be
conducted
in the
project
Project
Manager
Test
requirement
s to be
specified
All key
stakehold
ers
involved
Resources are
available to
meet
requirements
1.2.
3
Requirem
ent Tracing
Project
requirement
s would be
traced to
keep
updated if
they have
been
completed
Project
Manager
Stakeholde
r
requirement
s gathering
All key
stakehold
ers
involved
Resources are
available to
meet
requirements
1.3 Contract
Signing
Contract
would be
signed
between
Peters
company
and Corwins
Project
Manager
Project
managemen
t contract
Contract
would be
legal
Contractual
terms have to
be met

Requirements Management
defining the
terms and
conditions,
deliverable,
and legal
details of
the
arrangement
1.3.
1
Performan
ce
Specificati
ons
This
includes the
specificatio
ns of the
tests to be
performed
Project
Manager
Performanc
e testing
Should
meet
identified
needs
Mutually
agreed upon
1.3.
2
Fixed price
contract
The
company
would get a
fixed price
as the
contract
amount
Cost
Manager
Contract
managemen
t
Contractu
al terms
are
mutually
agreed
Fixed price
2 Research Project
Manager
2.1 Rubber
Material
Research
This would
involve
research to
be
conducted
on the
materials
used for the
developmen
t of rubber
Project
Manager
Material
research
As per
project
scope
Not out of
scope
(Gardiner,
2005)

Requirements Management
products
3 Developme
nt
Project
Manager
3.1 Rubber
Material
Developme
nt
This would
involve
developmen
t of the
rubber
materials
researched
Materials
Manager
Rubber
product
developmen
t
As per
project
scope
Not out of
scope
4 Testing Project
Manager
Product
testing
4.1 Test
planning
The
specificatio
ns of the
tests would
be identified
and planned
Project
Manager
Product
testing
As per
test
performan
ce sheets
No additional
tests
4.2 Testing Tests
would be
conducted
on the
rubber
materials
developed
Tester Product
testing
As per
test
performan
ce sheets
No additional
tests
4.3 Results
analysis
The results
of the tests
would be
analysed
Tester Product
testing
As per
test
performan
ce sheets
No additional
tests
5 Project
Closure
Includes
the
processes
involved in
closing the
Project
Manager

Requirements Management
project
5.1 Deliverabl
es
All the
project
deliverables
would be
submitted to
the client
organization
Project
Manager
Deliverable
s
submission
As per
project
scope
all
requirements
have to be
met
5.2 Acceptanc
e of
deliverable
s
Deliverables
would be
accepted
and
approved by
Peters
company
Project
owner
Client
acceptance
As per
project
scope
all
requirements
met have to
be accepted
5.3 Project
Sign-off
Final
project
completion
would be
marked by a
sign off
Project
Manager
Project
completion
Between
two
companie
s
(Jainendrakum
ar, 2016)
Scope Validation
Scope validation involves acceptance of the completed project deliverables. Once the project
is completed, all the project deliverables would be individually reviewed by the marketing
manager and other key stakeholders from the Peters company and as per their acceptance
criteria, they would review if all deliverables have ben covered in the scope. Once verified,
the client would be accepting the project as completed. The best way to ensure that validation
process is formally organized and sufficiently completed, it begins with the monitoring of the
project where validation is done with each deliverables completion and not just after the
completion of the project. Requirement traceability matrix would be used for the current

Requirements Management
project to show if the requirements defined in the project scope were reached with the
completion of the deliverable (PM4DEV, 2016).
Conclusions
This report was prepared to understand and explore how project requirements are collected,
documented and met on a project. The report explored the case of a manufacturing company
Peters that had outsourced its research, development, and testing activity to Corwins for its
current project requiring running of 30 tests. The requirements were collected from
stakeholders by interviewing them and were used to create a WBS. This WBS was further
used to trace how project requirements were met.

Requirements Management
References
Baguley, P. (2008). Project management. . London: Hodder Education.
Berbec, I. S. (2014). Aligning Project Scope And Deliverables With Business Strategy. KTH
Royal Institute of Technology .
Beringer, C. J., & Kock, A. D. (2013). Behavior of internal stakeholders in project portfolio
management and its impact on success. International Journal of Project
Management, 31(6), 840-846.
BIS. (2010). GUIDELINES FOR MANAGING PROJECTS: How to organise, plan and
control projects. BIS.
C.R, K., & Thomas, S. M. (2011). Requirement Gathering for small Projects using Agile
Methods. IJCA, 122-128.
Clements, J. P., & Gido, J. .. (2006). Effective Project Management. Thompson.
Cliff Consulting. (2007). A Systems Implementation Project Planning Guide. Cliff
COnsulting,.
Devi, T., & Reddy, V. (2012). Work Breakdown Structure of the Project. International
Journal of Engineering Research and Applications, 683-686.
FME. (2014). Project Scope Management: Project Skills. FME.
Gardiner, P. D. (2005). Project Management: A Strategic Planning Approach. Macmillan
International Higher Education.
Jainendrakumar, T. D. (2016). Project Stakeholder Management. PM World Journal, 5(5), 1-
9.
Leroy, A. (2012). Requirements Gathering Rules Basic guidelines for any project, . BDPA
National Technology Conference.
PM4DEV. (2016). Project Scope Management for Developing Organizations. PM4DEV.
PMI. (2013). A Guide to Project Management Body of Knowledge. PMI.
PMI. (2013). A guide to the project management body of knowledge. Newton Square:
Pennsylvania.: PMI.

Requirements Management
Ponnappa, G. (2014). Project Stakeholder Management.. roject Management Journal, 1-3.
SAEO. (2015). Cost Estimating Manual for Projects . SAEO.
Wysocki, R. K. (2014). Effective Project Management: Traditional, Extreme, Agile. Wiley
Publications.