Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Requirements Management and Communication

No description
by

Victoria Cupet

on 30 May 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Requirements Management and Communication

Requirements Management and Communication
4.1 Manage Solution Scope & Requirements
Elements
Domain SME
Project Manager
Techniques
Stakeholder List,
Roles,
& Responsibilities
Output from
Business Analysis
Planning&Monitoring
Requirements Management Plan
define the process for managing solution scope and requirements
Stakeholder,
Solution, or
Transition Reqs
[Communicated
or Traced ]
Reqs
managed at any point in their lifecycle (stated, specified and modeled, verified, validated, etc.)
Requirements
[Approved]
Reqs
agreed by stakeholders and ready for use in subsequent BA or implementation efforts
General Techniques

Problem Tracking (9.20)

Implementation SME
Sponsor
Solution
Scope
requirements must support the solution scope in order to be approved
Output from
Enterprise
Analysis
stakeholder approval is normally restricted to verified and validated requirements
Solution Scope Management
Conflict and Issue Management
Presenting Requirements For Review
Approval
Baselining
Signoff
4.2 Manage Requirements Traceability
Elements
Tester
Project Manager
Techniques
Requirements Management Plan
define traceability process
Requirement
Reqs
all kind off requirements
Requirements
[Traced]
Reqs
clearly defined relationships to other requirements within the solution scope
Implementation SME
Necessity
Effort
Relationships
Impact Analysis
Configuration Management System

Subset
Cover
Value
Coverage Matrix
4.3 Maintain Requirements for Re-use
Elements
Business Analyst
Domain SME
Techniques
Requirement
Reqs
maintained for re-use if describe information of use to the organization beyond the lifetime of an initiative
Requirements
[Maintained and Reusable]
Reqs
suitable for
long-term usage
by the organization
Implementation SME
Organizational
Process Assets
(OPA)
standards regarding how and when requirements should be maintained for re-use
Ongoing
Requirements
Satisfied
Requirements
4.4 Prepare Requirements Package
Elements
Project Manager
Regulators
Techniques
Requirement
Reqs
may be packaged at any point in their lifecycle
Requirements
Package
Reqs
requirements document, presentation, or package of requirements ready to be reviewed by stakeholders
Implementation SME
Organizational
Process Assets
(OPA)
templates that can be used to package requirements
Requirements Structure
package should contain a consistent, cohesive, and coherent set of requirements
Business Analysis Communication
Plans
define whether a single requirements package or multiple requirements packages are required for specific stakeholders
Format
Work Products and Deliverables

Request for Information (RFI)
Request for Quote (RFQ)
Request for Proposal (RFP)
Requirements Documentation
Business Requirements Document
Product Roadmap
Software/System Requirements Specification
Supplementary Requirements Specification
Vision Document

Requirements for Vendor Selection
Domain SMEs & End Users
Sponsor
Tester
4.5 Communicate Requirements
Elements
Techniques
Requirement
Reqs
any requirement may be communicated
Requirements
Package
Reqs
if a package has been assembled, it must be distributed, reviewed, and the contents must be communicated to stakeholders
Business Analysis Communication
Plans
what information is to be communicated
which stakeholders need to receive it
when communication should occur
and the form it should occur in
All stakeholders
Requirements
[Communicated]
Reqs
the requirements and their current state
Formal Presentation
Informal Presentation

Presentations
General Communication
Structured Walkthrough (9.30)
Requirements Workshops (9.23)
Output from
Business Analysis
Planning&Monitoring
Output from
Business Analysis
Planning&Monitoring
Output from
Business Analysis
Planning&Monitoring
Output from
Requirements
Analysis

Output from
Business Analysis
Planning&Monitoring
Full transcript