management review checklists
DESCRIPTION
TRANSCRIPT
Management Review ChecklistsTL-PMC-01 v1.0
1/27/09
MANAGEMENT REVIEW CHECKLISTS
The checklists contained in this document are guidance for conducting formal progress or management reviews. They address six reviews that might be used at various stages of a system or software project. It is expected that these checklists will be tailored to meet the needs of the project utilizing them. Although these checklists apply primarily to development-type projects, they may be tailored (items added or deleted) for other types of projects.
TABLE OF CONTENTSChecklist Title Page
System/Subsystem Requirements Review Checklist.....................................................................................2
System/Subsystem Design Review Checklist................................................................................................4
Software Requirements Review Checklist.....................................................................................................7
System Preliminary Design Review Checklist............................................................................................10
System Detailed Design Review Checklist..................................................................................................13
Test Readiness Review Checklist................................................................................................................15
1
Management Review ChecklistsTL-PMC-01 v1.0
1/27/09
SYSTEM/SUBSYSTEM REQUIREMENTS REVIEW CHECKLISTPurpose: The objectives of this review are listed below:
a. Ascertain the adequacy of the efforts in defining system or subsystem requirements
b. Assess the risks associated with plans and requirements
c. Obtain initial agreement between the user/customer and the system developer that the preliminary requirements specified for the system or subsystem are complete, accurate, and the requirements represent the initial commitment for the system or subsystem
d. Review and approve preliminary System/Subsystem Requirements Specification
System/Subsystem Requirements Review Entrance Criteria:
1) Peer Review (Formal Inspection) has been done on these documents:
____ Preliminary system or subsystem requirement specification
2) Following analyses have been performed:
____ Feasibility
____ Reliability (hardware and software)
____ Maintainability
____ Survivability
____ Logistics support
____ System/cost effectiveness
____ System safety
____ Human factors
3) ___ Risk management program (identification, avoidance, impact, contingency, and reduction) has been defined
4) Review team has been assembled and they have committed to attend
____ Developer:project manager, system manager, system engineer, software development manager, hardware development manager, testing manager, quality assurance, CM
____ Government:sponsor (program manager), program manager, project manager, software personnel, hardware personnel, Independent Verification and Validation (IV&V), users, life cycle support activity, testing activity
5) Metrics have been collected and analyzed:
____ Actual vs. planned staffing profile
____ Documentation defects
____ Number of requirements identified
____ Requirements fully attributed and entered in a database
6) ___ Current WBS is available
7) ___ Current Milestone Schedule and Deliverable Requirements are available
8) ___ If developer is a contractor, contract is current (contract/delivery order should be funded for the review to be held)
2
Management Review ChecklistsTL-PMC-01 v1.0
1/27/09
System/Subsystem Requirements Review Tasks:
1) Review:
____ Summary of technical issues/problems from Peer Review held prior to this meeting
____ Risk management program
____ Current risks
____ Decisions made prior to the review
- Are we making good decisions?
____ Plans and schedules
____ System quality goals
____ Studies performed and planned
- Feasibility
- Reliability
- Maintainability
____ System design constraints (next phase)
____ Personnel resources/staffing plan (Government and contractor)
____ Project organization structure/communication lines - is it working?
____ Contracting requirements modifications (if necessary) (discussed in Government only session)
____ Metrics collected and analyzed
2) Review project documents
____ Preliminary system or subsystem requirements specification
3) Make decisions
____ Be clear and write them down for distribution
System/Subsystem Requirements Review Exit Criteria:
1) ___ Action items with priority and due date have been assigned
2) ___ Minutes have been reviewed with all attendees present
3) ___ Review has been evaluated/how can we improve?
- Were the facilities adequate?
- Were all of the entrance criteria met?
4) ___ Decision on whether to redo the review has been made
5) ___ Changes to the schedule/deliverables have been recorded
6) ___ Any possible new risks that have surfaced during the meeting have been reviewed
7) ___ Commitment to continue or not has been made
8) ___ Documents have been approved
9) ___ Decisions/Agreements from the meeting have been recorded
10) __ Requirements database has been baselined
3
Management Review ChecklistsTL-PMC-01 v1.0
1/27/09
SYSTEM/SUBSYSTEM DESIGN REVIEW CHECKLISTPurpose: The objectives of this review are listed below:
a. Obtain agreement between the user/customer and the system developer that the system requirements and their allocation to hardware, software, or firmware are complete, accurate, and represent the commitment for the system.
b. Obtain approval for the software development approach and procedures as specified in the software development plan or project management plan.
c. Review and approve the system or subsystem requirement specification, system/subsystem design document, software development plan or project management plan, the preliminary software requirements specification(s), and the preliminary interface requirements specifications. An approved subsystem requirement specification establishes the Functional Baseline, i.e. the baseline of the system requirements
System/Subsystem Design Review Entrance Criteria:
1) Peer Review (Formal Inspection) has been done on these documents:
____ Final system or subsystem requirement specification
____ System/subsystem design document
____ Preliminary software requirements specification
____ Preliminary interface requirements specifications
____ Software development plan or project management plan
____ Configuration management plan
____ Quality assurance plan
2) Following analyses have been performed:
____ System Architecture
____ Allocation of system requirements to software, hardware, and firmware
____ Software and/or hardware configuration item decomposition analysis
____ Value engineering studies
____ Hardware production feasibility
____ Maintainability
____ Reuse and Commercial-Off-the-Shelf (COTS) Products
____ Security
____ Safety
____ Any analysis not reviewed during System/Subsystem Requirements Review
3) Review team has been assembled and they have committed to attend
____ Developer:project manager, system manager, system engineer, software development manager, hardware development manager, testing manager, configuration management, quality assurance
____ Government:sponsor (program manager), program manager, software project manager, hardware
4
Management Review ChecklistsTL-PMC-01 v1.0
1/27/09
project manager, software personnel, hardware personnel, IV&V, users, life cycle support activity, testing activity
4) ___ Prototype is available for review by users (if applicable)
5) Metrics have been collected and analyzed:
____ Actual vs. planned staffing profile
____ Documentation defects
____ Action items complete
____ Traceability of system requirements to system design
____ Traceability of preliminary software requirements to system requirements
____ Traceability of preliminary hardware requirements to system requirements
____ Testability of system requirements
____ Requirements satisfied - progress
6) ___ Current WBS is available
7) ___ Current Milestone Schedule and Deliverable Requirements are available
8) ___ If developer is a contractor, contract is current (contract/delivery order should be funded for the review to be held)
9) ___ Configuration Control Board established
System/Subsystem Design Review Tasks:
1) Review:
____ Summary of technical issues/problems from Peer Reviews held prior to this review
____ Risks
____ Decisions made prior to the review
- Are we making good decisions?
____ Plans and schedules
____ Software and hardware development process/procedures
____ System training program
____ Quality goals
____ Studies performed and planned
____ Personnel resources/staffing plan (Government and contractor)
____ Project organization structure/communication lines - is it working?
____ Contracting requirements modifications (if necessary) (discussed in Government only session)
____ Metrics collected and analyzed
2) Review project documents
____ Preliminary software requirements specification
____ Preliminary interface requirements specification
3) Approve/Disapprove project documents
____ Final system or subsystem requirement specification
____ System/subsystem design document
____ Software development plan or project management plan
5
Management Review ChecklistsTL-PMC-01 v1.0
1/27/09
____ Configuration management plan
____ Quality assurance plan
4) ___ Clarify decisions and write them down for distribution
System/Subsystem Design Review Exit Criteria:
1) ___ Action items with priority and due date have been assigned
2) ___ Minutes have been reviewed with all attendees present
3) ___ Review has been evaluated/how can we improve?
- Were the facilities adequate?
- Were all of the entrance criteria met?
4) ___ Decision on whether to redo the review has been made
5) ___ Record changes to the schedule/deliverables have been recorded
6) ___ Any possible new risks that have surfaced during the meeting have been reviewed
7) ___ Commitment to continue or not has been made
8) ___ Documents have been approved
9) ___ Decisions/Agreements from the meeting have been recorded
6
Management Review ChecklistsTL-PMC-01 v1.0
1/27/09
SOFTWARE REQUIREMENTS REVIEW CHECKLISTPurpose: The objectives of this review are listed below:
a. Assess the risks associated with plans and requirements.
b. Obtain mutual agreement between the user/customer and the software developer that the requirements specified for the software are complete and accurate, and the requirements represent the development commitment for the software. This establishes the allocated baseline for each configuration item (represented in the software requirements specification(s) and interface requirements specification(s)).
Software Requirements Review Entrance Criteria:
1) Peer Review (Formal Inspection) has been done on these documents:
____ Software requirements specification
____ Interface requirements specification
____ Software Test Plan (recommended, but not required until System Preliminary Design Review)
____ Draft Software User's Manual (optional)
2) Following analyses have been performed:
____ Reliability
____ Safety
____ Security
____ Life cycle cost
____ Human-computer interface
____ Software reuse
____ COTS software
____ Software sizing and performance timing
____ Design methods and tools
____ Programming standards and conventions
3) Review team has been assembled and they have committed to attend
____ Developer: project manager, system manager, system engineer, software development manager, hardware development manager, testing manager, configuration manager, software quality assurance
____ Government:sponsor (program manager), program manager, software project manager, software personnel, hardware personnel, IV&V, users, life cycle support activity, testing activity
4) ___ Prototype is available for review by users (if applicable)
5) Metrics have been collected and analyzed:
____ Requirements testability is 100%
____ Traced requirements is 100%
____ Number of Engineering Change Proposals (ECP) / Software Change Notice(s) (SCN) (since functional baseline established at System Design Review)
7
Management Review ChecklistsTL-PMC-01 v1.0
1/27/09
____ Actual vs. planned staffing profile
____ Documentation defects
____ Action items complete
6) ___ Current WBS is available
7) ___ Current Milestone Schedule and Deliverable Requirements are available
8) ___ If developer is a contractor, contract is current (contract/delivery order should be funded for the review to be held)
Software Requirements Review Tasks:
1) Review:
____ Summary of technical issues/problems from Peer Review held prior to the review
____ Risks
____ Decisions made prior to the review
- Are we making good decisions?
____ Plans and schedules
____ Software quality goals/requirements
____ Studies performed and planned
____ Software design constraints (next phase)
____ Personnel resources/staffing plan (Government and contractor)
____ Project organization structure/communication lines
- Is it working?
- Are CM and QA in place?
____ Contracting requirements modifications (if necessary)(discussed in Government only session)
____ Prototype (opens communication on requirements)
____ Metrics collected and analyzed
____ Special delivery requirement (packaging, formatting of software)
2) Review project documents
____ Draft Software User's Manual (optional)
3) Approve/Disapprove project documents
____ Software requirements specification
____ Interface requirements specification
____ Software Test Plan (recommended, but not required until System Preliminary Design Review)
4) ___ Clarify, write down, and distribute decisions
Software Requirements Review Exit Criteria:
1) ___ Action items with priority and due date have been assigned
2) ___ Minutes have been reviewed with all attendees present
3) ___ Review has been evaluated/how can we improve?
- Were the facilities adequate?
- Were all of the entrance criteria met?
8
Management Review ChecklistsTL-PMC-01 v1.0
1/27/09
4) ___ Decision on whether to redo the review has been made
5) ___ Changes to the schedule/deliverables have been made
6) ___ Any possible new risks that have surfaced during the meeting has been reviewed
7) ___ Commitment to continue or not has been made
8) ___ Documents have been approved
9) ___ Decisions/Agreements from the meeting have been recorded
9
Management Review ChecklistsTL-PMC-01 v1.0
1/27/09
SYSTEM PRELIMINARY DESIGN REVIEW CHECKLISTPurpose: The objectives of this review are listed below:
a. Assess the risks associated with design and test approaches.
b. Evaluate the basic design approach (software or hardware architecture) prior to proceeding with the detailed design effort.
c. Determine whether the design approach satisfies the requirements of the software or system requirements specification and whether the interfaces are compatible with other interfacing systems.
System Preliminary Design Review Entrance Criteria:
1) Peer Review (Formal Inspection) has been done on these documents:
____ Software Test Plan, Section C-3
____ Preliminary Software Design Document or System Design Document
____ Preliminary Interface Design Document
____ Revisions/updates to already baselined documents
2) Following analyses have been performed during top-level architectural design:
____ Partitioning analysis (modularity)
____ Data flow analysis
____ Control flow analysis
____ Computer resource utilization for each software component
____ Human factors
____ Critical timing and sizing
____ Maintainability
____ Reliability
____ Safety
____ Security
____ Performance
3) Review team has been assembled and they have committed to attend
____ Developer:project manager, system manager, system engineer, software development manager, hardware development manager, testing manager, configuration manager, quality assurance
____ Government:sponsor (program manager), program manager, project manager, software personnel, hardware personnel, IV&V, users, life cycle support activity, testing activity
4) ___ Design prototype to determine best architectural design
5) ___ User interface prototype - additional to that reviewed at Software Requirements Review
6) Metrics have been collected and analyzed:
____ Requirements testability is 100%
____ Traced requirements is 100% (requirements to design; requirements to test plan)
____ Number of ECPs/SCNs
10
Management Review ChecklistsTL-PMC-01 v1.0
1/27/09
____ Build/release content profile
____ Actual vs. planned staffing profile
____ Defects
____ Action items complete
____ Design progress
____ Code size
____ Computer resource utilization
____ Cost/Schedule Variance
7) ___ Current WBS is available
8) ___ Current Milestone Schedule and Deliverable Requirements are available
9) ___ Current risk management plan is available
10) __ If developer is a contractor, contract is current (contract must be funded to hold review)
11) __ Cost-to-complete estimate has been completed
System Preliminary Design Review Tasks:
1) Review:
____ Summary of technical issues/problems from Peer Review meeting of documents held prior to this meeting.
____ Risks
- Critical component list
____ Decisions made prior to the review
- Are we making good decisions?
____ Plans, schedules, budgets
____ System or software quality goals
____ Studies performed and planned
____ Partitioning analysis (modularity)
____ Data flow analysis
____ Control flow analysis
____ Computer resource utilization for each software component
____ Human factors
____ Critical timing and sizing
____ Performance
____ Maintainability
____ Reliability
____ Safety
____ Security
____ Detailed design constraints (next phase)
____ Adequacy of tools and facilities
- Development and testing
____ Personnel resources/staffing plan (Government and contractor)
____ Project organization structure/communication lines -is it working?
11
Management Review ChecklistsTL-PMC-01 v1.0
1/27/09
- CM and QA groups
- Interface working group
____ Contracting requirements modifications (discussed in Government only meeting)
____ Prototype (architectural design) (optional)
____ Prototype (user interface) (optional)
____ Metrics collected and analyzed
____ Action items from last review
2) Review project documents
____ Preliminary Software or System Design Document (containing design architectural specification)
____ Preliminary Interface Design Document
3) ___ Approve/Disapprove project documents
4) ___ Be clear and write down decisions and distribute
System Preliminary Design Review Exit Criteria:
1) ___ Action items with priority and due date have been assigned
2) ___ Minutes have been reviewed with all attendees present
3) ___ Review has been evaluated/how can we improve?
- Were the facilities adequate?
- Were all of the entrance criteria met?
4) ___ Decision on whether to redo the review has been made
5) ___ changes to the schedule/deliverables have been recorded
6) ___ Any possible new risks that have surfaced during the meeting have been reviewed
7) ___ Commitment to continue or not has been made
8) ___ Documents have been approved
9) ___ Decisions/Agreements from the meeting has been recorded
12
Management Review ChecklistsTL-PMC-01 v1.0
1/27/09
SYSTEM DETAILED DESIGN REVIEW CHECKLISTPurpose: The objective of this review to assess the risks associated with implementing the detailed
design approach.
System Detailed Design Review Entrance Criteria:
1) Peer Review (Formal Inspection) has been done on these documents:
___ Final Software or System Design Document (no TBDs allowed)
___ Final Interface Design Document (no TBDs allowed)
___ Test Descriptions (Cases)
___ Revisions/updates to any baselined documents
2) Following analyses have been performed during top-level architectural design:
___ Computer resource utilization for each software component
___ Human factors
___ Critical timing and sizing
___ Maintainability
___ Reliability
___ Safety
___ Security
___ Performance
___ Undesired event handling
___ Algorithm accuracy
3) Review team has been assembled and they have committed to attend
____ Developer:project manager, system manager, system engineer, software development manager, hardware development manager, design manager, configuration manager, testing manager, quality assurance
___ Government:sponsor (program manager), program manager, project manager, software personnel, hardware personnel, IV&V, users, life cycle support activity, testing activity
4) Metrics have been collected and analyzed:
____ Requirements testability is 100%
____ Traced requirements is 100% (requirements to design to tests)
____ Number of ECPs/SCNs
____ Build/release content
____ Actual vs. planned staffing profile
____ Documentation/product defects
____ Action items complete
____ Design progress
____ Code size estimates
____ Computer resource utilization
____ Cost/Schedule Variance
13
Management Review ChecklistsTL-PMC-01 v1.0
1/27/09
5) ___ Current WBS is available
6) ___ Current Milestone Schedule and Deliverable Requirements are available
7) ___ Current risk management plan is available
8) ___ If developer is a contractor, contract is current
9) ___ Cost-to-complete estimate completed
System Detailed Design Review Tasks:
1) Review:
____ Risks
- Critical component list
____ Decisions made prior to the review
- Are we making good decisions?
____ Plans, schedules, budgets
____ System or software quality goals
____ Implementation constraints (next phase)
____ Tools and facilities for system or software implementation
____ Tools and facilities for testing
____ Personnel resources/staffing plan (Government and contractor)
____ Organization structure/communication lines -is it working?
- CM and QA
- Interface working group
- Testing group
____ Contracting requirements
____ Metrics collected and analyzed
____ Action items from last review
2) ___ Approve/Disapprove project documents
3) ___ Make decisions - Be clear and write them down for distribution
System Detailed Design Review Exit Criteria:
1) ___ Action items with priority and due date have been assigned
2) ___ Minutes have been reviewed with all attendees present
3) ___ Review has been evaluated/how can we improve?
- Were the facilities adequate?
- Were all of the entrance criteria met?
4) ___ Decision on whether to redo the review has been made
5) ___ Changes to the schedule/deliverables have been recorded
6) ___ Any possible new risks that have surfaced during the meeting have been reviewed
7) ___ Commitment to continue or not has been made
8) ___ Documents have been approved
9) ___ Decisions/Agreements from the meeting have been recorded
14
Management Review ChecklistsTL-PMC-01 v1.0
1/27/09
TEST READINESS REVIEW CHECKLISTPurpose: The objective of this review is to determine if the developer is ready to conduct software
or hardware testing or Formal Qualification Testing (FQT).
Test Readiness Review Entrance Criteria:
1) Peer Review (Formal Inspection) has been done on these documents:
____ Test procedures
____ Configuration items
____ Configuration item documents containing test results from component testing
2) ___ Component testing has been completed
3) ___ Current Test Plan is available
4) Review team has been assembled and they have committed to attend
____ Developer:project manager, system manager, system engineer, software development manager, hardware development manager, testing manager, configuration manager, quality assurance
____ Government:sponsor (program manager), program manager, software project manager, IV&V, users, life cycle support activity, testing activity
5) Metrics have been collected and analyzed:
____ Requirements testability is 100%
____ Traced requirements is 100% (test cases to procedures)
____ Number of ECPs/SCNs (since functional baseline established at SDR)
____ Actual vs. planned staffing profile
____ Documentation defects
____ Configuration item defects
____ Action items complete
____ Build/release content
____ Testing progress (number of tests completed)
6) ___ Current WBS is available
7) ___ Current Milestone Schedule and Deliverable Requirements are available
8) ___ If developer is a contractor, contract is current (contract/delivery order should be funded for the review to be held)
Test Readiness Review Tasks:
1) Review:
____ Summary of technical issues/problems from Peer Reviews held before this review
____ Risks
____ Decisions made prior to the review
- Are we making good decisions?
____ Current test plans and schedules
15
Management Review ChecklistsTL-PMC-01 v1.0
1/27/09
____ System or software quality goals
____ Studies performed and planned
____ Testing constraints/limitations (next phase)
____ Personnel resources/staffing plan (Government and contractor)
____ Project organization structure/communication lines - is it working?
____ Contracting requirements modifications (if necessary) (discussed in Government only session)
____ Metrics collected and analyzed
____ Ensure that the test environment, all facilities, including support hardware and software, simulators, emulators, testing tools, is available to conduct the testing
____ Status of known software problems
____ Changes since System Detail Design Review to design documentation
____ Results from a dry-run of FQT procedures (optional)
2) Approve/Disapprove project documents
____ Test Procedures
3) ___ Clarify, write down, and distribute all decisions
Test Readiness Review Exit Criteria:
1) ___ Action items with priority and due date have been assigned
2) ___ Minutes have been reviewed with all attendees present
3) ___ Review has been evaluated/how can we improve?
- Were the facilities adequate?
- Were all of the entrance criteria met?
4) ___ Decision on whether to redo the review has been made
5) ___ Changes to the schedule/deliverables have been recorded
6) ___ Any possible new risks that have surfaced during the meeting have been reviewed
7) ___ Commitment to continue or not has been made
8) ___ Documents have been approved
9) ___ Decisions/Agreements from the meeting have been recorded
16