Planview Phases and PMAP Phases
General recommendations:
(1) When the project is in the “EXECUTION” phase of PMAP, the Phase names in the Planview tool should correlate to the SDLC that the project manager is using to
implement the project. The following Planview phase names are associated with the Waterfall SDLC. An example for the Agile or iterative SDLC is
depicted later in this document.
(2) If multiple iterations of the Planning phase are required, it is better to close the Planview Project and start a new project plan for each iteration.
Planview / SDLC Phases 
(none)
Cross Phase Project Administration & Management (activities that cross multiple phases of a project)
Definition
Planning
For projects with
phased roll-outs,
repeat these phases
for each production
release:
Design/Development
Testing
Close-Out
Execution
Planning
Definition
PMAP
g:\projects\project_office\PMandPV\PMAP and Planview phases activities and deliverables.doc
Revision: 10.0 (Final)
Implementation/
Rollout
Steady State
Close-Out
Page 1
May 28, 2010
Planview Phases and PMAP Phases: Waterfall SDLC for packaged software solution
PMAP Phase
Definition
Planning
Planview Phase
Typical Deliverables
Required Activities
Cross Phase Project
Administration &
Management


Definition
Planning





Updated Project Management (PM)
deliverables
Project Need Statement
Project Proposal including goals,
objectives, scope, project governance,
anticipated benefits, risks, high level
estimates for budget & schedule, etc.
PM Deliverables
o
Detailed Project Schedule
o Detailed Project Budget & Resource
Plan
o
Risk Management Plan
o
Communication Plan
o Commitment Change & Issue
Management Procedures
o
Training Plan
o
Test Strategy/Plan
o
End user Support Plan
o
Architecture Plan
o
Roll out Strategy/Plan
o
Project team established
Planning assumptions & constraints,
critical success factors, benchmarks,
and performance measures
Functional and technical requirements
o Current Systems Analysis (CSA)
o Functional/business
o Technical/architectural
o Conversion/Load/Interface
g:\projects\project_office\PMandPV\PMAP and Planview phases activities and deliverables.doc
Revision: 10.0 (Final)




















Maintain PM Deliverables & Commitments
o includes preparing status reports,
maintaining project plan, etc.
Orientation/training for new team members
Team meetings
Develop Project Needs Statement/Proposal
o includes preparing high level estimates
for budget and schedule
Prepare & Conduct Definition Phase Gate
Develop detailed Project schedule, budget,
and resource plan
Develop Risk Management Plan
Develop Communication Plan
Develop End user support plan
Develop Training plan
Develop Test Strategy/plan
Develop Architecture plan
Develop Roll out plan
Set-up Commitment Change & Issue Mgmt
Processes
Set-up Project directories, work
environment, etc.
Define functional & technical requirements
Conduct Current Systems Analysis (CSA)
Establish “as is” and “to be” process/data
models
Identify opportunities for process
optimization/re-design
Perform ""Make vs. Buy"" analysis (based on
requirements)"
Prepare RFP & Evaluate responses
Page 2
May 28, 2010
PMAP Phase
Planview Phase
Typical Deliverables




Execution
Design/Development






o Reporting
o Security and Privacy
o Testing
o Training
o EUS
Data & process models (“as is” and “to
be”)
o this should include identified
opportunities for process
optimization/re-design
Development approach/methodology
RFP & response evaluation matrix
Make vs Buy – Options &
Recommendation(s)
 Pros/Cons
 Estimated Costs
 Estimated Benefits
 Estimated Timeline
 Risks
Certification test results
Fit/Gap analysis
Documented strategies for:
o End user reporting
o Data security
o Conversion
Identified gap closing options &
implementation requirements for
defined strategies
Recommendation(s)
o Costs
o Benefits
For agreed upon customizations to
packaged software
o Database design (logical & physical)
g:\projects\project_office\PMandPV\PMAP and Planview phases activities and deliverables.doc
Revision: 10.0 (Final)
Required Activities

Prepare & Conduct Planning Phase Gate

Develop technical design/ specifications/
prototype
Conduct Fit/Gap Analysis
Define Security, Reporting and Conversion
Strategies
Prepare & Conduct Design Phase Gate







