The Project Management Workbook (PMW) is the governing document, from the initial authorization for work,

through the implementation phase. This workbook, in conjuction with the detailed Microsoft Project Schedule,
constitute the Software Development Plan for this project. Refer to the index below for a summary of its content.

Project Status Update Status Current budget/schedule & current planned tasks
Project Log Project risks, issues and defects

Project Estimate Estimate Summary Requirements Definition Acceptance Test

Estimate Details Tech Design Implementation
Code & Test Other Costs

Project Testing Test Log Test script and log used in Unit and Acceptance Testing
Project Log Project defects, actions and resolution

Project Team/Resources Resources Project team, staffing, materials and environment needs

Project Approvals Approvals Approvals required and received by work product

Other Project Documents
Commitment History History of commitment changes and root cause info
<project lead - insert hyperlink to
Business Requirements Design ftp://tmpfs318.tmp.allied.com/comm_sys/wr/open/wr#/wr#bd.doc>
<project lead - insert hyperlink to
Technical Design ftp://tmpfs318.tmp.allied.com/comm_sys/wr/open/wr#/wr#td.doc>
Project Initiation Tab
1) Enter risks along with possible mitigation plan Project Log
2) Enter preliminary requirements Project Log
3) Enter known resources Resources
4) Enter known facilities and tools requirements Resources
Enter non-technical customer requirements (e.g., imposed
5) standards or procedures) Obligations
6) Enter ROM estimate with assumptions ROM Estimate
7) Enter preliminary project schedule with assumptions Schedule
8) Record approvals for Work Package Approvals

Project Planning Tab

1) Update risks along with mitigation plan Project Log
2) Finalize Project Team and Customer resources Resources
3) Update facilities and tools requirements Resources
Update non-technical customer requirements (e.g., imposed
4) standards or procedures) Obligations
5) Enter budget from Work Order Obligations
6) Enter detailed estimate with assumptions Detailed Estimate
7) Enter detailed project schedule with assumptions Schedule
Record approvals for Requirements Document and Project
8) Plan Approvals

Project Control Tab

1) Update status on risks Project Log
2) Record actual effort expended and actual schedule Schedule
Record approvals for Technical Requirements Document,
Revised Requirements Document and Project Plan, and Test
3) Plan Approvals
4) Record updated estimate and reason for replan Detailed Estimate
5) Record updated schedule and reason for replan Schedule
Record reason for missed budget or schedule milestone after
6) each phase completion Project Log
7) Record lessons learned throughout the project Project Log
Record and track defects throughout the project (minimum of
8) System Test and Acceptance Test defects) Project Log

Project Closing Tab

1) Record approvals for release of baseline to production Approvals
 ABC Reporting Status for period of <insert date> to <insert date>
Life Cycle Phase: <insert phase name here> <insert group name>
BACK TO INDEX TAB
Project Description Project Status Project Team
<insert description of project purpose, scope, goals, objectives and identified Project Lead <insert Project Lead Name>
benefits as a result of system implementation or enhancement, etc. Specify G Schedule Customer <insert Customer Name>
that system requirements are described in more detail in the statement of work Budget
in the originating workpackage or in the Requirements Document as modified G NOTE: For a complete listing of Project Team members
Resources
by approved requirements listed in the Project Log.> G see Project Team/Resources.

Schedule and Budget Summary -- Phase 1

Planned Planned Actual Planned Actual Remaining
Unit Description Start Date End Date End Date Hours Hrs Hrs Unit Status
Requirements Design Phase 11/13/2001 11/26/2001 11/30/2001 0 0 0 Closed
Technical Design Phase 11/19/2001 12/7/2001 12/7/2001 0 0 0 Closed
Code & Test Phase 11/27/2001 12/28/2001 12/30/1899 0 0 0 Open
Acceptance Test Phase 12/20/2001 12/28/2001 12/30/1899 0 0 0 Open
Implementation 12/28/2001 12/28/2001 12/30/1899 0 0 0 Open
Training N/A N/A 12/30/1899 N/A 0 0 N/A
Documentation N/A N/A 12/30/1899 N/A 0 0 N/A
Project Management 11/13/2001 12/28/2001 12/30/1899 0 0 0 Open
Total Hours 0 0 0
Cost ($) $0 $0 $0
Actions or Comments: Total Estimated
<insert actions planned or comments related to budget or schedule commitments> Project Cost* #REF!

*Contains labor costs and other material costs detailed in estimate.

Last Period's Accomplishments Current Period's Plan

<indicate what work products were completed since the last status update> <indicate what work products are currently being worked on>

Project Risks/Issues See Project Log <insert any additional comments or concerns>

NOTE: Project changes identified after approval of this agreement, which affect the estimated hours, costs or schedule will be re-negotiated as to the project impacted and
incorporated into this tracking document for re-distribution and sign-off.
 Project Log

Work Request Number: BACK TO INDEX TAB

