MPMM Method123 Project Management Methodology

Project Management Software Requirements

13 February 2009

Define Project Management Software Requirements

The three steps of defining software requirements are listed in this diagram:

1.      Prepare List of Applications

2.      Define Functional Requirements

3.      Define Technical Requirements

Step one must be done first. Steps two and three can be done in either order, or simultaneously.

n

Prepare list of applications. The list of applications is the answer to the question: What software programs will solve the problems the PMO is tasked to solve? What software applications will help the PMO meet its goals? Only those applications which benefit the organization and help the PMO meet its goals should be adopted. To prepare the list of applications, the PMO team:

§       Reviews the PMO's charter and business case, with particular attention to goals to be achieved and problems to be solved.

§       Defines what problems exist due to the lack of software or due to the limitations of software currently in use.

§       Defines what problems exist due to limited use of current software.

§       Prepares a list of applications which, if adopted, will solve these problems and help achieve the PMO's goals. The list includes:

  • Applications to be used internally, within the PMO
  • Applications to be used throughout the organization
  • Applications to be used on some projects or in some part of the organization

Once each application is listed, the PMO team then defines its functional and technical requirements.


 
 
Posted in Project Office


Copyright © Method123 Ltd 2000-2012

 
Tips and Hints Archive
A Good Project Manager
or the Report Status Service
Service Features
Report Status Service
Management Software
Project Management Services
Risk Management
Execution Phase
All Tips and Hints
Categories
General (45)
Project Management Office (45)
Project Office (34)
PMO (38)

RSS FEED