Install & Configure Software
Perform certification testing
Document new or modified business
processes to support identified opportunities
for optimization/re-engineering Develop &
Unit Test agreed upon enhancements to
packaged software
Develop & Unit Test interfaces to packaged
Page 3
May 28, 2010
PMAP Phase
Planview Phase
Typical Deliverables

Execution
Testing


o Object model & use cases
o Detailed specifications for all screens,
interfaces and integration points,
processes, conversion, reports, and
any required modifications to
existing systems
New custom software and/or agreed
upon enhancements to packaged
software
Test Plans
Test Results
Required Activities





Execution
Implementation/Rollout






Test Plans
Test Results
User Signoff
Training Materials
User manual / business process
documentation as needed
Operational production system
g:\projects\project_office\PMandPV\PMAP and Planview phases activities and deliverables.doc
Revision: 10.0 (Final)
software
Develop & Test
o data migration/conversion
o initial data loads
Finalize test plan
o plans should address specific testing
requirements for security and privacy
Setup environment
Execute test & document results
Error correction & retesting
Under each of the above activities, define tasks
to identify the type of testing that is occurring,
e.g.,

Desktop/Browser testing

System Test

Integration Test

Performance Test

Regression Test
 End User Training
 User Acceptance Test
o Finalize Test Plan
o Setup Environment
o Execute & Document results
o Error Correction & Re-testing
o Fine-tune and finalize business
processes
 Obtain user signoff
 Execute Communications, Training, and End
Page 4
May 28, 2010
PMAP Phase
Planview Phase
Typical Deliverables
Required Activities


Execution
Close-out
Steady State
Close-out






System Documentation
Trained support team
Operational system in steady state
Lessons Learned Report
Five Year product evolution, budget &
resource plan
SLA
g:\projects\project_office\PMandPV\PMAP and Planview phases activities and deliverables.doc
Revision: 10.0 (Final)









User Support Plans
Prepare & Conduct Implementation Phase
Gate
Execute
o data migration/conversion
o initial data loads
Conduct Production Turnover
Prepare Steady State Plan
Execute Steady State Plan, which includes,
for example
o Prepare System Documentation
o Conduct training sessions/knowledge
transfer to support team
o Production support
Complete agreed-upon deferred items
Conduct post-implementation review/audit
Prepare Lessons Learned Report
Prepare 5-Year product evolution plan
Establish/revise SLA
Prepare & Conduct Operational Phase Gate
Page 5
May 28, 2010
Planview Phases and PMAP Phases: Waterfall SDLC for custom software solution
PMAP Phase
Definition
Planning
Planview Phase
Typical Deliverables
Required Activities
Cross Phase Project
Administration &
Management


Definition
Planning





Updated Project Management (PM)
deliverables
Project Need Statement
Project Proposal including goals,
objectives, scope, project governance,
anticipated benefits, risks, high level
estimates for budget & schedule, etc.
PM Deliverables
o
Detailed Project Schedule
o Detailed Project Budget & Resource
Plan
o
Risk Management Plan
o
Communication Plan
o Commitment Change & Issue
Management Procedures
o
Training Plan
o
Test Strategy/Plan
o
End user Support Plan
o
Architecture Plan
o
Roll out Strategy/Plan
o
Project team established
Planning assumptions & constraints,
critical success factors, benchmarks,
and performance measures
Functional and technical requirements
o Current Systems Analysis (CSA)
o Functional/business
o Technical/architectural
o Conversion/Load/Interface
g:\projects\project_office\PMandPV\PMAP and Planview phases activities and deliverables.doc
Revision: 10.0 (Final)




















Maintain PM Deliverables & Commitments
o includes preparing status reports,
maintaining project plan, etc.
Orientation/training for new team members
Team meetings
Develop Project Needs Statement/Proposal
o includes preparing high level estimates
for budget and schedule
Prepare & Conduct Definition Phase Gate
Develop detailed Project schedule, budget,
and resource plan
Develop Risk Management Plan
Develop Communication Plan
Develop End user support plan
Develop Training plan
Develop Test Strategy/plan
Develop Architecture plan
Develop Roll out plan
Set-up Commitment Change & Issue Mgmt
Processes
Set-up Project directories, work
environment, etc.
Define functional & technical requirements
Conduct Current Systems Analysis (CSA)
Establish “as is” and “to be” process/data
models
Identify opportunities for process
optimization/re-design
Develop Proposed System Design/Prototype
Perform ""Make vs. Buy"" analysis (based on
requirements)"
Page 6
May 28, 2010
PMAP Phase
Planview Phase
Typical Deliverables