Release Number:
Work Request Description:
Activity Identification A

Act. Date Discovery Date Resource Date Effort

ID Stat Prty Description Originator ECD
Type Disc. Point Assigned Assigned Closed Hours

1 O
2 O
3 O
4 O
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

371490085.xls/Project Log 11/13/2017 Page - 4 of 10

 Project Log

Work Request Number:

Release Number:
Work Request Description:
Activity Resolution Activity Identification Defects
Defect Defect
Act. Point of Defect
ID Stat Resolution Type Impact Root Cause
Type Intro. Cat
(e,o) (l,m,h)

1 O
2 O
3 O
4 O
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

371490085.xls/Project Log 11/13/2017 Page - 5 of 10

 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

371490085.xls/Test Log 11/13/2017 Page 6 of 10

 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

371490085.xls/Test Log 11/13/2017 Page 7 of 10

 Project Team/Resources

PROJECT TEAM BACK TO INDEX TAB

Team Role Name Active

Team
Member?
Customer Team Members COR - Contracting Officer Representative - Peter Tuttle
signs contracts, travel authorization, 1357's
N
COTR - Contracting Officer Technical Jim Grahn
Representative N
Customer Sponsor - Lead within user Jean Parris
organization responsible for approving
deliverables Y
Business Analyst Bill Green, John Kelley, Cathy Ruth, John South, Joe
Hurley, Linda Threatt Y
Technical Support Doug Watson Y
Project Team Members BAD Wendy Henry N
Project Manager Bill Knecht Y
Analyst/Developer Anna Karneh Y
DBA Tom Abrials Y
Developer Joe Schultz Y
Database Design Review Gavin Martin N
Database Design Review Laskhmi P. N
Other Impacted Team Members Business Analyst Eric Rodgers (PWC) Y
Metify Analyst/Developer Tim Gatts (Armstrong Laing) Y

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 database. Armstrong
Laing is responsible for developing that interface and delivering it by the end of November.

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

371490085.xls/Resources 11/13/2017 Page 8 of 10

 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 1>

<Affected Group 2>

<Affected Group 3>

Configuration Mgr>

<Software Quality
<Customer 2>

Assurance>
<Software
App DBA
CM/BAD

USPS
Version Date
Work Product Date Sent
Workpackage 27-Nov 27-Nov ? ? ### - - - - - -
Requirements Doc <A> <R> <A> <A> <R> <R> <R> - -
Reports 1-6
Reports 7-10
Project Schedule <A> <R> <A> <A> <R>* <R>* <R>* - -
SQA Plan <A> <R> - - - - - - <A>
SCM Plan <A> <R> - - - - - <A> -
Technical Design <A> <A> - - <R> <R> <R> - -
Code <R> <R> - - - - - - -
Acceptance Test - - <A> <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).>

371490085.xls/Approvals 11/13/2017 Page 9 of 10

 Project Commitments

Work Request # BACK TO INDEX TAB

Description
Project Estimate (hrs) 0
Project Actual (hrs) 0

Current Plan Plan Date <Insert date of plan>

Phase: Start Date End Date Effort Hours

Status Reason for Missed Milestone
First 5 reports Planned Actual Planned Actual Estimate Actual Remaining
Requirements Definition 11/13/2001 11/13/2001 11/26/2001 ### Closed
Technical Design 11/19/2001 11/19/2001 12/7/2001 12/7/2001 Closed
Code & Test 11/27/2001 11/29/2001 12/28/2001 Open
Acceptance Test 12/20/2001 12/28/2001 Open
Implementation 12/28/2001 12/28/2001 Open
Training N/A N/A N/A N/A
Documentation N/A N/A N/A N/A
Project Management 11/13/2001 12/28/2001 Open

Revision History

Historic Plan 1 Plan Date <Insert date of plan>

Phase Start Date End Date Effort Hours

Status Reason for Missed Milestone
Planned Actual Planned Actual Estimate Actual Remaining
Requirements Definition
Technical Design
Code & Test
Acceptance Test
Implementation
Project Management
Reason for Replan <explain reason for replan and reference PCN # (if applicable)>

Historic Plan 2 Plan Date <Insert date of plan>

Phase Start Date End Date Effort Hours

Status Reason for Missed Milestone
Planned Actual Planned Actual Estimate Actual Remaining
Requirements Definition
Technical Design
Code & Test
Acceptance Test
Implementation
Project Management
Reason for Replan <explain reason for replan and reference PCN # (if applicable)>

Historic Plan 3 Plan Date <Insert date of plan>

Phase Start Date End Date Effort Hours

Status Reason for Missed Milestone
Planned Actual Planned Actual Estimate Actual Remaining
Requirements Definition
Technical Design
Code & Test
Acceptance Test
Implementation
Project Management
Reason for Replan <explain reason for replan and reference PCN # (if applicable)>

371490085.xls/Schedule 11/13/2017 Page 10 of 10