Usually Implementation of project may contain steps are: Pre-project preparation, project planning, implementation, analysis, continual improvement and closure. But when you are talking for particular project plan implementation, you have to understand and need to following steps are:
After completing the first three implementation project team meetings, you’re ready to begin building your implementation plan document. Essentially, you accomplish this task by pulling together the documents you’ve created to this point in the process, as the following list describes including references to previous articles. These documents become your implementation plan.
After you get them in place, get everyone on the project to sign off on the package. With signatures in hand, you’re ready to hit the ground and get things rolling!
Actually there are six major steps to success the project. Usually for each project, project implementation steps can be varying from other project. Hence, number of steps can be different.
Here you can get the 6 major steps that will be helpful for the success of your project. So, let's see each steps with dept.:
Implementation Project Team's Roles' Matrix
Project Team Meetings & Training
In preparing for your implementation development environment and for the rollout of your software at the customer site, you will conduct a thorough capacity-planning study. During this capacity-planning study, you evaluate the customer’s current technical environment so that you can make accurate recommendations for any hardware or software upgrades that the customer needs.
The below Capacity Planning Worksheet is provided to assist you in doing the capacity planning study. For details on the capacity planning study process, you can refer to the Defining the Customer's Environment section in previous articles.
Capacity Planning Worksheet
Gap Analysis
Gathering the customer’s customization requirements and then performing a gap analysis between the “plain-vanilla” software and any customizations that the customer wants.
The Project Scope Document (PSD) for the implementation team serves the same purpose as the PSD for your earlier development team. The only difference, of course, is the focus of these deliverables -- here you’re focused solely on a single implementation of your software for a specific customer. Your PSD will include your: Statement of Scope (SOS) (mission statement), project goals, assumptions, and constraints. For more information on the PSD, you can refer to previous article. You can use Template 3-4 Project Scope Document on the CD-ROM to create a PSD for your software project.
Your third implementation team meeting is the Work Breakdown Structure (WBS) meeting. Here is where you divide up the work to do (as the RD and the PSD define it) among your team members, estimate the task durations and costs. The worksheet below is designed to assist you in this process
Controlling the ever-creeping scope and other risks affecting your software project is one of the biggest challenges that you must face as a project manager. Although you go to great lengths to nail everything down by creating an elaborate Work Breakdown Structure (WBS) that you organize along a critical path, your project is still subject to the inescapable monkey wrench of change.
You can refer to previous project management articles for complete details on creating the WBS and the critical path. Thus you need to devise some sort of change/risk-management (C/RM) plan for your project. A good C/RM plan encompasses the following four easily identifiable facets: identification, assessment, aversion, and monitoring. For more information, you can refer to previous articles.
After completing the first three implementation project team meetings, you’re ready to begin building your implementation plan document. Essentially, you accomplish this task by pulling together the documents you’ve created to this point in the process, as the following list describes including references to previous articles. These documents become your implementation plan.
After you get them in place, get everyone on the project to sign off on the package. With signatures in hand, you’re ready to hit the ground and get things rolling!
- Implementation Team's Roles: Implementation Team's Roles' Matrix, Team Meetings and Training
- Customer’s Technical Environment: Capacity Planning Worksheet
- Requirements: Requirements Document (RD), Gap Analysis
- Project Scope: Project Scope Document (PSD)
- Work Breakdown Structure (WBS) & Resource estimates: Work Breakdown Structure (WBS), Assignments, & Cost Estimation Worksheet
- Change/Risk Management plan
Actually there are six major steps to success the project. Usually for each project, project implementation steps can be varying from other project. Hence, number of steps can be different.
Process Steps
Here you can get the 6 major steps that will be helpful for the success of your project. So, let's see each steps with dept.:
Implementation Team's Roles
Implementation Project Team's Roles' Matrix
Team
Member
|
Executive
Sponsor
(Customer)
|
Project
Manager
(Customer)
|
Technical
Lead
(Customer)
|
Technical Account
Manager
(Vendor)
|
Developers
|
Beta/
Acceptance
Testers
(Customer)
|
Trainer
(Vendor)
|
Employee1
|
X
|
X
|
|||||
Employee2
|
X
|
||||||
Employee3
|
X
|
||||||
Employee4
|
X
|
X
|
Project Team Meetings & Training
Meeting
|
Scheduled date
|
Date Held
|
Implementation Project Kickoff
|
||
Implementation Project Plan Brainstorm Session
|
||
Work Breakdown Structure (WBS)
|
||
Joint Application Design sessions
|
||
Joint Application Development sessions
|
||
User training
|
Customer's Technical Environment
In preparing for your implementation development environment and for the rollout of your software at the customer site, you will conduct a thorough capacity-planning study. During this capacity-planning study, you evaluate the customer’s current technical environment so that you can make accurate recommendations for any hardware or software upgrades that the customer needs.
The below Capacity Planning Worksheet is provided to assist you in doing the capacity planning study. For details on the capacity planning study process, you can refer to the Defining the Customer's Environment section in previous articles.
Capacity Planning Worksheet
|
Component
|
Configuration Parameter
|
|
Network
bandwidth
|
|
|
Hardware
|
|
|
Software
|
|
|
Operating
system
|
|
|
Database
sizing
|
|
|
Systems
integration/interfaces with other systems
|
|
|
Migration/integration path
|
|
Requirements
Requirements Document
At the customer site the implementation team gathers your customer’s customization requirements, and their technical environment. Many of the tasks that you must face in gathering requirements for an implementation are the same as those you face while developing the software.Gap Analysis
Gathering the customer’s customization requirements and then performing a gap analysis between the “plain-vanilla” software and any customizations that the customer wants.
Project Scope
Project Scope Document
The Project Scope Document (PSD) for the implementation team serves the same purpose as the PSD for your earlier development team. The only difference, of course, is the focus of these deliverables -- here you’re focused solely on a single implementation of your software for a specific customer. Your PSD will include your: Statement of Scope (SOS) (mission statement), project goals, assumptions, and constraints. For more information on the PSD, you can refer to previous article. You can use Template 3-4 Project Scope Document on the CD-ROM to create a PSD for your software project.
Work Breakdown Structure (WBS) & Resource Cost Estimates
Your third implementation team meeting is the Work Breakdown Structure (WBS) meeting. Here is where you divide up the work to do (as the RD and the PSD define it) among your team members, estimate the task durations and costs. The worksheet below is designed to assist you in this process
Change/Risk Management Plan
Controlling the ever-creeping scope and other risks affecting your software project is one of the biggest challenges that you must face as a project manager. Although you go to great lengths to nail everything down by creating an elaborate Work Breakdown Structure (WBS) that you organize along a critical path, your project is still subject to the inescapable monkey wrench of change.
You can refer to previous project management articles for complete details on creating the WBS and the critical path. Thus you need to devise some sort of change/risk-management (C/RM) plan for your project. A good C/RM plan encompasses the following four easily identifiable facets: identification, assessment, aversion, and monitoring. For more information, you can refer to previous articles.
Project Plan template
Wow, cool post. I'd like to write like this too - taking time and real hard work to make a great article... but I put things off too much and never seem to get started. Thanks though. visit the website
ReplyDelete