 |
Functional Project Management Requirements
06 February 2009
| n | Define functional requirements. The functional requirements of each application must be defined. A summary list of many of the major categories of functional requirements appears at the top of this page. Following the PMO's methodology for project management software requirements specification, the functional requirements should be fully developed. This work includes reviewing the goals and objectives of the organization and communication with all users and stakeholders. The PMO may wish to retain specialized expertise in information technology (IT) development, either internal or external, for this evaluation.
| | n | Define technical requirements. Working in cooperation with the organization's information technology (IT) department, the PMO team should define the technical requirements for each application.
|
Here is an example of a list of software applications by function: | List of Software Applications by Function2/1/2007 | | Application Function | Problem(s) Solved /
Goals Met | Deployed to | Applications Under Consideration | Planned Deployment Date | | Project Management Scheduling Tools | § Standardize status tracking and management of projects to reduce costs§ Implement best practices for schedule estimation | § Deploy new tool for all future projects. § Allow current tools to end of current projects, then discontinue | § ABC PMtool, version 10 (new/ external)§ XYZ PMtool, version 3 (new/ external)§ MS Project® 2000 (internal)§ MS Project ® 2002 (internal) | 4/1/2007 | | Full PMIS | § Optimal implementation of PM best practices§ To reduce project cost and risk as much as possible | Entire organization | To be determined | Sometime in 2008. Planning for this deployment will begin in the 2nd half of 2007. | | Executive Dashboard | n/a | Only if included with full PMIS | To be determined | Cost justification evaluation will occur in late 2007. | | | | | | | | | | | | |
The functional and technical requirements for each application can be listed in the software requirements section of the Software Execution Plan. Here is a partial example of the requirements for a project management scheduling tool: | Functional Requirements for Software ApplicationsProject Management Scheduling Tool1/7/2007 | | ID # | Category | Name | Specifications | | FSR-01 | User Features | Standard Windows | User interface must operate using standard MS Windows® visual, mouse, and keyboard interface | | FSR-02 | Methodology Compatibility | Life Cycle | Must allow Company project management life cycle implementation, defining all activities within standard life cycle phases. | | FSR-03 | Standards/processes compatibility | PERT and CPM | PERT and CPM scheduling must function per PMI standard | | FSR-04 | Access Control | Network Access Control | Access control must be linked to network userID with appropriate views and data sets available to defined users, according to standard API defined by IT standard A123-2006 | | | | | | | | | | |
| Technical Requirements for Software ApplicationsProject Management Scheduling Tool1/7/2007 | | ID # | Name | Specifications | | TSR-01 | OS compatibility | Must work with Windows XP® Professional | | TSR-02 | Printing compatibility | Must generate PDF files for all views, documents, and graphics | | | | | | | | |
Copyright © Method123 Ltd 2000-2012
|
|
|
|
