requirements management office - strata

Requirements Management Office

(RMO)

John Cheesman

IIBA 13th March 2013

Abstract A Requirements Management Office (RMO) is a

structured way to manage requirements and

specifications.

It is a co-ordinating organisational function providing

tooling, standards, policies and governance across

projects for requirements.

Similar to the PMO (Project Management Office) for project

management.

This talk describes the purpose of an RMO and

experiences working with companies to set them up.

2 copyright © 2005-2013 Strata Software Ltd. All rights reserved.

Topics

• Requirements for Requirements

• The RMO

• Example Processes and Reports

• Lessons Learned

• Q&A


RDM

Project Disciplines – the V Model

Operational

Reporting

Business

Requirements

System

Specification

Business

Objective

Acceptance

Testing

System

Testing

High-Level

Design

Integration

Testing

Unit

Design/Dev

Unit

Testing

Have we

built the

right system?

Have we

built the

system right?


RDM

Single Source of Truth

5

Test

Design/Dev

Business

PM BA

REQS

Multiple Stakeholders

Collaboration and

Communication

Cross-discipline consistency

Single Source of truth

copyright © 2005-2013 Strata Software Ltd. All rights reserved.

System Specification

Business Requirements

Structured Requirements

6

Business Process

Use Case

System

Business

Objective /

Requirement

Requirements-

Driven Projects

Solution-Driven

Projects System

Requirement

Business Capability

REQS

Requirements Structure

Standards

ALM Mappings and

Consistency


System Specification

Multiple Requirements Forms

7

Use Case Functional

Requirement

Message Notification

Step

User Interface System Rule

REQS

Standardised Requirements

Types

Story

Business Requirements

Business Process

Business

Objective /

Requirement

Business Capability


Projects and Architecture

Project Project Project Project Project Project

Projects have a vertical focus, Architecture has a horizontal focus.

Business Architecture

Technology Architecture

Application Architecture


Business Architecture

Application Architecture

Traceability and Consistency

9

Re

qu

ire

me

nts

Tra

ce

ab

ility

Project /

Release

Focus

Architecture Governance / Consistency

Product / Roadmap Focus

Business Process

Use Case

System

Business Capability

REQS

Vertical Traceability

Architectural Consistency


Requirements for Requirements

10

REQS

Multiple Stakeholders

Collaboration and

Communication

Cross-discipline consistency

Single Source of truth

REQS

Requirements Structure

Standards

ALM Mappings and

Consistency

REQS

Standardised Requirements

Types

REQS

Vertical Traceability

Architectural Consistency

REQS

Support (Standards, Tooling)

Governance (Consistency,

Compliance, Reporting)

+ copyright © 2005-2013 Strata Software Ltd. All rights reserved.

Project Requirements

Architecture,

Standards & Policies

POLICY MGT REPORTING TOOL ING

RMO ACTIVITIES

DISCOVERY IMPLEMENTATION BUILD & TEST

DELIVERY ACTIVITIES

The Governance Burger Ensuring consistency across projects

Support

Compliance


Requirements Management Office

12

RDM

Repository

& Tools

Standards

(Types, Structure)

Policies (ALM,

Architecture)


Requirements Lifecycle Process


Status Reporting


Quality & Delivery Dashboard


Establishing an RMO – Lessons

• Prioritise (scope) Requirements for Requirements

• Gain stakeholder buy-in (like any other project)

• Create an RMO role and champion(s)

• Establish tooling / repository

• Implement iteratively – standards, measures, reports

• Deliver early wins

• Ensure projects are supported

• Light-touch compliance (initially)

• Incremental RDM improvement


requirements management office - strata

Documents