Appendix E: Project Management Life-Cycle Framework

---

PROJECT PHASE	PHASE DESCRIPTION	PHASE TASKS	DEVELOPMENT PHASE DELIVERABLES	PROCIT PERSONNEL RESPONSIBILITIES
Commitment	Project planning, initiation, & commitment	Receive authorized request from executive sponsor and working clients Analyze project/service request Define project scope Determine approach Define project team assignments Model resource requirements Hold commitment review, obtain signoffs Obtain resource commitments Create the project control process Create project scorecard Hold kickoff meeting	Commitment document with signoffs by executive sponsor, working clients, and all IT organization partner providers for the project Project plan Project budget Master project schedule entry Scorecard (monthly updates) Scope change control forms Deliverable acceptance forms	Project director and manager meet iteratively with project sponsor and working client(s) to define scope and resources Project director, project manager, and working clients develop commitment document and draft project plan Project director or project manager obtain input on commitment document and plan from IT organization partner providers
Analysis, Part 1 Business requirements analysis		Confirm project scope Establish customer needs Assess current business processes Define quality assurance (QA) evaluation process and scope Identify gaps and opportunities for IT-enabled process changes Develop launch strategy and preliminary implementation plan Model process and data requirements Develop project measures and metrics Review and sign off on business requirements Change management process in place	Business requirements document with business benefits/ROI analysis if appropriate Functional requirements document for IT-enabled business solution Process model/use cases Page schematics for Web solutions Review scope changes Updated commitment document Deliverable acceptance form signed by the customer at each project phase	Project team, led by project director, with management and analysis services provided by PMO (if applicable); technical analysis provided by partner providers and external resources as needed Project team, including working clients, to develop customer service strategy and plan, including help desk training and customer feedback plan Project team ensures deliverables acceptance by the customer and formally ends the phase Project team ensures that QA reviews phase outcomes for the subsequent development of test plans and scripts
Analysis, Part 2	Technical and infrastructure requirements analysis	Analyze solution alternatives Recommend technical solution Architect and model initial IT solution Define QA evaluation process and scope Validate against organization's existing IT architectural standards and best practices Gather technical requirements and discuss implications with appropriate IT infrastructure management personnel (i.e., network, server, storage, production services impacts) Review and sign off on technical specification Review and approve recommended solution with working clients and IT partner providers	Complete technical requirements questionnaire form with stakeholder input (both working clients and partner providers as required) Technical specification document Updated commitment document Deliverable acceptance form signed by the customer at each project phase	Project team to engage internal and external partner providers in process QA, partner providers, external parties, et al., to provide technical input In particular, the project team must involve IT infrastructure personnel (e.g., system services and network services) at this stage of the project and thereafter as changes occur in the technical architecture and deployment plans for the project Project team ensures deliverables acceptance by the customer and formally ends the phase Project team ensures that QA reviews phase outcomes for the subsequent development of test plans and scripts
Design, Part 1	Solution definition and design	Establish business process and technical frameworks Specify systems/subsystems involved in the delivery of the IT solution Specify data requirements Design databases Specify/design data conversion process Complete documentation of business process changes and system specifications Specify operational requirements, including training for IT and customer support units and end users Define QA testing and evaluation Define test strategy Define development infrastructure Training and support needs defined	Detailed functional specifications Preliminary visual designs and screenshots Development infrastructure specifications QA/test scripts and infrastructure specifications Workflow design and organization plan Adjustments to technical specification document Deliverable acceptance form signed by the customer at each project phase Capture any scope changes in commitment document Draft service level agreement (SLA) matrix and associated IT operational service delivery agreement (OSDA) metrics	Project manager to ensure review and signoff on detailed functional specification Project manager or business analyst to carry out usability planning with working clients, other customers, and the project team Release strategy developed by QA working with project manager Review and approve final specifications and agree on change management process by project team and working clients PMO personnel to modify technical specifications as required Project director ensures deliverables acceptance by the customer and formally ends the phase
Design, Part 2	Prototype [1]	Create visual prototype based on business and technical requirements; employ "sandbox" IT environments as appropriate Conduct focus groups Adjust solution design as necessary, based on feedback Place orders for IT hardware and software as appropriate	Nonworking prototype an aid to understanding requirements Launch plan Focus groups findings document Purchase orders Deliverable acceptance form signed by the customer at each project phase Capture any scope changes in commitment document and project plan	Working clients review and provide feedback Working clients review and sign off on prototype and also visual designs/prototypes Working clients review and approve updated project plan and commitment document Launch planning with customers and project team, including IT infrastructure personnel Project director ensures deliverables acceptance by the customer and formally ends the phase
Infrastructure	Infrastructure requirements for development, testing, and production	Review project technical specifications with IT infrastructure and QA personnel Given the technical specifications, identify development environment Secure development lab resources As development proceeds, anticipate implications of changes in technical requirements that impact IT test and production environments Communicate implications to QA regarding test lab Communicate implications to IT infrastructure personnel regarding production Take steps during development to ensure that both test and production platforms are properly resourced to receive the project's system at the times stated in the project plan Architectural review Business continuity and disaster recovery review	Development lab specifications Test lab specifications (or at least the beginnings of gap analysis between current capabilities and projected needs once the project proceeds to QA) Production environment specifications (or at least the beginnings of gap analysis between current capabilities and projected needs once the project proceeds to production) Purchase orders as appropriate Synchronization of test lab and production change scheduling in line with the project plan Delivery plan adjustments as appropriate Deliverable acceptance form signed by the customer at each project phase Capture any scope changes in commitment document and on project plan Defined backup, restore, and disaster recovery standards/thresholds	Review and signoff by the development lab coordinator Review and signoff by IT infrastructure personnel Review and signoff by QA Review and signoff by the IT team that will host the application once it is in production IT executive approval of all software acquisitions IT executive approval of all hardware acquisitions Architectural review and signoff by IT management IT business officer approval of purchase orders
Development	Development	System(s) installation and modification Technical development of database, middleware, and front-end components Data feeds/cleanup Develop reporting services and reports Unit testing Develop test planning and test script Support staff training and document development Prepare customer service and marketing plans Reengineer business processes Screenshots documented Support staff and end-user training developed Communication and marketing strategies developed	Application that conforms to functional specifications User documentation Technical documentation Reporting package (for canned reports) and reporting/query tools for end-user ad hoc reporting Business workflow procedures document User training package Deliverable acceptance form signed by the customer at each project phase Capture any scope changes in commitment document Technical design document Training program descriptions	Project team develops solution in partnership with internal and external partner providers Data lead ensures all data feeds in place and that the data is clean/normalized for use by application PMO personnel and working clients provide business process and application documentation PMO personnel provide business cases for test plan AA. Project team to review and approve reporting package with working clients AB. PMO personnel to coordinate technical support and user training and customer service and marketing plans; ensure partner provider agreement AC. Project director to provide metrics for stress and acceptance testing
Certification	QA testing and release management	Perform functional QA tests Perform technical tests Perform usability testing Perform system integration testing Perform stress testing Perform acceptance testing Fix bugs! Initiate communications and marketing strategies Collect information about future enhancements as part of the development of a release strategy for the new or revised IT product or service	Testing approaches/scripts Implemented system in test environment QA certification Final implementation plan Support team training validation Customer training validation Refined application per functional QA, technical, usability, system integration, environmental, and acceptance testing activities Deliverable acceptance form signed by the customer at each project phase Capture any scope changes in commitment document	QA to review and approve test acceptance criteria QA to review and approve test approach and plan QA to perform functional, technical, usability, system, and stress testing, typically within QA lab Perform customer acceptance testing, typically within customer environments QA certifies ready for production Project manager to communicate customer feedback to project team and working clients Project director to communicate with users regarding pilot/full launch Executive sponsor and working clients sign off on system AA. Risk review held with IT management for formal "Go/No Go" signoff
Launch	Pilot [2]	Extend the implementation of communications and marketing strategies Implement pilot system or system (as appropriate) Regression testing completed and all bug fixes either addressed or plans in place for resolution Transition to servicing team For Web sites, load Web assets and site content (ongoing process) Training underway; user support in place	Implemented production-ready system Launch-ready organizational packages SLAs, including future enhancements, ongoing maintenance, release planning, and support costs Augmented future enhancements document User training and documentation in place	Project team monitors pilot progress Revise launch plans with working clients and project team Project team reviews pilot feedback; determines need to incorporate feedback prior to launch Project team risk review held with management for formal "Go/No Go" signoff IT customer services to publish training schedules and documentation PMO personnel to adjust IT OSDAs and customer SLAs.
Release	Go live	Go live signoff by QA Implement production system For Web sites, load Web assets and site content (ongoing process) As part of hand-off to ongoing IT service provider, assist in development of release strategy that defines future enhancements as part of a 1–2 year view of the product/service offering Meet with your team to bring closure	Documentation completed Communication/press release Code archived All technical, systems, and user documentation archived All project artifacts in IT knowledge repository Project signoff by customer Release strategy	Project team to assist with user training and launch activities Customer signoff on deliverables Appropriate IT manager to meet with project team and discuss lessons learned Project director to monitor ongoing feedback mechanisms — e-mail, calls to service center, metrics, and measures — and, as appropriate, initiate steps to enhance program and services Project manager to deposit all major project documents in an IT project knowledge management repository
Sunset	Retire existing and replaced platforms	Recovery planning for legacy systems Data preservation for historical reporting/audit purposes Uninstall software as it comes offline Uninstall hardware as it comes offline	Postimplementation celebration Update IT organization asset inventories Adjust OSDAs and SLAs accordingly Lessons-learned document in IT knowledge repository	Project director ensures that all changes are well communicated in advance to customers and IT personnel
[1]May not apply in all cases. [2]This step does not apply in all project instances.

---