IT Project Management

IT Project Management Book

Introduction

The IT Project Management Practices Guide (Guide) contains a repeatable, institution-wide approach for the management of application development and/or software procurement and deployment projects. These project management (PM) practices are transferable to other types of projects (beyond IT) that would benefit from project management. The following sections of the Guide represent the ordered steps for each project, to ensure that proper activities and management are utilized:
Step 1. Application of Project Management – distinguishes what types of work should and should not be categorized as projects and includes the general flow of projects from idea into deployment. This step also defines and outlines project management process groups;
Step 2. Project Classification – assigns a classification level to a project based on a combination of complexity and risk; this step also defines projects that require an additional level of management, as defined by State of Texas guidelines;
Step 3. PM Required Processes – details processes required to be completed for each level of project, as classified in Step 2; and
Step 4. Document Management – outlines document management requirements for documents created as part of PM Required Processes
Appendix A provides detailed document templates, based on the State of Texas DIR general templates. Note that DIR announced that templates will change in the fall 2008. At that time, the templates in Appendix A will be updated accordingly. Appendix B offers project management guidelines for portfolio management and Appendix C lists the references used in the development of this Guide.
Step 1. Application of Project Management
Types of Work
The Guide should be used for the management of Information Technology projects. Initiatives categorized as ‘tasks’ or ‘operational’ are not required to follow the project management methodologies outlined within the Guide. Upcoming/potential work should be analyzed to determine which category is applicable:
• Task
• Small piece of work
• Independent of a project
• Lasting not longer than a few person-hours
• Involving only a few people
• Meant to accomplish a simple and straightforward goal
• May be a component of operational work
• May require change management processes
IT Project Management Practices Guide Page 2 of 83 ASU, HSC, TTU, TTUS
• Rated as such Project Complexity and Risk Assessment model (Step 2)
• Operational
• Ongoing work to sustain or provide a service
• Change management processes applicable for non project-related changes
• Project
• Temporary endeavor (defined beginning and end)
• Which uses progressive elaboration
• To create products, services, or results
• Texas Project Delivery Framework Project
• Identified in a state agency’s biennial operating plan whose development costs exceed $1 million and either takes longer than one year to reach operation status; involves more than one agency of the State; or substantially alters work methods of state agency personnel or the delivery of services to clients; or
• So designated by the legislature in the General Appropriations Act.
• Such projects are also considered major information resources projects,