10.14 Alternative Work Pattern Selection

 < Day Day Up > 



During the Planning phase, the Project Manager evaluates the project statement and High-Level Solutions Document and uses the criteria for selecting either the full sequential work pattern or an alternative work pattern. This section proposes some criteria for selecting an alternative work pattern. (Note: Criteria for selection may not be mutually exclusive [e.g., complexity and size because size] may be a factor of complexity.)

Determine the type of system development:

  • New development

  • Modification or enhancement of existing system

  • Prototype system

  • Procurement of a COTS system

  • O&M small-scale enhancement

  • O&M project

Determine the cost of the system development project using the followingguidelines:

  • Class 1: Very large projects with estimated development or life cycle costs of more than $20 million

  • Class 2: Large projects with estimated development or life cycle costs between $10 million and $20 million

  • Class 3: Midsize projects with estimated development or life cycle costs between $2.5 and $10 million

  • Class 4: Small projects with estimated development or life cycle costs between $500,000 and $2.5 million

  • Class 5: O&M enhancements with estimated life cycle costs less than $500,000

Determine mission criticality of the proposed system development effort: Most critical (C1) to non–mission critical (C5).

Determine the risk of inability to achieve the project objectives from highest (R1) to lowest (R4), based on one or more of the following:

  • Risk due to high uncertainty associated with the system’s requirements, the technology that the system will employ, or the way that the system will affect the SEP’s business process

  • Risk due to highly compressed development time (low turnaround time) because of an emergency or legal, business, or political requirements

  • Risk due to high visibility resulting from public or political attention or requirements

Determine the complexity of the system development effort from highest-(E1) to lowest (E3), based on one or more of the following:

  • The project affects many organizations or functional areas within an organization, thus adding a level of difficulty regarding the definition of requirements.

  • The project results from business process reengineering, dramatically altering the use of information technology.

  • The project requires new or rapidly advancing technology.

  • The project requires a long time for development.



 < Day Day Up > 



Managing Software Deliverables. A Software Development Management Methodology
Managing Software Deliverables: A Software Development Management Methodology
ISBN: 155558313X
EAN: 2147483647
Year: 2003
Pages: 226

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net