multi
incomplete or changing system requirements. extensive user involvement. thorough and detailed project plans. strong support from upper management. |
incomplete or changing system requirements. limited user involvement. overly complex technology. lack of executive support. |
project management. systems analysis. feasibility assessment. risk management. |
client. oversight committee. user. project manager. |
project development tasks. user tasks. project management tasks. client tasks. |
agile. traditional. structured. heavyweight. |
agile development. RAD. PERT/CPM. weighted scoring. |
business benefits. project stakeholders. project risks. system capabilities. |
context prototype. design prototype. functional prototype. proof-of-concept prototype. |
only key project team members. only key project stakeholders. only the project manager and senior executives. key project team members and project stakeholders. |
|
identifying potential trouble spots that could jeopardize project success. developing a work breakdown structure, including intermediate deliverables. understanding how the project contributes to the organization's strategic direction. listing all stakeholders with an interest in the system. |
economic resource organizational and cultural resource |
A system will create changes to long-standing work procedures for users. Management imposes an unrealistic deadline for deploying the system. A key development team member is hired away by a competitor. Users of the system possess a low level of computer competency. |
organizational and cultural resource economic schedule |
organizational and cultural costs, resource costs, and technological benefits. development costs, operational costs, and anticipated benefits. internal user costs, external user costs, and sponsor benefits. inception costs, construction costs, and deployment benefits. |
development costs. organizational costs. incremental costs. operating costs. |