PM Earth
 

Prepare Project Management Software Adoption

20 February 2009

Prepare Project Management Software Adoption Schedule

The statement of approach is a complex document that addresses five issues:

n

Which application functions will be adopted and when. Will the PMO provide software for project scheduling, full project management tools, executive or stakeholder dashboards, or other functions? When will they be available?

n

The future of each internal application. Each application used internally for project management may be discontinued immediately, phased out after current project are complete or after a specified time period, allowed to continue in limited use, or adopted for use by the entire organization. The PMO team, in addition to making these decisions, must justify them and convince stakeholders and users of current applications to accept these choices.

n

How will each application be implemented? See the discussion of software implementation below.

n

How will applications be managed? Will the PMO purchase software, or will each department or project purchase it? How will the PMO coordinate with IT services to install and maintain applications?

n

What services will be associated with the applications? Will the PMO provide application training in the Train Staff service? Will the applications be used to automate online project management Report Activities? Will other services use applications? How?


With regard to software implementation, there is a classical contrast called the "build vs. buy" decision. This does not accurately reflect the work that needs to be done to adopt software. In fact, all five of the following processes may be used during software adoption, and the total cost is the sum of the cost of these five activities:

n

Buying. One or more software applications may be purchased. Include sufficient licenses and annual maintenance or upgrade fees in the cost.

n

Configuration. Almost all applications require some degree of configuration, where information unique to the organization or specific to how the application will be used is entered.

n

Customization. Sometimes, customization through programming, the addition of macros or automated functions, or addition of custom fields for information is required.

n

Integration. Sometimes, additional work is needed to make applications work with one another or to make applications work in the specified environment.

n

Building. Sometimes, a module or application is developed from scratch through computer programming.


 
 
Posted in General


Copyright © Method123 Ltd 2000-2017