kiss the brd good-bye

Kiss the BRD GoodbyePhil Vincent

[email protected]

Copyright © 2008 Phil Vincent & AssociatesNo part of this presentation may be used without the expressed, written consent of the author

Copyright © 2008 Phil Vincent & AssociatesNo part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved

You guys start coding, I’ll go find out what the users want


What is a BRD?


Conceptualize

Initiate

Execute

Closeout

PlanProjectLife Cycle

Analysis

Design

Test Transition

Development

System Development Life Cycle

Iteration 1

Iteration 2

Iteration n

Iteration 3


BABOK 1.6

“The business requirements document describes the behavior required of a software application.

The primary target audience for a BRD is the customer and users.”

BABOK v 1.6 pg 207


Requirements Planning and Management

Enterprise Analysis

Requirements Elicitation

Requirements Analysis and Documentation

Solution Assessment and Validation

Requirements Communication

Glossary

Fundamentals

Underlying Concepts

BABOK 1.6


BABOK ®v2 Knowledge Areas

Business Analysis Planning

Enterprise Analysis Elicitation

Requirements Analysis

Solution Assessment

and Validation

Requirements Management and Communication

Underlying Concepts

BABOK 2.0 (Draft)


BABOK 2.0 (Draft)“….(Requirements) deliverables must be packaged into a requirements document for presentation to stakeholders” pg 72

“There will likely be a combination of many formats in one document” pg 73

“If the package is created with intention of making it a baseline for change control, the requirements documentation must be complete in order to prepare the requirements package” pg 73


Requirements Documents

Preliminary Scope StatementVision DocumentFeasibility Study ReportBusiness Case ReportProject CharterRequest For ProposalBusiness Requirements DocumentFunctional Requirements SpecificationSupplementary Requirements SpecificationSoftware Requirements SpecificationNon-Functional Requirements Specification


A Requirements Document is a snapshot at a point in time

It is not a requirements deliverable


Requirements Deliverables

n

Context Diagram Use Case Diagram

User Profiles

Logical Data Model

Workflow Diagrams

Class Model

Course description

P a y

b y

c r e d i t

c a r d

Ac kno wle dg e

Pa y by ch ec k or mo ne y

ord er

R e g i s t e r

Credit card

details

AvailabilityEligibilityPayment options

C a n c e l

Registration Status

Describe payment

procedures

Card was declinedCre

dit car dDe clin edCredit card

transaction authorized

Story Boards

Use Case Descriptions Business Rules


n

Vision Document


n

Business Case


n

Project Charter


n

Request for Proposal


n

Functional Requirements Specification

Course description

P a y

b y

c r e d i t

c a r d

Ac kno wle dg e


ord er

R e g i s t e r

Credit card

details


C a n c e l

Registration Status

Describe payment

procedures





n v1,v2,v3,v4,v5,v6, v7, v8,…..

v1,v2,v3,v4,v5,v6,…..

v1,v2,v3,v4,v5,…..

v1,v2,v3,v4,…..

v1,v2,v3,v4,v5,v6,…..

v1,v2,v3,v4,…..

v1,v2,v3,v4,v5,v6,v7,v8…..

v1,v2,v3,v4,v5,v6,v7,v8,v9…..

Course description

P a y

b y

c r e d i t

c a r d

Ac kno wle dg e


ord er

R e g i s t e r

Credit card

details


C a n c e l

Registration Status

Describe payment

procedures





v1,v2,v3,v4,v5,v6, v7, v8,…..

v1,v2,v3,v4,v5,v6,…..

v1,v2,v3,v4,v5,…..

v1,v2,v3,v4,…..

v1,v2,v3,v4,v5,v6,…..

v1,v2,v3,v4,…..

v1,v2,v3,v4,v5,v6,v7,v8…..

v1,v2,v3,v4,v5,v6,v7,v8,v9…..

Requirements Repository


Requirements Repository

• Automatic versioning of requirements deliverables– Access to past versions

• Baselining– Control which versions of deliverables go with which– Facilitates traceability

• Communication– All versions are accessible by all stakeholders

• Generate documents from the repository– As and when needed


Baseline

“A set of specifications….that has been formally reviewed and agreed on, which thereafter serves as the basis for further development, and can only be changed through change control procedures.”

CMMI Guidelines for Process Improvement, Glossary, pg 613


Baseline

n

Course description

P a y

b y

c r e d i t

c a r d

A c k n o w l e d g e

P a y

b y

c h e c k

o r

m o n e y

o r d e r

R e g i s t e r Credit

card details


C a n c e l

Registration Status

Describe payment

procedures

Card was declinedC

r e d i t

c a r dD e c l i n e d

Credit card transacti on authoriz ed

B#1 v2 v4

B#2 v5 v9 v3

B#3 v7 v11 v5 v12 v3

B#4 v7 v14 v9 v17 v6 v4 v7 v3

B#5 v7 v14 v9 v17 v8 v4 v9 v6

B#6 v7 v14 v10 v18 v11 v5 v9 v6


Milestone

“A significant point or event in the project.”

PMBOK Third Edition, Glossary, pg 364


Milestone

B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B…..

The review and approval of a document is a milestone

The baseline is the collection of requirements deliverables that is approved


Change Control

“Identifying, documenting, approving or rejecting and controlling changes to the project baselines.”

PMBOK Third Edition, Glossary, pg 364


Change Control

B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B…..

Change control is applied here


Change Control

The purpose of change control is to ensure that

we build exactly the right product


Once Upon a Time…

A software application was delivered on time, within budget, and met scope and quality objectives.

The business domain was complicated; requirements kept changing and the users kept changing their minds

It was staffed by ordinary people: analysts, designers, developers, …Even the subject matter experts were ordinary.

The team was distributed in 5 cities in 3 countries across 12 time zones and they spoke at least 3 different languages

Instead of “documents”, they relied on a requirements repository.


Once Upon a Time…


Best Practices• Manage requirements deliverables, not

requirements documents– A document is just a snapshot

• A milestone

• Each requirements deliverable has its own life cycle– Use a repository tool

• Versioning, managing baselines, team communication

• Change control begins with the first baseline– Rigorously enforced

• To ensure that we build exactly the right product


Thanks for listening!

Any questions?

[email protected]

kiss the brd good-bye

Business

expressed written permission

phil vincent associatesno

requirements documentation

proposal copyright

requirements package

written consent

nvision document copyright

nbusiness case copyright