Mais conteúdo relacionado
Semelhante a Kiss the BRD Good-Bye (20)
Mais de Patrick van Abbema, PMP, CBAP, CSP (20)
Kiss the BRD Good-Bye
- 1. Kiss the BRD Goodbye
Phil Vincent
phil@birchisland.ca
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be used without the expressed, written consent of the author
- 2. You guys start coding,
I’ll go find out what the users want
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 3. What is a BRD?
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 4. e
liz
a
ptu t
ou
ute
e te
nc e
c
lo s
tia n xe
Co Ini Pla
Project C
E
Life Cycle
t
en n
m
itio
is op
n
ys l s
sig
l ve t an
na es
De De r
A T
T
System
Development
n
1 3
2
Life Cycle n
n n
n
tio
tio tio
tio
era
era era
era It
It It
It
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 5. 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
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 6. BABOK 1.6
Requirements Planning and Management
Requirements Elicitation
Requirements Analysis and
Documentation
Enterprise
Solution Assessment and
Analysis
Validation
Requirements Communication
Underlying Concepts
Fundamentals
Glossary
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 7. BABOK 2.0 (Draft)
BABOK ®v2 Knowledge Areas
Business Analysis Planning
Solution
Requirements
Enterprise
Assessment
Elicitation Analysis
Analysis
and Validation
Requirements Management and Communication
Underlying Concepts
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 8. 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
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 9. Requirements Documents
Preliminary Scope Statement
Vision Document
Feasibility Study Report
Business Case Report
Project Charter
Request For Proposal
Business Requirements Document
Functional Requirements Specification
Supplementary Requirements Specification
Software Requirements Specification
Non-Functional Requirements Specification
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 10. A Requirements Document is a snapshot at a point in time
It is not a requirements deliverable
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 11. Requirements Deliverables
n
Use Case Diagram Workflow Diagrams
Context Diagram
Business Rules
Use Case Descriptions
User Profiles
R
Availability
Course description e
Eligibility
g Payment options
i
s
t Ac
e kno
Pa r P wle
C
y a dg
a
Credit Card was
by y e
Describe n
card Cre declined
ch
payment c
details dit
ec b
procedures e car
k y l
d
or
De
mo c
clin
ne rCredit card
ed
y etransaction
ord Registrationdauthorized
er Status i
t
c
a
r
d
Story Boards
Logical Data Model
Class Model
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 12. n
Vision Document
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 13. n
Business Case
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 14. n
Project Charter
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 15. n
Request for Proposal
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 16. n
R
Availability
Course description e
Eligibility
g Payment options
i
s
t Ac
e kno
Pa r P wle
C
y a dg
a
Credit Card was
Functional Requirements Specification
by y e
Describe n
card Cre declined
ch
payment c
details dit
ec b
procedures e
car
k y l d
or
De
mo c
clin
ne rCredit card
ed
y etransaction
ord Registrationdauthorized
er Status i
t
c
a
r
d
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 17. v1,v2,v3,v4,v5,v6, v7, v8,…..
n
v1,v2,v3,v4,v5,v6,…..
v1,v2,v3,v4,v5,…..
v1,v2,v3,v4,…..
v1,v2,v3,v4,v5,v6,…..
R
Availability
Course description e
Eligibility
g Payment options
i
s
t Ac
e kno
Pa r P wle
C
y a dg
a
Credit Card was
by y e
Describe n
card Cre declined
v1,v2,v3,v4,…..
ch
payment c
details dit
ec b
procedures e
car
k y l d
or
De
mo c
clin
ne rCredit card
ed
y etransaction
ord Registrationdauthorized
er Status i
t
c
a
r
d
v1,v2,v3,v4,v5,v6,v7,v8…..
v1,v2,v3,v4,v5,v6,v7,v8,v9…..
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 18. Requirements v1,v2,v3,v4,v5,v6, v7, v8,…..
Repository 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…..
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 19. 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
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 20. 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
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 21. Baseline
R
Course description Availability
e
Eligibility
g Payment options
i
s
A
t
c
e
P P C
n k
r
a Credit a a n Card was
Describe
y card y n o declined
C
payment details c r w
procedures
b b e e l
y y l d e
i d
c c
t g
Credit
h r
e
Registration card
e e c
Status d transacti
c
a
on
k i r
t authoriz
d
ed
o
D
r c
e
a
c
m r l
o d
i
n n
e
e
y
d
o
r
d
e
r
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
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 22. Milestone
“A significant point or
event in the project.”
PMBOK Third Edition, Glossary, pg 364
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 23. Milestone
The review and approval of a document is a milestone
B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B…..
The baseline is the collection of requirements deliverables
that is approved
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 24. Change Control
“Identifying, documenting,
approving or rejecting and
controlling changes to the
project baselines.”
PMBOK Third Edition, Glossary, pg 364
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 25. Change Control
B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B…..
Change control is applied here
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 26. Change Control
The purpose of change control is
to ensure that
we build exactly the right product
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 27. Once Upon a Time…
A software application was delivered on time,
within budget, and met scope and quality objectives.
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
The business domain was complicated;
requirements kept changing and the users kept changing their minds
Instead of “documents”, they relied on a requirements repository.
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 28. Once Upon a Time…
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 29. 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
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 30. Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved
- 31. Thanks for listening!
Any questions?
phil@birchisland.ca
Copyright © 2008 Phil Vincent & Associates
No part of this presentation may be reproduced without the expressed written permission of the author. All rights reserved