Docstoc

Controlling Idea Outline Template

Document Sample
Controlling Idea Outline Template Powered By Docstoc
					                                                                Software Development Project Checklist

NOTE : All steps are required for Class A projects

Opportunity Assessment Phase
                                                                      Class B
                                                                      Required
                               Activity                                Steps   Completed                        Deliverable
Idea Generation
Receive or solicit ideas from the customers/clients                    Yes
Define the Opportunity Assessment Team                                 Yes
Refine the idea through discussions with the customer, research
and benchmarking of similar areas                                      Yes
Idea Structuring
Identify and confirm sponsorship                                       Yes                 Identify Sponsor
Document high level business need and significant milestones.
                                                                       Yes                 Project Initiation Document
Identify customers, users, and stakeholders                            Yes                 Project Initiation Document
Define high-level business benefits                                    Yes                 Project Initiation Document
Identify high-level requirements and critical success factors          Yes                 Project Initiation Document
Identify related projects/affected systems. List below:                Yes                 Project Initiation Document
Outline scope, schedule and resources for the next phase               Yes                 Project Initiation Document, Project Schedule
Opportunity Assessment Approval
Prepare and submit the Project Initiation Document                     Yes                 Project Initiation Document
Prioritize idea based on business criteria and resource constraints
                                                                       Yes
Conduct the Opportunity Assessment Review and obtain approval
                                                                       Yes
Enter information into the project tracking system and time
reporting system
Phase Closure
Assess the Opportunity Assessment Process to capture lessons
learned                                                                Yes                 Lessons Learned

Exit Criteria




Signature:




5b16978f-5688-4a1b-8758-296d44e582bd.xls                                                                                               1 of 42
cklist
         Project Name
         Program Mgr.
         Project Mgr.




                 Leader                 Participants




         Date:




         5b16978f-5688-4a1b-8758-296d44e582bd.xls      2 of 42
                                                                  Software Development Project Checklist

NOTE : All steps are required for Class A projects

Concept Phase
                                                                    Class B
                                                                    Required
                               Activity                              Steps   Completed
Phase Start Up
Define /refine Concept (Initiating) Team and identify project
manager                                                              Yes
Conduct project planning meeting.
Review lessons learned                                               Yes
Develop Concept Phase schedule                                       Yes
Implement time tracking status reporting                             Yes
High-Level Requirements Identification
Understand and further define business need                          Yes
Define/refine business requirements, vision, scope, critical
requirements, and risks for the project                              Yes
Define assumptions and dependencies                                  Yes
Options Analysis

Develop and analyze potential concepts to meet business need         Yes
Conduct initial enterprise architecture, data architecture, and
technical planning review                                            Yes
Notify and include future support services and operations
organizations                                                        Yes
Develop a recommended approach                                       Yes
Executive presentation of recommended approach




      5b16978f-5688-4a1b-8758-296d44e582bd.xls                                               3 of 42
Project Definition
Develop ROM estimate for resources/costs and high-level
schedule/timeline for the project                                  Yes

Finalize Concept Analysis Document and architecture diagram        Yes
Continue to develop the Business Case                              Yes

Refine Project Initiation Document and complete Project Charter    Yes
Plan for next phase by developing schedule, budget, and identify
resources                                                          Yes
Concept Approval
Prepare for and participate in Concept Checkpoint Review           Yes
Phase Closure
Document lessons learned from Concept Phase                        Yes

Exit Criteria




Signature:




      5b16978f-5688-4a1b-8758-296d44e582bd.xls                           4 of 42
Development Project Checklist
                                                  Project Name
                                                  Program Mgr.
                                                  Project Mgr.




                        Deliverable                      Leader   Participants



   SD Phase Checklist, Organizational Chart
   Project Phase Kickoff Presentation

   Project Schedule


   Project Initiation Document, Project Charter

   Project Initiation Document, Project Charter
   Project Charter


   Concept Analysis Document




   Concept Analysis Document
   Concept Analysis Executive Summary




         5b16978f-5688-4a1b-8758-296d44e582bd.xls                                5 of 42
(Schedule and Costs Summary section) of
Business Case

