|

Introduction
Why do projects that are well designed, expertly built, and attractively packaged for delivery to internal customers often fail to meet their objectives? A common reason is the “throw it over the wall and the customers will learn to use it” method of deploying projects. It never works. IT teams face this problem continually, and as a result, many projects fail to deliver the promised return on investments. The reasons are many: the project team has been working long hours to get the project finished and is ready to move on to new opportunities; end-users/customers are too busy to learn the system. And finally, there is the often-held belief by too many customers that the development team is ultimately responsible for successful project implementation.
Even when IT organizations begin to educate their teams in the principles and practices of project management, the focus is placed mostly on the development teams, and the people responsible for successful project deployment (primarily end-users/customers) are left out. It is imperative that the appropriate end-users/customers be properly educated and trained in the skills of project deployment and implementation.
Objectives
The goals of this seminar are to provide the participants with a clear understanding of the differences between the processes of project development and project deployment. They will learn the required skills to determine their roles and responsibilities in successful project deployment and implementation. They will learn the tools and techniques for developing comprehensive task plans; estimating and scheduling their tasks, and the importance of monitoring project vital signs.
Upon successful completion of this seminar participants will be able to:
Differentiate between project development and project deployment
Identify the stages and steps of the PPA
Outline the roles and responsibilities of project end-users/customers
Generate a WBS
Produce a task network diagram
Produce realistic and defensible estimates
Create a viable schedule
Track relevant project vital signs
Propose steps to retire an old system
|