Project Management Scheduling

---

These five issues are documented in the statement of approach. Here is an example:

Statement of ApproachSoftware Execution Plan2/28/2007
Summary by Application Function
Application Function				Summary Plan
Project Manager Scheduling
Application Name	Internal or External		Start date		Approach	End Date
ABC PMTool Version 10	External		3/1/2007		Purchase & Configure	6/1/2007
MS Project® 2000	Internal		n/a		Allow until project using it are complete	Estimated 2/2008
MS Project® 2002	Internal		n/a		Allow until projects using it are complete	Estimated 6/2008
Full PMIS
Application Name	Internal or External		Start date		Approach	End Date
To be determined	External		8/2007		Purchase plus configuration and customization through programming	6/2008
Executive Dashboard
Application Name	Internal or External		Start date		Approach	End Date
To be determined	External		Evaluation 10/2007		Determine value over cost. Integrate with full PMIS development if ROI is sufficient	To be determined
Application Management Policy
Enter the information below. If some applications will be managed differently than others, create multiple sections, one for each management policy
Applies to:		All Applications (except those being phased out)
Ownership:		PMO
Installation Management:		IT Dept. x9-9999. New purchase approval from PMO, x8-8888
Maintenance Management:		IT Dept. x9-9999.
User Support:		PMO Support Services. Start at internal web support page, www.company.com/pmo/support.htm.
Training:		PMO Training Services. Start at internal web training page, www.company.com/pmo/training.htm.
Related Services		§       Software training. PMO will provide job-specific training in use of application, including full feature training for PMs and project administrators, scheduling training for PM leads, timesheet data entry for all project staff on all projects using this software.§       PM skills training. PM skills training will include examples generated by this software, and hands-on portions of this training will be in the supported software package. §       Executive reporting. Reports will be generated from ABC PMtool data export to Excel. Later, full PMIS will be used for this function.§       Executive oversight training. This training will use ABC PMtool data exported to Excel. Later, full PMIS (or executive dashboard will be used for this function.

 

Once the statement of approach is complete, the PMO has defined the scope and approach to software adoption. The last step is to prepare a milestone chart for implementation of the project management software solution. Here is a partial example:

PMO Software Adoption Milestone Chart[DATE]
Application Function	Application	Begin Work	Begin Testing	Application Ready for Delivery
PM Scheduling	ABC PMTool	3/1/2007	4/1/2007	6/1/2007
PM Scheduling	MS Project® 2000	3/1/2007 (add printer driver only)	3/8/2007	3/15/2007
PM Scheduling	MS Project® 2002	3/1/2007 (add printer driver only)	3/8/2007	3/15/2007
Full PMIS	To be determined	8/1/2007	2/1/2008	6/1/2009
Executive Dashboard	To be determined	10/1/2007 – evaluation only	To be determined	If implemented, to be determined

 

Next Steps

You have completed the process of adopting software. Now  you can:

n	View a project management template of the Software Execution Plan.
n	Learn how to Adopt Databases.

 
 


Copyright © Method123 Ltd 2000-2012