Concept Analysis Document
Business Case

Project Initiation Document, Project Charter
Project Initiation Document, Project Charter,
Project Schedule, Project Timeline



Lessons Learned




                                                Date:




      5b16978f-5688-4a1b-8758-296d44e582bd.xls          6 of 42
                                                                 Software Development Project Checklist

NOTE : All steps are required for Class A projects

Requirements Phase
                                                                      Class B
                                                                      Required
                                  Activity                             Steps   Completed
Phase Start Up
Define/refine the Requirements (Planning) team and review roles
and responsibilities                                                   Yes
Conduct project planning meeting.

Initiate controlling processes.                                        Yes
Project Approach

Review project approach and validate that the modified waterfall
project lifecycle, identify the project team to complete the phases
of the project, and define project measures of success                 Yes
Initiate engagement with dependent areas. This includes
operations, training, support services, data, and documentation
management.                                                            Yes
Initiate development of a work breakdown structure. Review
example in SD Handbook.                                                Yes
Identify Configuration Management Plan, requirements
management process, work products, change control, version
control, requirements with status tracking.                            Yes


Select change control, version control, and traceability tools         Yes

Review and revise business objectives, scope and vision from
Concept phase, document the "As-Is" and "To-Be" business
processes and any process improvement opportunities                    Yes




   5b16978f-5688-4a1b-8758-296d44e582bd.xls                                                   7 of 42
User Requirements Definition
Identify the project requirements, decision process, and decision
makers                                                               Yes

Define approach for requirements definition, documenting,
communicating requirements and identify log tool                    Yes
Develop and prioritize use cases for portions of the software
application to be developed                                         Yes
Further define complex use cases (if required) with additional
techniques such as data flow diagrams, entity relationship
diagrams, state-transition diagrams, and object class and
interaction diagrams
Technical Requirements Definition
Define data requirements. Create data models to document, as
needed.                                                              Yes
Identify, define, and document technology, infrastructure, and
support requirements. Conduct/refine enterprise and data
architectural reviews.                                               Yes
Define the user documentation deliverable types and the training
deliverables needed for the application/system.
Elaborate the use cases into the necessary functional
requirements                                                         Yes
Develop user interface prototypes.
Develop and evaluate application/system input and output
requirements, screens, menus, reports, and forms




   5b16978f-5688-4a1b-8758-296d44e582bd.xls                                8 of 42
Requirements Documentation and Review
Prioritize features and/or functional requirements                   Yes

Develop Software Requirements Specification                          Yes
Plan and conduct Requirements Walkthrough with the
Development Team. Gather feedback and approval for the
Software Requirements Specification                                 Yes
Plan and conduct User Requirements Walkthrough. Gather
feedback and approval for the Software Requirements
Specification                                                       Yes
Test Planning

Begin development of Test Plan. Evaluate test risks to determine
an appropriate test strategy. Include a high level test schedule.    Yes
Develop conceptual test cases                                        Yes

Develop initial draft of User Acceptance Criteria                    Yes
Use the test cases to verify use cases, technical requirements,
and prototypes                                                       Yes




   5b16978f-5688-4a1b-8758-296d44e582bd.xls                                9 of 42
Requirements Refinement
Repeat requirements definition steps, as required. Refine SRS, if
required.                                                            Yes
Define/revise the System diagram                                     Yes
Project Planning
Refine/validate project approach and project lifecycle.             Yes
Begin development of the Project Notebook and management
approaches                                                          Yes
Identify Project Team Members and document the project
organization.                                                       Yes
Establish Communication strategy.                                   Yes
Create Steering Committee presentation

Starting with the WBS, develop a project schedule and budget.
Estimate work effort and duration for the project activities.         Yes
Refine the Business Case.                                           Yes
Review the project schedule, budget and SRS with the project
team, sponsors, and other appropriate stakeholders.                 Yes
Prepare Project Funding deliverables and review with the funding
approval authority                                                   Yes
Review the Project Funding deliverables with senior staff.
Plan for next phase                                                  Yes
Planning/Funding Approval
Prepare for, schedule, and participate in Project Funding
Checkpoint Review. Obtain Project Funding number                     Yes
Phase Closure
Baseline requirements, schedule, and budget and place all
configurable documents (e.g., SRS, Project Plan, etc.) in the
project repository                                                   Yes
Document lessons learned.                                            Yes

