Project Management Workbook Index

The Project Management Workbook (PMW) is the governing document, from the initial authorization for work, through the
implementation phase. This workbook, in conjunction with the Budget Tracking Workbook (BTW), the Status Tracking Workbook
(STW) and a detailed Microsoft Project Schedule, constitute the Software Development Plan for this project. Refer to the index
below for a summary of the PMW content.

Instructions Provides instruction on when to update this workbook during the life of the project. Additionally, it
indicates when the BTW, STW and MS Project Plan must be created/updated.
Project Initiation
ROM Record ROM estimate of size and effort and associated assumptions

Project Planning
Project Log Track project risks, lessons learned, new requirements, CM and QA Findings
Estimate Record detailed estimates (effort hrs, schedule, and assumptions)
Resources Project team and master communications plan
Standards Record project standards, CM Plan-config items/units, QA Plan, team responsibilities

Project Control
Test Log OPTIONAL: log used to record and track test plan and results

Approvals Approvals required and received by work product

11/09/2017
 PMW Instructions

PROJECT INITIATION Tab Workbook

Required
1) Enter ROM estimate budget with assumptions. ROM Budget BTW
2) Enter ROM size estimates and schedule with assumptions ROM PMW
3) Detail how Labor Category hours break out into life cycle tasks (high level WBS) Estimate Backup & BTW
and record Assumptions Assumptions
5) Record approvals for Work Package Approvals PMW
Enter if applicable
5) Enter any known staffing and/or facilities/tools requirements ROM Budget BTW
6) Enter known resources Resources PMW
7) Enter customer imposed standards Standards PMW
8) Enter any budget tracking/invoice requirements Budget Tracking BTW
CM Requirements
Prior to Work Package Approval - Store PMW in LAN Project Directory until project is approved.
After Work Package Approval - Create a project directory in VSS and store the current PMW.

PROJECT PLANNING Tab Workbook

Required
Software Development Plan (authored by the PM or designee)
1) Copy ROM estimate to Detailed Budget and revise per known requirements Detailed Budget BTW
2) Copy ROM schedule to Estimate schedule and revise per known requirements and Estimate PMW
Detailed Budget revisions
3) Enter detailed project schedule and assumptions in MS Project Plan N/A Project Plan
4) Enter budget information and customer billing requirements Budget Tracking BTW
5) Review/Update billing rates for the contract - match to Contract Order Rate BTW
6) Enter risks along with mitigation plan Project Log PMW
7) Enter Project Team including customer contacts and other affected groups Resources PMW
8) Enter/Update facilities and tools requirements ROM Budget BTW
9) Enter/Update customer imposed standards Standards PMW
10) Enter standard procedures and tools to be followed - indicate any deviations to Standards PMW
JMCS standards
CM Plan (authored by the CM Manager)
11) Enter CM and CCB resources and responsibilities Resources PMW
12) Identify configuration items/units, file names and project directory Standards PMW
13) Enter CM estimate, facilities and tools requirements Estimate PMW
QA Plan (authored by the QA Manager)
14) Enter QA resources Resources PMW
15) Enter estimate, facilities and tools ROM BTW
16) Enter QA activities, procedures, tools and standards to be followed Standards PMW

17) Record approvals for Requirements Doc, SDP, CM and QA Plans Approvals PMW
CM Requirements
Draft Copies - Store PMW in LAN Project Directory until project plan is approved.
After PMW Approval - Save the current version of PMW in VSS.

PROJECT CONTROL Tab Workbook

18) Update status on risks Project Log PMW
19) Record actual effort expended and actual schedule Status STW
20) Record approvals for Technical Requirements Document, Revised Requirements Approvals PMW
Document and Project Plan, and Test Plan (as required)
21) Record updated estimate and reason for replan (if applicable) Estimate PMW
22) Record updated schedule and reason for replan Status STW
23) Record reason for missed budget or schedule milestone after each phase Project Log PMW
completion
24) Record lessons learned throughout the project Project Log PMW
25) Create and distribute Status report for customer/sr management Status STW
26) Enter and track to closure CM and QA audit findings Project Log PMW
CM Requirements
Draft Copies - Store PMW in LAN Project Directory until project plans are re-approved.
After PMW Re-Approval - Save the new version of PMW in VSS.

PROJECT CLOSING Tab Workbook

27) Record approvals for release of baseline to production Approvals PMW
28) Record final lessons learned Project Log PMW
29) Record final project actuals Status STW
CM Requirements
After project completion - Save the final version of PMW, BTW, and STW in VSS.

