![]() |
|||||||||||||||||||||||||||||||||||||||||||||
Define Project Management Tool Requirements03 January 2009Define Project Management Tool RequirementsA requirement is a necessary attribute of a process or product. Requirements for project management tools are defined using the two steps shown in this diagram:
1. Define General Tool Requirements 2. Define Specific Tool Requirements
Take these two steps to define general tool requirements: 1. Define compatibility requirements. All tools must be compatible with the PMO's methodology, standards, and processes. There may be other compatibility requirements as well, such as compatibility with software or database systems. These should be documented in the general tool requirements table of the Tools Execution Plan. 2. Define goal-based and problem-based requirements. Some general requirements are derived from the goals the PMO seeks to achieve and the problems it is tasked to solve. For example, if the PMO is tasked to reduce inefficiency by creating a single standard for online project management, this creates two requirements: Each tool must, whenever possible, apply to all projects. Also, whenever a tool does not apply to all projects, a decision rule governing use of alternate tools must be defined. Review the goals in the Execution Plan and problems in the PMO Charter to identify these requirements. Complete the general tool requirements table by entering goal-based and problem-based requirements. Posted in General
Copyright © Method123 Ltd 2000-2012 |
|
||||||||||||||||||||||||||||||||||||||||||||