Exit Criteria



Signature:




   5b16978f-5688-4a1b-8758-296d44e582bd.xls                                 10 of 42
re Development Project Checklist
                                                            Project Name
                                                            Program Mgr.
                                                            Project Mgr.




                           Deliverable                             Leader   Participants



      SD Phase Checklist
      Project Phase Kickoff Presentation
      PM Executing / Controlling templates, Project Plan,
      Project Notebook




      Work Breakdown Structure (WBS)
      Request for Change, Change Management Log,
      Software Requirements Specification,
      Requirements Traceability Matrix
      Request for Change, Change Management Log,
      and Software Requirements Specification,
      Requirements Traceability Matrix


      Business Requirements Catalog, Concept Analysis
      Document




        5b16978f-5688-4a1b-8758-296d44e582bd.xls                                           11 of 42
Business Requirements Catalog
Business Requirements Catalog, Software
Requirements Specification, Requirements
Traceability Matrix

Use Case



Use Case

Software Requirements Specification,
Requirements Traceability Matrix


Technical Evaluation, Support Expectations
Documentation Plan (no template), Training Plan,
Project Schedule
Software Requirements Specification,
Requirements Traceability Matrix




  5b16978f-5688-4a1b-8758-296d44e582bd.xls         12 of 42
Software Requirements Specification,
Requirements Traceability Matrix




Test Plan (Master) or Test Plan (Minor), Project
Schedule (Test Phase)

Software Requirements Specification,
Requirements Traceability Matrix, Test Plan




   5b16978f-5688-4a1b-8758-296d44e582bd.xls        13 of 42
Software Requirements Specification,
Requirements Traceability Matrix
Systems Diagram




Organization Chart
Communications Matrix
Steering Committee Presentation


Project Schedule, Timeline, Project Budget
Business Case




Software Requirements Specification,
Requirements Traceability Matrix, Project
Schedule, Project Budget
Lessons Learned




                                             Date:




  5b16978f-5688-4a1b-8758-296d44e582bd.xls           14 of 42
                                                           Software Development Project Checklis

NOTE : All steps are required for Class A projects

Design Phase
                                                                Class B
                                                                Required
                              Activity                           Steps   Completed
Phase Start Up

Initiate Design Acivities                                        Yes
Conduct project planning meeting.

Implement Control processes and activities.                      Yes
Create mechanisms for tracking, managing, and changing design
specs. (Configuration Management)                                Yes
Define/Refine project team roles and responsibilities            Yes
High-Level Design
Establish a design strategy
Create a high level design based on requirements and identify
impact risks                                                     Yes
Decompose the system into subsystems and outline the
communications                                                    Yes
Create Prototype with inputs and outputs                          Yes
Create logical data models and design data model                Yes
Identify DBMS platform, hardware, operating system              Yes
Conduct high level architecture design review                   Yes
Baseline High Level Design Document                             Yes




    5b16978f-5688-4a1b-8758-296d44e582bd.xls                                         15 of 42
Detailed Design
Create physical databases                                        Yes
Create Detailed Design, design system inputs and outputs, user
interfaces, and dialogues                                        Yes

Update traceability matrix                                       Yes
Test and Documentation Planning
Continue development of test plan                                 Yes
Continue development of documentation approach                    Yes
Design Approval
Obtain design approval                                            Yes
Phase Closure
Begin development of the Deployment Strategy and Plan,
focusing on the Strategy section.                                 Yes
Begin development of the System/Application Support Document
to be used for long-term support issues.                          Yes
Revise Project Schedule and Project Budget as required, and
plan for the next phase.                                          Yes
Document Lessons Learned                                          Yes

Exit Criteria


Signature:




    5b16978f-5688-4a1b-8758-296d44e582bd.xls                            16 of 42