PMW Instructions Tab 11/09/2017 Page 2

 Initial Project Commitments
(ROM Estimate)

ROM Estimate and Schedule

Effort Planned Planned

Phase 1 Hours Start Date End Date
Planning/Analysis 64 29-Oct 16-Nov
Design Phase 114 19-Nov 30-Nov
Technical Platform 122 19-Nov 25-Jan
Code & Unit Test 430 26-Nov 14-Dec
Acceptance Test 121 17-Dec 21-Dec
Implementation 45 24-Dec 28-Dec
Project Management
Quality Assurance
<Other>
<Other>

Comments: There was no separate ROM and Detailed Estimate. They are the same. Assumptions are detailed in \ABC\Cost
estimates\ABC SOW assumptions.doc.

ROM Size Estimates -- Phase 1

Types of Objects Object Counts

Easy Medium Complex
Database tables 14 14 7
Screens (web pages,
windows) 1 20 8

Stored (server) procedures 1 27 0

Reports 0 20 8
Interfaces 1 0 0
Other 0 0 0

Effort Planned Planned

Phase 2 Hours Start Date End Date
Planning/Analysis 292 31-Dec
Design Phase 62
Code & Unit Test 438
Acceptance Test 121
Implementation 25 5-Apr
Documentation
Project Management
Quality Assurance
<Other>
<Other>

Comments: Assumptions are detailed in \ABC\Cost estimates\ABC SOW assumptions.doc.

ROM Size Estimates

Types of Objects Object Counts

Easy Medium Complex

PMW ROM Tab 11/09/2017 Page 3

 Initial Project Commitments
(ROM Estimate)

Database tables
Screens (web pages,
windows)

Stored (server) procedures

Reports
Interfaces
Other

PMW ROM Tab 11/09/2017 Page 4

 Initial Project Commitments
(ROM Estimate)

Assumptions

Spread across all the other tasks

tailed Estimate. They are the same. Assumptions are detailed in \ABC\Cost
oc.

Assumptions

Spread across all the other tasks

ost estimates\ABC SOW assumptions.doc.

PMW ROM Tab 11/09/2017 Page 5

 Initial Project Commitments
(ROM Estimate)

This is unknown because this phase has not been defined yet

PMW ROM Tab 11/09/2017 Page 6

 Project Estimate

Detailed Estimate and Schedule

Effort Planned Planned

Phase 1 Hours Start Date End Date
Planning/Analysis 64 29-Oct 16-Nov
Design Phase 114 19-Nov 30-Nov
Technical Platform 122 19-Nov 25-Jan
Code & Unit Test 430 26-Nov 14-Dec
Acceptance Test 121 17-Dec 21-Dec
Implementation 45 24-Dec 28-Dec
Project Management
Quality Assurance
<Other>
<Other>

Comments: There was no separate ROM and Detailed Estimate. They are the same. Assumptions are detailed in \ABC\Cost
estimates\ABC SOW assumptions.doc.

ROM Size Estimates -- Phase 1

Types of Objects Object Counts

Easy Medium Complex
Database tables 14 14 7
Screens (web pages,
windows) 1 20 8

Stored (server) procedures 1 27 0

Reports 0 20 8
Interfaces 1 0 0
Other 0 0 0

Effort Planned Planned

Phase 2 Hours Start Date End Date
Planning/Analysis 292 31-Dec
Design Phase 62
Code & Unit Test 438
Acceptance Test 121
Implementation 25 5-Apr
Documentation
Project Management
Quality Assurance
<Other>
<Other>

Comments: Assumptions are detailed in \ABC\Cost estimates\ABC SOW assumptions.doc.

ROM Size Estimates

Types of Objects Object Counts

Easy Medium Complex
Database tables
Screens (web pages,
windows)

Stored (server) procedures

PMW Estimate Tab 11/09/2017 Page 7

 Project Estimate

Reports
Interfaces
Other

PMW Estimate Tab 11/09/2017 Page 8

 Project Estimate

Assumptions

Spread across all the other tasks

nd Detailed Estimate. They are the same. Assumptions are detailed in \ABC\Cost
ons.doc.

Assumptions

Spread across all the other tasks

BC\Cost estimates\ABC SOW assumptions.doc.

This is unknown because this phase has not been defined yet

PMW Estimate Tab 11/09/2017 Page 9

 Project Log

Project Name: ABC Reporting BACK TO INDEX TAB