Execution
Design/Development




o Reporting
o Security and Privacy
o Testing
o Training
o EUS
Data & process models (“as is” and “to
be”)
o this should include identified
opportunities for process
optimization/re-design
High level proposed design, including
screen designs if feasible, descriptions
of features, functions, integration
points, required interfaces, and
proposed technical architecture.
High level plan with estimated schedule
and resource requirements for next
phase of the project (either “design” or
“design/development”.
Development approach/methodology
Make vs Buy – Options &
Recommendation(s)
 Pros/Cons
 Estimated Costs
 Estimated Benefits
 Estimated Timeline
 Risks
Documented strategies for:
o End user reporting
o Data security
o Conversion
Database design (logical & physical)
Object model & use cases
Detailed specifications for all screens,
g:\projects\project_office\PMandPV\PMAP and Planview phases activities and deliverables.doc
Revision: 10.0 (Final)
Required Activities

Prepare & Conduct Planning Phase Gate


Develop technical design/ specifications/
prototype
Define Security, Reporting and Conversion
Strategies
Prepare & Conduct Design Phase Gate

Develop & Unit Test software

Page 7
May 28, 2010
PMAP Phase
Planview Phase
Typical Deliverables

Execution
Testing


Required Activities
interfaces and integration points,
processes, conversion, reports, and any
required modifications to existing
systems
New custom software and/or agreed
upon enhancements to packaged
software

Test Plans
Test Results





Execution
Implementation/Rollout





Test Plans
Test Results
User Signoff
Training Materials
User manual / business process
documentation as needed Operational
production system
g:\projects\project_office\PMandPV\PMAP and Planview phases activities and deliverables.doc
Revision: 10.0 (Final)
Develop & Test
o data migration/conversion
o initial data loads
Document new or modified business
processes to support identified opportunities
for optimization/re-design
Finalize test plan
o plans should address specific testing
requirements for security and privacy
Setup environment
Execute test & document results
Error correction & retesting
Under each of the above activities, define tasks
to identify the type of testing that is occurring,
e.g.,

Desktop/Browser testing

System Test

Integration Test

Performance Test

Regression Test
 End User Training
 User Acceptance Test
o Finalize Test Plan
o Setup Environment
o Execute & Document results
o Error Correction & Re-testing
 Fine-tune and finalize business processes
Obtain user signoff
 Execute Communications, Training, and End
User Support Plans
 Prepare & Conduct Implementation Phase
Page 8
May 28, 2010
PMAP Phase
Planview Phase
Typical Deliverables
Required Activities

Execution
Close-out
Steady State
Close-out






System Documentation
Trained support team
Operational system in steady state
Lessons Learned Report
Five Year product evolution, budget &
resource plan
SLA
g:\projects\project_office\PMandPV\PMAP and Planview phases activities and deliverables.doc
Revision: 10.0 (Final)









Gate
Execute
o data migration/conversion
o initial data loads
Conduct Production Turnover
Prepare Steady State Plan
Execute Steady State Plan, which includes,
for example
o Prepare System Documentation
o Conduct training sessions/knowledge
transfer to support team
o Production support
Complete agreed-upon deferred items
Conduct post-implementation review/audit
Prepare Lessons Learned Report
Prepare 5-Year product evolution plan
Establish/revise SLA
Prepare & Conduct Operational Phase Gate
Page 9
May 28, 2010
Planview Phases and PMAP Phases: Example for Agile or iterative SDLC
For the Agile or iterative SDLC, the phase names would be the same as in Waterfall except that the “Design/Development” Phase in Waterfall would
change to “Timebox-n” and would be named according to the objectives or expected outcomes/deliverables of that particular Timebox. For
example, if a particular Timebox was intended to develop software for “Feature ABC”, then that Phase would be named “Timebox for feature ABC”. In
Penn’s implementation of the Agile SDLC, multiple Timebox phases can occur for each production release.
PLanview / SDLC Phases 
(none)
Cross Phase Project Administration & Management (activities that cross multiple phases of a project)
Close-Out
Execution
Planning
Definition
PMAP
Definition
Planning
Repeat the “Timebox”
phase 1-to-n times to
develop the software
intended for each
production release then
continue with testing &
implementation/rollout;
all three phases should
be repeated for each
production release
“Timebox-n”
Testing
g:\projects\project_office\PMandPV\PMAP and Planview phases activities and deliverables.doc
Revision: 10.0 (Final)
Implementation/
Rollout
Steady State
Close-Out
Page 10
May 28, 2010
Mapping for the Agile SLDC
PMAP Phase
Planview Phase
Typical Deliverables
Required Activities
Cross Phase Project
Administration &
Management
[same as for Waterfall]
[same as for Waterfall]
Definition
Definition
[same as for Waterfall]
[same as for Waterfall]
Planning
Planning
Execution
“Timebox-n”
[same as for Waterfall]
PLUS
Iteration Plan
[same as for Waterfall]
[same as for Waterfall]
PLUS
Develop Iteration Plan
Develop requirements
Develop design model
Develop & unit test code
Execution
Note: The name of the
Phase should be indicative
of its expected outcome or
deliverable. For example, if
the purpose of the timebox
is to develop a particular
function or feature (e.g.,
“Feature A”), then name
the phase “Feature A” or
something like that.
Testing
[same as for Waterfall]
[same as for Waterfall]
Execution
Implementation/Rollout
[same as for Waterfall]
[same as for Waterfall]
Execution
Steady State
[same as for Waterfall]
[same as for Waterfall]
Close-Out
Close-out
[same as for Waterfall]
[same as for Waterfall]



Note: After each timebox is completed, the
project manager needs to update/refine the
iteration plan. This activity is included in the
standard “Maintain PM Deliverables &
Commitments” activity within the “Cross Phase
Project Administration & Management” Phase
of the project plan.
g:\projects\project_office\PMandPV\PMAP and Planview phases activities and deliverables.doc
Revision: 10.0 (Final)
Page 11
May 28, 2010
Planview Phases and PMAP Phases
The following is an example of the iterations for software upgrade or re-hosting projects that can involve multiple non-production environments.
PLanview / SDLC Phases 
(none)
Cross Phase Project Administration & Management (activities that cross multiple phases of a project)
Close-Out
Execution
Planning
Definition
PMAP
Definition
Planning
Repeat for each nonproduction
environment. Include
the
implementation/rollout
phase for the LAST
repeat
Design/Development
Testing
Implementation/
Rollout
Steady State
Include all three phases for the last iteration prior to the production release
g:\projects\project_office\PMandPV\PMAP and Planview phases activities and deliverables.doc
Revision: 10.0 (Final)
Close-Out
Page 12
May 28, 2010
Mapping for software upgrades/re-hosting projects
PMAP Phase
Definition
Planning
Planview Phase
Typical Deliverables
Required Activities
Cross Phase Project
Administration &
Management


Definition
Planning





Updated Project Management (PM)
deliverables
Project Need Statement
Project Proposal including goals,
objectives, scope, project governance,
anticipated benefits, risks, high level
estimates for budget & schedule, etc.
PM Deliverables
o
Detailed Project Schedule
o Detailed Project Budget & Resource
Plan
o
Risk Management Plan
o
Communication Plan
o Commitment Change & Issue
Management Procedures
o
Training Plan
o
Test Strategy/Plan
o
End user Support Plan
o
Architecture Plan
o
Roll out Strategy/Plan
o
Project team established
Planning Assumptions & Constraints,
critical success factors, benchmarks,
and performance measures
High level impact analysis results,
including: [these analyses are refined
during subsequent phases]
o Required changes to existing
customizations
g:\projects\project_office\PMandPV\PMAP and Planview phases activities and deliverables.doc
Revision: 10.0 (Final)


















Maintain PM Deliverables & Commitments
o includes preparing status reports,
maintaining project plan, etc.
Orientation/training for new team members
Team meetings
Develop Project Needs Statement/Proposal
o includes preparing high level estimates
for budget and schedule
Prepare & Conduct Definition Phase Gate
Develop detailed Project Schedule, Budget,
and Resource Plan
Develop Risk Management Plan
Develop Communication Plan
Confirm/modify existing end user support
plan
Develop Training plan
Develop Test Strategy/plan
Develop Architecture plan
Develop Roll out plan
Set-up Commitment Change & Issue Mgmt
Processes
Set-up Project directories, work
environment, etc.
Perform high level upgrade impact analysis
Identify opportunities for business process
optimization/re-design
Develop preliminary pre- and post-upgrade
steps
Prepare & Conduct Planning Phase Gate
Page 13
May 28, 2010
PMAP Phase
Planview Phase
Typical Deliverables
Required Activities
o

Execution
Design/Development





Identified opportunities for
business process optimization/redesign
o Required changes to existing
interfaces/integration with other
systems
o Required changes to Security
o Required new customizations or
reports
o Recommendation(s)
o Costs
o Benefits
Preliminary list of pre- and postupgrade steps
Certification test results
Updated process and data models
o including identified opportunities
for business process
optimization/re-design
Refined impact analysis results
For custom development and/or for
agreed upon customizations to
packaged software:
o Database design (logical & physical)
o Object model & use cases
o Detailed specifications (& user
signoff) for all screens, interfaces
and integration points, processes,
conversion, reports, and any
required modifications to existing
systems
New custom software and/or agreed
upon enhancements to packaged
g:\projects\project_office\PMandPV\PMAP and Planview phases activities and deliverables.doc
Revision: 10.0 (Final)






Establish environment
Install & configure upgraded software
Perform validation/certification testing
Confirm/modify data and process models
Design, develop & unit test agreed upon
enhancements/changes to upgraded
software [this activity would occur in the first
iteration only]
Develop/refine implementation plan
Page 14
May 28, 2010
PMAP Phase
Execution
Planview Phase
Testing
Typical Deliverables




software
Test Plans
Test Results
Refined impact analysis results
Updated process and data models
Required Activities




Finalize test plan
o plans should address specific testing
requirements for security and privacy
Setup environment
Execute test & document results
Error correction & retesting
Under each of the above activities, define tasks
to identify the type of testing that is occurring,
e.g.,

Desktop/Browser testing

System Test

Integration Test
 Performance Test (this typically occurs only
in the LAST iteration prior to production
release)


Regression Test
User validation test (this applies for each
interim iteration except the final one prior to
production release; user testing for that one
is included in the implementation/rollout
phase)
Execution
Implementation/Rollout



Test Plans
Test Results
User Signoff
g:\projects\project_office\PMandPV\PMAP and Planview phases activities and deliverables.doc
Revision: 10.0 (Final)

Prepare & Conduct Interim Upgrade Phase
Gate -- this activity applies for each interim
iteration except the final one prior to
production release; the phase gate for that
one is included in the implementation/rollout
phase


End User Training
User Acceptance Test
o Finalize Test Plan
o Setup Environment
Page 15
May 28, 2010
PMAP Phase
Planview Phase
Typical Deliverables




Required Activities
Training Materials
Updated user manual / business process
documentation
Detailed implementation plan, including

contingencies

Operational production system



Execution
Steady State



System Documentation
Trained support team
Operational system in steady state
Close-out
Close-out


Lessons Learned Report
Five Year product evolution, budget &
resource plan
SLA

g:\projects\project_office\PMandPV\PMAP and Planview phases activities and deliverables.doc
Revision: 10.0 (Final)









o
o
o
Execute & Document results
Error Correction & Re-testing
Fine-tune and finalize business
processes
Obtain user signoff
Execute Communications, Training, and End
User Support Plans
Prepare detailed implementation plan,
including contingencies
Prepare & Conduct Implementation Phase
Gate
Perform upgrade/rehost in production
environment
Conduct Production Turnover
Prepare Steady State Plan
Execute Steady State Plan, which includes,
for example
o Prepare System Documentation
o Conduct training sessions/knowledge
transfer to support team
o Back-port upgrades to all non-production
environments
o Production support
Complete agreed-upon deferred items
Conduct post-implementation review/audit
Prepare Lessons Learned Report
Prepare 5-Year product evolution plan
Establish/revise SLA
Prepare & Conduct Operational Phase Gate
Page 16
May 28, 2010