e Development Project Checklist
                                                       Project Name
                                                       Program Mgr.
                                                       Project Mgr.




                         Deliverable                          Leader   Participants


     SD Phase Checklist, Software Requirements
     Specification, Requirements Traceability Matrix
     Project Phase Kickoff Presentation
     PM Executing / Controlling templates, Project
     Notebook
     Configuration Management Plan, Change Control
     Management Plan
     Organization Chart



     High Level Design, Risk and Response Log

     High Level Design
     High Level Design



     High Level Design




         5b16978f-5688-4a1b-8758-296d44e582bd.xls                                     17 of 42
Detailed Design (no template)
Software Requirements Specification,
Requirements Traceability Matrix

Test Plan (Master) or Test Plan (Minor)




Deployment Strategy and Plan

Support Expectations

Project Schedule, Project Budget
Lessons Learned




                                               Date:




    5b16978f-5688-4a1b-8758-296d44e582bd.xls           18 of 42
                                                                  Software Development Project Checklist

NOTE : All steps are required for Class A projects

Development Phase
                                                                    Class B
                                                                    Required
                               Activity                              Steps   Completed
Phase Start Up
Initiate Development Activities                                      Yes
Conduct project planning meeting.
Define/Refine project team roles and responsibilities                Yes
Implement Control processes and use the management
approach.                                                            Yes
Development Strategy and Planning
Review/revise software integration process                           Yes
Define development strategy to build application                     Yes
Evaluate resources for the Development Phase.                        Yes
Create Unit Test Plan and expected results.                          Yes
Define/Refine test team.                                             Yes
Determine specific test types and update the Test Plan as
required.                                                            Yes
Decompose schedule into logical „work packages‟                      Yes
Review/revise time tracking, status reporting, issues tracking,
communication procedures                                             Yes
Review/revise defects tracking process                               Yes
Code Development
Develop code for each module/component.                              Yes
Perform code analysis                                                Yes




      5b16978f-5688-4a1b-8758-296d44e582bd.xls                                              19 of 42
Code Verification
Unit Test each module and document defects in a defect-tracking
process.                                                            Yes
Review code to ensure meets specifications                          Yes
Conduct Code Peer Reviews                                           Yes
Test Planning
Implement “build” procedures, execute smoke tests and fix any
errors that prohibit the build from being tested.                   Yes

Conduct a walkthrough of the application/system to the test team
and support team and provide tester training and support training   Yes
Develop test scripts based on requirements, design
specifications, and code development.                               Yes
Create the test environment and setup automated test
procedures, as appropriate. Adapt test reporting procedures
based on size, complexity, and specific project needs. Develop
test data management strategy.                                      Yes
Review the System/Application Support Checklist and update
support documents, as appropriate.                                  Yes
Working with the development team, business partners, and
client, develop test data to be used in testing the application.    Yes




      5b16978f-5688-4a1b-8758-296d44e582bd.xls                            20 of 42
Documentation Planning
Conduct a walkthrough of the application/system with the
documentation team.                                                 Yes

Create a User Documentation prototype and obtain user approval.
Development Approval
Prepare for and conduct final development approval.                 Yes
Phase Closure
Maintain communications and change control processes, project
scheduling and status reporting, and continue to manage any
project issues.                                                     Yes
Identify any additional risks, develop appropriate responses, and
update risk log, as appropriate.                                    Yes
Plan for the next phase                                             Yes
Document Lessons Learned                                            Yes

Exit Criteria


Signature:




      5b16978f-5688-4a1b-8758-296d44e582bd.xls                            21 of 42
Development Project Checklist
                                                   Project Name
                                                   Program Mgr.
                                                   Project Mgr.




                        Deliverable                       Leader   Participants


   SD Phase Checklist
   Project Phase Kickoff Presentation
   Organization Chart
   PM Executing / Controlling templates, Project
   Notebook



   Organization Chart, Project Schedule
   Unit Test Plan (no template)
   Organization Chart

   Test Plan (Master) or Test Plan (Minor)

   Team Member Status Report, Issues Log,
   Communications Matrix
   Defects Tracking Log

   Software Code (no template)




         5b16978f-5688-4a1b-8758-296d44e582bd.xls                                 22 of 42
