BUS9041M PROJECT PLANNING AND
MANAGEMENT
Lecture 4a -Requirements Definition
Presented by Herbert Mapfaira
Systems Development Cycle (SDC)
Phase A: Conception Phase B: Definition
phase phase
Initiation stage Project definition
Feasibility stage System definition
Proposal preparation User and system
requirements
Phase D: Operation Phase C: Execution
phase phase
System maintenance Design stage
and evaluation Production/build stage
Fabrication
System System Testing
Improvement termination Implementation stage
Training
Acceptance tests
(To Phase A: Installation
repeat cycle) Termination
Systems Development Cycle (SDC)
Phase A: Conception Phase B: Definition
phase phase
Initiation stage Project definition
Feasibility stage System definition
Proposal preparation User and system
requirements
Phase D: Operation Phase C: Execution
phase phase
System maintenance Design stage
and evaluation Production/build stage
Fabrication
System System Testing
Improvement termination Implementation stage
Training
Acceptance tests
(To Phase A: Installation
repeat cycle) Termination
Customer, User and System
Requirements
Requirements Definition
Define User/ Define
Customer Deliverables
Requirements
Create Project
Plan
Requirements Definition
So why are requirements so important?
https://youtu.be/0YBMfTorE6A
Requirements Definition
Two of the main reasons projects fail are:
• Unclear objectives
– Inadequate definition
– Scope not fully defined
• Poor communications
– Lack of stakeholder consultation
Sources: National Audit Office study 2013 and Office of
Government Commerce findings 2013
Requirements Definition
Requirements Definition
• Without clear requirements:
– How would you know “what” is needed?
– How would you know how to provide what is
needed?
– How would you define the necessary project
work?
Requirements Exercise
Customer: “I want a drawing of an animal”
• You have 10 questions to get all the
answers you need to draw me my animal
Requirements Exercise
• Why aren’t your drawings exactly the
same?
• What could we do so that we all have the
same understanding?
– More questions?
– More specific questions?
– More structured questions?
– An example drawing?
– Others?
Requirements Definition - Issues
1. Incorrect Requirements:
– Needs of wrong stakeholders
– Conflicting needs of multiple stakeholders
– The “Wish List”
– Unsuitable expert advice
– Customers may not describe key requirements
because those requirements are so familiar to
them, and they assume they are equally familiar to
everyone else
Requirements Definition - Issues
2. Imprecise or Ambiguous Requirements:
– Language
– Deliberate imprecision for flexibility
– User’s lack of expertise
3. Shifting Requirements
• User’s change of mind
• New opportunities
• Seeking perfection
Requirements Definition - Issues
• According to the PMI Project Management Body of
Knowledge, requirements should be:
– Unambiguous (measurable and testable)
– Traceable
– Complete
– Consistent
– Acceptable to key stakeholders
– Baselined
• The Analyst should take the time to understand the
customer’s needs, problems and opportunities
Requirements Gathering
• One-to-one interviews
• Group interviews
• Focus groups
• Brainstorming session
• Questionnaires
• Prototype /Mock-up
• Use cases / diagramming
• Observing
Requirements Breakdown Structure
• Supports requirements management throughout the
project life cycles and the choice of life cycle
Project Goal and
Solution
Functional Physical Quality
Requirement #1 Requirement #2 Requirement #3
Physical Physical
Requirement #2.1 Requirement #2.2
Requirements – New Product Development
• “Market Requirements” are key benefits (not
features) that a product must have in order to
succeed in the market
• May also be “Customer Experience Requirements.”
• The Marketing department may produce the market
requirements document, then Engineering
department creates the product requirements
• Product requirements are the list of technical
attributes (specification) that the product must have
in order to meet the market requirements
Requirements – New Product Example
• Objective: create a customer experience around
portable music, by creating a product with the
following requirements:
– Large song capacity
– Small enough to fit in your pocket (“1,000 songs in
your pocket”)
– Long battery life
– An intuitive user interface and navigation
– A fast, simple and consistent method to transfer
songs
Any Questions?
