This
example shows a Review Process with individual lanes for the four roles: Moderator,
Reviewers, Authors, and Recorder. The tasks to be performed are in ovals with
decisions in diamonds.
defining Procedures
What are procedures? Procedures are step-by-step instructions on how to perform
a task. To be repeatable, the steps need to be broken down to a level that anyone
who needs to perform the task, with a general understanding of the work to be
done, can perform the work adequately by following the instructions. Procedures
are a subset of processes. The process is what to do; the procedures are how to do
the steps in the process.
Procedures are step-by-step instructions of how your processes are performed.
They include:
Action or Task
Obtain Work Request from the customer
PM Review Work Request
Create Initial Budget/Estimates/Schedule
PM, project team
PM, project team
PM, project team, QA
PM, customer, project team, QA
PM, project team, QA, customer
PM, project team, customer
PM, project team, customer
Initial planning
High-level requirements
Risk identi?¬?cation and documentation
Requirements Spec DRAFT
Technical review
Customer Customer review
Re?¬?ne Requirements
Create Requirements Traceability Matrix
Review requirements and RTM
PM Review/update risks
PM Update estimates and schedules
Review requirements and schedules and estimates
PM, analysts Requirements Spec FINAL
Customer, QA, PM, SM, EPG Approvals and signo?¬?s
PM, CCB, EPG Baseline Requirements Spec
Assess, track, and incorporate changes
LEGEND:
PM = Project Manager
SM = Senior Management
CCB = Con?¬?guration Control Board
QA = Quality Assurance
EPG = Engineering Process Group
SM, PM
PM, project team
PM, CCB, QA, EPG, Customer, project team
PM
PM
Responsibility
table 15.
Pages:
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445