Test Plan (Master) or Test Plan (Minor)

Support Expectations




      5b16978f-5688-4a1b-8758-296d44e582bd.xls   23 of 42
Risk and Response Log

Lessons Learned




                                            Date:




     5b16978f-5688-4a1b-8758-296d44e582bd.xls       24 of 42
                                                                    Software Development Project Checklist

NOTE : All steps are required for Class A projects

Testing Phase
                                                                      Class B
                                                                      Required
                               Activity                                Steps   Completed
Phase Start Up

Initiate Testing Activities                                            Yes
Conduct project planning meeting.
Define/Refine project team roles and responsibilities                  Yes
Implement Control processes and use the management
approach.                                                              Yes
Test Planning
Review/refine or create the Test Plan.                                 Yes
Review the results of the system verifications.                        Yes
Determine test tracking tools, defects tracking list, and prepare
Defect tracking log.                                                   Yes

Define the type and frequency of interim test reports                  Yes

Refine test cases and test scripts, as required.                       Yes




      5b16978f-5688-4a1b-8758-296d44e582bd.xls                                                25 of 42
System Validation
Refine the data and load data into the test environment.           Yes
Execute test scripts and create a test report.                     Yes
Report results of test scripts and update test issues and defect
tracking list. Develop interim reports for the project.            Yes
Store the data collected during testing in accordance with
configuration management procedures.                               Yes
Validate the system with functional and structural testing.        Yes
Test the support functions for the system defined in the
System/Application Support Document. Revise the
System/Application Support Document                                 Yes
Evaluate test reports to determine accomplishments and report
status. Update the test log.                                        Yes

Refine Acceptance Criteria, and perform User Acceptance
Testing. Obtain User sign off.                                      Yes




      5b16978f-5688-4a1b-8758-296d44e582bd.xls                            26 of 42
Deployment Preparation
Plan for the deployment of the new application/system. Define
process and transitional period for transitioning support.              Yes
Identify Deployment team.                                               Yes

Provide training for support staff on the new system/application.       Yes
Ensure the business users who will be verifying the final deployed
solution are familiar with the documentation and trained in the use
of the new release.                                                     Yes
Select appropriate site(s)/users for initial deployment, as required.
Prepare a Deployment Strategy and Plan (DS&P).                          Yes
Schedule a date and time for the introduction/migration of the new
release.
Testing Approval
Develop Final Test document summarizing all tests, results,
defects found, etc.                                                     Yes
Plan and conduct test Review. Gather feedback and approval for
the testing.                                                            Yes
Phase Closure
Revise Project Schedule as required, and plan for the Deployment
Phase.                                                                  Yes
Document Lessons Learned                                                Yes

Exit Criteria


Signature:




      5b16978f-5688-4a1b-8758-296d44e582bd.xls                                27 of 42
Development Project Checklist
                                                     Project Name
                                                     Program Mgr.
                                                     Project Mgr.




                        Deliverable                         Leader   Participants


   SD Phase Checklist, Software Requirements
   Specification, Requirements Traceability Matrix
   Project Phase Kickoff Presentation
   Organization Chart
   PM Executing / Controlling templates, Project
   Notebook, Project Schedule (Test Phase)

   Test Plan (Master) or Test Plan (Minor)


   Defect Tracking Log
   Test Report Format (no template - referenced in
   the Test Plan Master)
   Test Cases (no template), Test Scripts (no
   template)




         5b16978f-5688-4a1b-8758-296d44e582bd.xls                                   28 of 42
Support Expectations
Test log (no template - referenced in the Test Plan
Master)
Software Requirements Specification,
Requirements Traceability Matrix, Acceptance
Testing




      5b16978f-5688-4a1b-8758-296d44e582bd.xls        29 of 42
Deployment Strategy and Plan
Organization Chart




Deployment Strategy and Plan




Project Schedule
Lessons Learned




                                             Date:




      5b16978f-5688-4a1b-8758-296d44e582bd.xls       30 of 42
                                                                   Software Development Project Checklist

NOTE : All steps are required for Class A projects

Documentation and Training Phase
                                                                        Class B
                                                                        Required
                                Activity                                 Steps   Completed