Phase Number 1
Activity Identification Activity Resolution

Estimated
Act. Phase Resource Date Effort
ID Stat Prty Description Originator Date Disc. Complete Resolution
Type Disc Assigned Closed Hours
Date (ECD)

1 O N 1 New requirement to be able to download data for any report into USPS ABC C Estimate provided to USPS for developing
Excel team this capability.
2 O N 1 Requirement to change the date for moving the first five reports Jim Grahn 12/17/2001 C 0 On 12/28, Jim Grahn sent an email to Peter
into production from 12/28/2001 to 2/25/2002. Tuttle, the COR, asking him to modify the
SOW.
3 O N 1 Requirement to change the date for moving the second five Jim Grahn 12/17/2001 C 0 On 12/28, Jim Grahn sent an email to Peter
reports into production from 1/15/2002 to 2/25/2002. Tuttle, the COR, asking him to modify the
SOW.
4 O N 1 New requirement to show only direct activities in the AUC - Other John Kelley 1/15/2002 A Joe Schultz 1/15/2002 1 Change made.
report (these are activities that have a code beginning with 'DA'.
This would eliminate the following activities from that report:
TRANSPORTATION, NON-PLANT, and MAINTENANCE-
OUTSIDE.
5 O
6 O
7 O
8 O
9 O
10 O
11 O
12 O
13 O
14 O
15 O
16 O
17 O
18 O
19 O
20 O
21 O

PMW Project Log Tab 11/09/2017 Page 10

 Project Standards and Procedures

This worksheet contains a plan for how the project will be managed. It covers the standards and procedures that the project will follow, the
method/mode/frequency of the different types of statusing to be done, the environment assumptions about the project, the configuration items that will be
used to control the project throughout the SDLC and the plan for ensure requirements are met and procedures are followed.

TABLE OF CONTENTS
Project Standard Procedures List of the standards and tools to be employed by this project.
Project Status
Status Meetings Describes the type, purpose, attendees, frequency and location of project team meetings.
Status Reports Describes the type, purpose, recipients, frequency and location of status reports.
Project Environment Assumptions about the environment to be employed by this project.
Project Configuration Items
Documentation Documentation work products that will be used to document and control this project
Source List of source units that is used for managing the project and organizing the CM Lib
Development Tools List of development tools to be used in the project and the version numbers/dates
Project Quality Assurance
Testing Plan for testing product to ensure customer requirements are met
QA Audits/Reviews Plan for audits and reviews to be performed

PMW Standards Tab 11/09/2017 Page 11

 Project Standards and Procedures
PROJECT STANDARD PROCEDURES/TOOLS
This standards and procedures can be located <insert location>
Functional Area Process Asset
Software Development Lifecycle SDLC Process Document - <indicate
selected lifecycle>
Project Management Project Management Workbook
- Risks PMP - Risk Mgmt Procedures
- Schedule PMP - Scheduling Procedures
- Estimate PMP - Estimating Procedures
- Project Plan PMP - Project Planning Procedures
Requirements Management Requirements Document
Requirements Management Procedures
PMW - Project Log tab
Configuration Management Project Management Workbook - CM Plan
JMCS Standard SCM Plan
CM Procedures
SNAFU Procedures
Software Quality Assurance SQA Plan
SQA Procedures
Project Management Workbook - QA Plan
PMW Standards Tab
Description Version
Date
Defines the standard lifecycle phases and
activities for two lifecycles.
Main tool used on all projects to record and 12/18/2001
manage estimate, schedule, risks,
facilities/tools plan
Instructions for identifying/managing risks
Instructions for identifying/managing
schedules
Instructions for identifying/managing
estimates
Instructions for identifying/managing SDP
Record requirements baseline during
Planning Phase
Instructions for identifying/managing
requirements
Used to manage change in requirements after 12/18/2001
the Planning Phase
Used to manage baseline releases and issues
with the baseline.
11/09/2017 Page 12
 Project Standards and Procedures

PROJECT STATUS

Status Purpose Required Attendees Frequency

Team Status Review project status - schedule, estimate, risks, Project Leader and all JMCS project team Bi-Weekly
issues members (miniminum)
Team Leads Meeting Inform Sr Mgmt of project status and Sr Mgmt, Team Leads Bi-Weekly
escalation project barriers (miniminum)
QA Status Review Give QA status and escalation QA Manager, Sr Mgmt Monthly (or ad
noncompliance issues hoc as
needed)
Project Status Report Inform Sr Mgmt of project status and Sr Mgmt Bi-Weekly
escalation project barriers (miniminum)

SQA Status Report Summarized status of QA audits and findings Sr Mgmt Monthly
including summary of open noncompliance
issues

<insert other status report or meeting, as <indicate purpose of additional status report <indicate required attendees or recipients of <input
required> or meeting> the status> frequency of
status>

Comments: <insert any other special notes about project statusing and/or communication>

PMW Standards Tab 11/09/2017 Page 13


PROJECT CONFIGURATION ITEMS/UNITS
Documentation
Work Package
Project Management Workbook
Project Initiation baseline
Requirements baseline
Design baseline
Change Control baselines
Software Development Plan
Project Planning/Analysis end
Revisions to SDP
Requirements Document
Requirements baseline
Revisions to baseline
Project Schedule
ROM
Detailed Schedule
Changes to Planned Schedule
Meeting Minutes
Customer/CCB Mtg Minutes
SQA Review Meeting Minutes
Team Lead Status Mtg Minutes
Project Team Status Meeting Minutes
Status Report
PMW Standards Tab
Project Standards and Procedures
Version Control Location/File Name Assignee
Store Work Package on LAN until project is VSS/wp_usps_<project name>.doc Consulting
approved. Then store in VSS. Mgr
PMW is kept in the Project Directory in the VSS/pmw_usps_<project name>.doc PM
LAN. A copy must be saved in VSS after <NOTE: keep working copy on LAN>
Project Initiation, Project Planning, Design,
and any other times the project commitments
change (SDP, CM, or QA items)
SDP is a subsection of the Project See Project Management Workbook PM
Management Workbook and will be archived
per the PMW requirements listed above.
The Reqs Doc must be saved in VSS upon VSS/req_usps_<project name>.doc Business
approval at the end of the Project Planning Analyst
stage and when project changes require
updates to the requirements
Project Schedule is kept in the Project VSS/ps_usps_<project name>.mpp PM
Directory in the LAN. A copy must be saved NOTE: If project is small enough an MS
in VSS after Project Initiation, Project Project Schedule is not required. In which
Planning, Design, and any other times the case the schedule is recorded in the PMW
planned schedule changes. and adheres to the CM standards for PMW.
All meeting minutes are stored in the Project LAN/ccbmm_usps_<project name>_date.doc CM Mgr
Directory on the LAN. LAN/sqamm_usps_<project name>_date.doc SQA Mgr
LAN/tlmm_usps_<project name>_date.doc TBD
LAN/ptmm_usps_<project name>_date.doc PM
11/09/2017 Page 14
 Project Standards and Procedures

Sr Mgmt Status Report All status reports are stored in the Project LAN/msr_usps_<project name>_date.doc PM
Customer Status Report Directory on the LAN. LAN/csr_usps_<project name>_date.doc PM

SCM Plan
Project Planning/Analysis end
Revisions to CM Plan
The CM Plan must be saved in VSS upon VSS/scmp_usps_<project name>.doc SCM Mgr
approval at the end of the Project Planning
stage and when project changes require
updates to the plan.

SQA Plan
Project Planning/Analysis end QA Plan is a subsection of the Project See Project Management Workbook SQA Mgr
Revisions to QA Plan Management Workbook and will be archived
per the PMW requirements listed above.

Test Plan Should be created and saved in Project LAN/tp_usps_<project name>.doc Tester
Directory on LAN prior to starting System
Test

Release Notes Should be created and saved in Project LAN/rn_usps_<project name>.doc CM Mgr
Directory on LAN prior to going to Production

Optional Documents
Design Document <insert CM versioning requirements> <location>/dd_usps_<project name>.doc TBD
Users Guide <insert CM versioning requirements> <location>/ug_usps_<project name>.doc TBD
Users Manual <insert CM versioning requirements> <location>/um_usps_<project name>.doc TBD
<insert any Customer Deliverables> <insert CM versioning requirements> <location>/<naming std>_usps_<proj name>.d TBD

Source File Name Location

<insert source configuration items and <location>
units> <refer to CM Procedures>

Development Tools Version # Location/File Name

<insert development tool> <insert version #> <location>

PMW Standards Tab 11/09/2017 Page 15

 Project Standards and Procedures

PROJECT QUALITY ASSURANCE

Testing
<insert the plan for testing the product to ensure along the SDLC that the customer requirements are met by the final production baseline.>

Quality Assurance Audits/Reviews

Work Product Audits All configuration items Audit will be performed upon completion of
work product
Work Process Audits Requirements Management Process Random audits will be conducted throughout
Project Management Process the life of the project
Configuation Management Process
Reports SQA Status Report Reports will be provided to Sr management
on a monthly basis

Noncompliance Process Give a summary as to how the noncompliance issues will be escalated on the project. Specify individuals to
escalate to.

PROJECT TEAM RESPONSIBILITIES

ROLE ASSIGNED RESOURCE RESPONSIBILITIES

SQA <insert assignee> <List SQA responsibilities>

PM <insert assignee> <List PM responsibilities>

Configuration Management
CM Manager <insert assignee> Manage Configuration Control Board -
organize meeting, facilitate meeting,
document meeting minutes
Develop/maintain/distribute CM plan, stds,
procedures
Identify work products and configuation items
under CM
DBA Create CM Library
Manage access to CM Library
Create/update software baselines
Conduct production software baseline audits

PMW Standards Tab 11/09/2017 Page 16

 Project Team

Project Team INDEX

Team Role Name Responsibilities for customer obligations CCB Develop Production
Member Security Security
Customer Team COR - Contracting Officer Peter Tuttle Signs contract, travel authorization, 1357s
Members Representative <Y or N> N/A N/A
COTR - Contracting Officer Jim Grahn Approves technical scope
Technical Representative Y R R
Customer Sponsor Jean Parris Lead within user organization responsible
for approving deliverables - Approves
detailed requirements Y R R
Business Analyst Bill Green Supplies detailed requirements and report
layouts <Y or N> R R
Business Analyst John Kelley Supplies detailed requirements for
aggregation algorithms; tests aggregations
and calculations <Y or N> R R
Business Analyst Cathy Ruth Approves report layouts; responsible for
training <Y or N> R R
Business Analyst, Technical John South Supports Metify interface; general Oracle
Support support; tests reports <Y or N> R R
Business Analyst Joe Hurley <Y or N> R R
General support Linda Threatt <Y or N> R R
Technical Support Doug Watson Supports Metify interface; general Oracle
support <Y or N> R, W, A, D R
Johnston McLamb BAD Wendy Henry Authorize all project commitments and
Team Members changes (budget, schedule, resources).
Remove project barriers <Y or N> R, W, A, D R
Project Manager Bill Knecht Provides customer status, and escalate
project issues/barriers - Manages CCB -
organize/run meeting
Develop Project Plan
Create Requirements Document Y R, W, A, D R
DBA Tom Abrials DBA support for all ABC databases <Y or N> R, W, A, D R, W, A, D
Analyst/Developer Anna Karneh Lead for designing and developing ABC
reports <Y or N> R, W, A, D R
Bus. Objects Programmer Joe Schultz Programs ABC reports N R, W, A, D R
Database Design Review Gavin Martin Assists with DBA support and schema
design review N R, W, A, D R
Database Design Review Lakshmi Purushothaman Schema design review N R, W, A, D R
Other Impacted Business Analyst Eric Rodgers (PWC)
Group Team Members
N R R

[Tab] 11/09/2017 Page 17

 Project Team

Metify Analyst/Developer Tim Gatts (Armstrong Laing) Developer and technical support for Metify
data extract utility N N/A N/A

<Critical Dependencies will be listed in the MS Project Plan version date ???>
RESOURCE REQUIREMENTS

Staffing
Need someone who can define a Business Objects universe.
Need two Business Objects report developers.

Materials

We need a software interface that extracts data from the ABC Metify database and loads that data into the ABC Reporting Oracle databse. Armstrong Laing is responsible
for developing that interface and delivering it by the end of Novenber.

Environment

This project does not require the use of any non-standard software development tools or development environments.

Communication Plan

Status Purpose Meeting Frequency Required Attendees Location

Weekly Project Status Entire team reviews status of all Every Monday Jim Grahn, Jean Parris, Bill Green, John Telecon
Telecon project activities Kelley, Cathy Ruth, John South, Joe Hurley,
Linda Threatt, Doug Watson, Eric Rodgers,
Bill Knecht, Anna Karneh
Monthly JMCS Status Report status of all JMCS activities Last day of every month Supplied to Peter Tuttle and Jim Grahn <indicate where
Report to the COR and COTR master copies are
kept>

Comments: <insert any other special notes explaining how the groups will interface. A good example would be to explain the escalation path for
unresolved issues between impacted groups and Johnston McLamb>

[Tab] 11/09/2017 Page 18

 Project Approvals

This worksheet is used to track the approvals of the various different work products. Fill in the name of the individual filling each role across the top row. Approval
requirements of each work product is provided in the matrix by project team role . (A = Approval Required, R = Review Only) Enter the date the approval was received from
that individual over top of the approval requirement code. Enter approvals received (via e-mail, verbal, etc.) in the Approval Detail at the bottom of this page.
BACK TO INDEX TAB

<Affected Group 2>

<Affected Group 3>

Configuration Mgr>

<Software Quality
Wendy Henry

Cathy Banks

Assurance>
John Kelley
Bill Knecht

<Software
Bill Green
Version Date
Work Product Date Sent Comments
Work Package 11/27/2001 11/27/2001 ? - 11/19/2001 <A> - - - - -
Requirements Doc <A> <R> <A> <A> <R> <R> <R> - -
First 5 reports
Written requirements 12/6/2001 12/6/2001 12/14/2001 12/7/2001 12/7/2001 12/14/2001
Report layouts 12/6/2001 12/6/2001 12/14/2001 12/7/2001 12/7/2001 12/14/2001
Aggregation formulas 12/5/2001 12/5/2001 12/7/2001 12/7/2001 12/5/2001
Software Dev Plan <A> <R> <R> <R> <R> <R> <R> <R> <R>
Project Schedule <A> <R> <A> <A> <R>* <R>* <R>* - -
SQA Plan <A> <R> - - - - - - <A>
SCM Plan <A> <R> - - - - - <A> <R>
Technical Design <A> <A> - - <R> <R> <R> - -
Code <R> <R> - - - - - - -
Acceptance Test - - <R> <R> <A> - - - -
Release #1 <R> - <A> <A> <R> <R> <R> - -
Release #2 <R> - <A> <A> <R> <R> <R> - -
Release #3 <R> - <A> <A> <R> <R> <R> - -

Approval Detail

Approval Date Approval Comment/E-mail

<copy and paste approval e-mail or alternate approval received (I.e., verbal approval on phone).>

Approvals 11/09/2017 Page 19

 Project Test Plan

Testing for Phase 1 BACK TO INDEX TAB

First 5 Business Objects reports

Status
Test ID Description (Script) of Test Setup Requirements Expected Results Method of Verification Originator (O,I,F,C)
Test procedures that load data into the ABC Data must be loaded into the ABC
1 data mart tables from the ABC data tables and data tables and cross reference
cross reference tables. tables first. Anna Karneh C
Test aggregation routines to ensure that they Data must be loaded into the data All aggregated numbers are calculated correctly Compare our aggregated numbers to ones that
2 are calculating the aggregations correctly. mart tables. based on the aggregation formulas that John Kelley were calculated using John Kelley's own Anna Karneh
provided. aggregation routines. John Kelley (USPS) C
Test calculations that occur within the Business Data must be loaded into the data All calculations are performed correctly. Compare our calculated numbers to ones that Anna Karneh
3 Objects reports mart tables. were calculated by routines from John Kelley and John Kelley (USPS)
John South. John South (USPS) O
Test data selection criteria for each report. Data must be loaded into the data All data selection criteria specified in the report Compare available selection criteria with what is
mart tables. requirements are available for each report. specified in the report requirements.
4 When each report is displayed, it contains only the Run SQL queries with the same selection criteria
data that satisfy the selection criteria. and compare the results to the reports.
O
Test the ability to produce the reports in Data must be loaded into the data Each report will match the report layout in the report Visual comparison with report mockups in the
5
Business Objects. mart tables. requirements. report requirements document. O

371176873.xls/Test Log 11/09/2017 Page 20 of 21

 Project Test Plan

Unit Test Acceptance Test

Resource Date Date Status Resource Date Date
Assigned Assigned Completed Actual Results (O,I,F,C) Assigned Assigned Completed Actual Results

Anna Karneh 11/19/2001 11/30/2001 All data verified as correctly loaded. N/A
Testing successful. John accepted the
All aggregation routines verified results of the JMCS aggregation
Anna Karneh 12/7/2001 12/11/2001 working correctly. C John Kelley 12/10/2001 12/14/2001 routines.

John Kelley
Anna Karneh 12/12/2001 I John South 12/17/2001

Anna Karneh
Joe Schultz O
Anna Karneh
Joe Schultz O

371176873.xls/Test Log 11/09/2017 Page 21 of 21