Implementing a Project Delivery Framework by John Napier, PMP, CSM

1. Project Delivery
Framework
1
John Napier

2. Project Delivery Framework - PDF
 To create a common language that can be used across the entire firm for consistent project
interpretation and cross impact project collaboration.
 To provide foundational guidance for newly integrated units to incorporate major processes.
 To enable consistent financial reporting, compilation and aggregation of critical project reporting
and analysis.
 To enable more productive integration of cross-impact and firm-wide processes and tools.
 To enable more effective process development and integration.
 To enable more effective and accurate process analysis, measurement and improvement, in the
future.
 To enable more efficient mobility in the workforce to work in different projects with the same
common understanding and faster startup.
2

3. Phase Definitions
0.0
Concept
1.0 Initiation
2.0 Requirements
3.0 Design
Project
4.0
Build
5.0
Test
Management
6.0 Implementation
7.0 Project
Closure
Processes
The objective of each phase has been defined to ensure consistency in use of the
phase reference. E.g. When LOBs report a project is in the Requirements phase,
the same kinds of activity are in progress and expectation of the deliverables of that
phase are consistent.
More detailed specific processes will be defined at the LOB level to fit their
organizational construct and governance needs, as well as the firmwide process
requirements.
3

4. Phase 0.0 Concept
0.0
Concept
1.0 Initiation
2.0 Requirements
3.0 Design
Project
4.0
Build
5.0
Test
Management
6.0 Implementation
7.0 Project
Closure
Processes
•0.0 Concept:
To
 take the ideas and intentions of a group of people and evaluate them to determine if there is
business value for a project and converts them into a formal, planned project request
in a way that
 establishes a convincing business case (cost benefit / strategic need) for the project
 clearly and explicitly defines the business objectives and scope and provides supporting
documentation
 defines the high level business requirements for the project
 gains commitment and approval of the project from the appropriate level of senior management
so that
 a project request can be completed
 the initiation of project scoping and understanding of high level business requirements can
commence by partnering with technology
 project requests can be prioritized based on high level estimated business benefit.
4

5. Phase 1.0 Initiation
0.0
Concept
1.0
Initiation
2.0 Requirements
3.0 Design
Project
4.0
Build
5.0
Test
Management
6.0 Implementation
7.0 Project
Closure
Processes
1.0 Initiation:
To
 take a request for a project from the sponsor to define high level scope, plans and estimates
in a way that
 elaborates on the business case (cost benefit / strategic need) for the project
 clearly and explicitly defines the project objectives and scope
 defines a project organization structure which can be used to effectively manage and carry out
the necessary project work
 develops an high level schedule of milestone activities and resources required
 produces tangible measures of success for the product
 gains commitment and approval of the project from the appropriate level of senior management
so that
 a high level plan and refined business case estimate can be developed
 detailed requirements analysis and system design can commence
 the probability of producing a high quality product on budget and on schedule is maximized.
5

6. Phase 2.0 Requirements
0.0
Concept
1.0 Initiation
2.0
Requirements
3.0 Design
Project
4.0
Build
5.0
Test
Management
6.0 Implementation
7.0 Project
Closure
Processes
2.0 Requirements
To
 solicit, analyze and validate detail business, technology, and project requirements
 outline a conceptual “to be” process and architecture.
in a way that
 identifies new or modified business process or function requirements
 identifies existing problems that must be solved and constraints to the conceptual strategy
 identifies current system functions that must be retained or altered
so that
 detailed specifications to support product design or new business processes are created
 a high level conceptual solution strategy is defined.
6

7. Phase 3.0 Design
0.0
Concept
1.0 Initiation
2.0 Requirements
3.0
Design
Project
4.0
Build
5.0
Test
Management
6.0 Implementation
7.0 Project
Closure
Processes
3.0 Design:
To
 complete a detailed design that fulfills the specified requirements
in a way that
 elaborates on the business case (cost benefit / strategic need) for the project
 provides detailed specifications for product construction, software / hardware selection,
architecture, dependencies, testing, implementation and impacts
so that
 A detailed project plan, business case and estimates are committed to.
 a solution is defined that will provide detail specifications for product development, software
/ hardware selection and testing and implementation.
7

8. Phase 4.0 Build
0.0
Concept
1.0 Initiation
2.0 Requirements
3.0 Design
Project
4.0
Build
5.0
Test
Management
6.0 Implementation
7.0 Project
Closure
Processes
4.0 Build
To
 build all product components to comply with the requirements and design specifications
 meet required technology and risk controls
in a way that
 produces a functional prototype to demonstrate features and functions (optional)
 ensures the programs / modules compile and integrate
 ensures unit tests are completed and meet expected results
 provides effective test scripts for the testing phase
 enables flexibility for incorporating pilot results
 provides a training plan
so that
 the system is ready for system and user testing
 user documentation and training are ready
 test scripts are ready for test phase.
8

9. Phase 5.0 Test
0.0
Concept
1.0 Initiation
2.0 Requirements 3.0 Design
Project
4.0
Build
Management
5.0
Test
6.0 Implementation
7.0 Project
Closure
Processes
5.0 Test
To
 perform product testing across all affected applications using prepared test scripts
in a way that
 ensures requirements and design specifications have been met
 determines types and order of tests to be run
so that
 the complete working product is ready for user testing
 the product can be implemented using change management processes.
 stability can be ensured in the production environment
9

10. Phase 6.0 Implementation
0.0
Concept
1.0 Initiation
2.0 Requirements 3.0 Design
Project
4.0
Build
5.0 Test
Management
6.0
Implementation
7.0 Project
Closure
Processes
6.0 Implementation
To
 prepare for deployment by readying the technical, working and support environments
 validate final production support readiness
in a way that
 enables the end user to utilize the product effectively
 defines tactics to resolve issues that might arise upon implementation
so that
 there is a smooth transition into the production environment and processes
 the product meets strategic results and provides value to the user.
10

11. Phase 7.0 Project Closure
0.0
Concept
1.0 Initiation
2.0 Requirements 3.0 Design
Project
4.0
Build
5.0 Test
Management
6.0 Implementation
7.0 Project
Closure
Processes
7.0 Project Closure
To
 formally evaluate project processes and close out the project
in a way that
 establishes mechanisms for the continued development or improvement of the final product
 improves the standard process for this type of project
 enhances the estimating model for this type of project
so that
 project resources can be re-deployed
 processes can be continuously improved for more effective project management in the future.
11

12. Phase Project Management Processes
0.0
Concept
1.0 Initiation
2.0 Requirements 3.0 Design
Project
4.0
Build
5.0 Test
Management
6.0 Implementation
7.0 Project
Closure
Processes
Project Management Processes (continuous throughout the life cycle)
To
 ensure project success by applying effective project management methodologies and
practices
in a way that
 enables effective project progress monitoring and control
 establishes regular checkpoints involving the project team and formal reviews
 controls the quality of products in the project
 manages change and risk to the project
 addresses and tracks issues that arise during the course of the project
so that
 the project is delivered to the satisfaction of the requestor
 requirements and changes are managed and controlled throughout the project.
12