Phase Start Up
Initiate Documentation and Training Activities                           Yes
Conduct project planning meeting.
Define/Refine project team roles and responsibilities                    Yes
Implement Control processes and use the management
approach.                                                                Yes
Documentation Planning and Training Preparation
Determine User documentation requirements                                Yes
Schedule training facilities and instructors for conducting training,
if appropriate.                                                          Yes
Prepare User documentation deliverables and report on
achievements.                                                            Yes
Deployment Training and Documentation
Establish a transition process and transitional support period for
the system/application and review.                                       Yes
Create documentation for the support procedures and review.              Yes
Develop technical training documentation and provide detailed
technical training to the support services representative.               Yes
Provide technical training to the support staff.                         Yes

Prepare user training material.                                          Yes
Coordinate user training dates and scheduling of attendees.              Yes




       5b16978f-5688-4a1b-8758-296d44e582bd.xls                                              31 of 42
Documentation and Training Approval
Edit and validate User documentation deliverables. Conduct
checkpoint review.                                             Yes
Edit and validate User training material. Conduct checkpoint
review.                                                        Yes
Conduct tech training doc checkpoint review.                   Yes
Plan for publication and distribution of User Documentation.   Yes
Phase Closure
Review training schedule. Modify as appropriate.               Yes
Store and control the documents in a secured library.          Yes
Revise Project Schedule and Project Budget, as required, and
plan for next phase.                                           Yes
Document Lessons Learned                                       Yes

Exit Criteria


Signature:




      5b16978f-5688-4a1b-8758-296d44e582bd.xls                       32 of 42
Development Project Checklist
                                                   Project Name
                                                   Program Mgr.
                                                   Project Mgr.




                        Deliverable                       Leader   Participants


   SD Phase Checklist
   Project Phase Kickoff Presentation
   Organization Chart
   PM Executing / Controlling templates, Project
   Notebook




   User Documentation (no template)




   Technical Training Documentation for Support
   Analysts (no template), Support Expectations

   Training Plan, User Training materials (no
   template)




         5b16978f-5688-4a1b-8758-296d44e582bd.xls                                 33 of 42
Project Schedule, Project Budget
Lessons Learned




                                             Date:




      5b16978f-5688-4a1b-8758-296d44e582bd.xls       34 of 42
                                                                 Software Development Project Checklist

NOTE : All steps are required for Class A projects

Deployment Phase
                                                                       Class B
                                                                       Required
                               Activity                                 Steps   Completed                        Deliverable
Phase Start Up
Initiate Deployment Activities                                          Yes                 SD Phase Checklist
Conduct project planning meeting.                                                           Project Phase Kickoff Presentation
Define/Refine project team roles and responsibilities                   Yes                 Organization Chart
Implement Control processes and use the management                                          PM Executing / Controlling templates, Project
approach.                                                               Yes                 Notebook

Review and update the Deployment Strategy and Plan developed
during the Testing Phase, as required. If applicable, review initial
site preparation and training requirements.                             Yes                 Deployment Strategy and Plan
Initial Deployment Preparation if applicable)
Confirm that site staff is available to support the deployment.
Review agreement on transitional support period.                        Yes
Verify the hardware and software configurations for target
installation meet specification.                                        Yes
Confirm that the technology, infrastructure, and support
requirements have been fulfilled.                                       Yes
                                                                                            Software Requirements Specification (includes
Create a Deployment Package.                                            Yes                 Traceability Matrix), Change Management Log
Define and archive the software configuration items for the
release package. Store the release package in the software
configuration library.                                                  Yes
Conduct a Release Readiness Review to ensure the package is
installable and operational. Obtain Release Sign-off                    Yes                 Release Readiness Review

Prepare for the initial deployment of the application/system (new
release). Reconfirm scheduled dates, site management
involvement, and involvement of all participating site personnel.       Yes                 Installation Test, Issues Log




        5b16978f-5688-4a1b-8758-296d44e582bd.xls                                                                                            35 of 42
Initial Deployment (if applicable)
Conduct a Deployment Kickoff Meeting at the initial installation
site (if applicable).                                                    Project Phase Kickoff Presentation
Conduct initial deployment test in a pre-production environment
using production data, if possible.                                Yes
Prepare for Site Business Transition.                              Yes
Conduct Installation Test and complete User Acceptance Test
Report.                                                            Yes   Acceptance Test, Installation Test

Production-Ready Review and get sign-off of Program Manager.       Yes
Monitor initial installation in the production environment.              Initial Release - Final Report
General Release Preparation
Formalize support procedures for system/application.               Yes
Application supportability during transitional period and modify
support plans, as required.                                        Yes
Conduct Readiness Review to determine if software is ready for
general release.                                                   Yes   Release Readiness Review
Submit required changes for approval.                              Yes   Request for Change, Change Management Log
Update Deployment phase plan (if required).                        Yes   Project Schedule, Timeline, Project Budget
Set up managing processes for deploying to other sites.            Yes
Verify site staff availability and system structure.               Yes




       5b16978f-5688-4a1b-8758-296d44e582bd.xls                                                                   36 of 42
General Release
Install software and test installation at sites.                      Yes
Monitor installation in the production environment.                   Yes
Conduct support assessment meeting to develop a plan for formal
transition of support services.                                       Yes

Transition support of the system/application to support services.     Yes
Final Client Acceptance
Prepare for and conduct Client Acceptance Review and obtain
customer approval.                                                    Yes   Deliverables Acceptance
Phase Closure
Initiate project closeout procedures. Close out all logs.             Yes
Evaluate project performance against Project Plan and archive all
project files and media.                                              Yes
Prepare a written evaluation of the support interaction.                    Support Interaction Final Report
Begin preparing the Project Closeout Report. Document all final
actions.                                                              Yes   Project Closeout Report
                                                                            Client Satisfaction Survey, Project Survey,
Prepare and conduct Post-Project Review.                              Yes   Contractor Exit Checklist
Review and submit lessons learned                                     Yes   Lessons Learned
Distribute the Post-Project Review report to appropriate staff, and
add to project repository.                                            Yes   Team Member Evaluation

Exit Criteria



Signature:




       5b16978f-5688-4a1b-8758-296d44e582bd.xls                                                                           37 of 42
t
    Project Name
    Program Mgr.
    Project Mgr.




           Leader                  Participants




          5b16978f-5688-4a1b-8758-296d44e582bd.xls   38 of 42
5b16978f-5688-4a1b-8758-296d44e582bd.xls   39 of 42
Date:




        5b16978f-5688-4a1b-8758-296d44e582bd.xls   40 of 42
                                                                Software Development Project Checklist

NOTE : All steps are required for Class A projects

Post-Deployment Phase
                                                                    Class B
                                                                    Required
                               Activity                              Steps   Completed
Operations
Receive and install non-major releases including patches and
minor feature/function upgrades                                   Yes
Conduct on-going operations, including processing, security, data
integrity, backup and disaster recovery and performance
monitoring                                                        Yes

Monitor project effectiveness and collect performance statistics.
Track issues and defects identified by category and provide
information to business partner and development organizations.
Identify any gaps in performance or quality and take corrective
actions. Collect and submit Technical Defects (i.e., bugs) to
Change Control Board or designated support services                 Yes
Process Improvement

Summarize and analyze program/performance issues, Technical
Defects, and other trends as part of a Post-Deployment Review       Yes
Conduct a user satisfaction survey and use this information to
improve practices and processes and to identify deficiencies that
need to be addressed                                                Yes
Measure benefits, cost savings, ROI and compare with initial
project estimates. Update appropriate Knowledge Bases (e.g.,
risk, estimating, lessons learned)                                  Yes

Exit Criteria
Not Applicable
Signature:




      5b16978f-5688-4a1b-8758-296d44e582bd.xls                                            41 of 42
Development Project Checklist
                                              Project Name
                                              Program Mgr.
                                              Project Mgr.




                   Deliverable                        Leader   Participants




                                              Date:




       5b16978f-5688-4a1b-8758-296d44e582bd.xls                               42 of 42

				
DOCUMENT INFO
Description: Controlling Idea Outline Template document sample