Managing System Development 2024

Managing System Development

Objective

  • Assess appropriate controls for managing risks in information systems development projects.

Learning Outcomes

  • Identify typical stages in an information systems project.

  • Recognize risks associated with typical project phases.

  • Understand approaches used by project managers to control projects.

Management Issues

  • Questions for managers:

    • How to avoid high failure rates for IS implementations?

    • What specific risks relate to management of information management projects?

Typical Phases in Systems Development Project

  1. Initiation

    • Purpose: Start-up phase, assess feasibility.

    • Inputs: Business case.

    • Process: Feasibility analysis.

    • Output: Decision to proceed.

  2. Analysis

    • Purpose: Define requirements and determine system needs.

    • Inputs: Business case and user requirements documentation.

    • Output: Decision to proceed.

  3. Design

    • Purpose: Specify system configuration.

    • Inputs: Requirements evaluation.

    • Output: Decision to proceed.

  4. Development

    • Purpose: Implement design and configure system.

    • Inputs: Design document.

    • Output: Decision to proceed.

  5. Implementation

    • Purpose: Deploy system.

    • Outputs: Live system, project closedown report, and decision to proceed after testing.

  6. Maintenance

    • Purpose: Monitor and enhance system performance.

    • Outputs: Upgrades or patches as required.

Feasibility Types

  • Economic: Cost-benefit analysis of solutions.

  • Technical: Assess technical solutions, make-or-buy decisions.

  • Operational: Evaluate impact on business processes.

  • Organizational: Fit with structure and culture.

Project Resolution History (2000 - 2008)

  • Success remained low:

    • Succeeded: 32% in 2008.

    • Failed: 24% in 2008.

    • Challenged: 44% in 2008.

Constraints on IS Project Management

  • Project Management Constraints:

    • Project duration, effort, resources, cost, and performance.

Variations in Requirements

  • Different interpretations can lead to mismatches between project requirements and deliverables.

Success Factors in Development Projects

  1. Executive sponsorship is crucial.

  2. User involvement enhances requirements definition and project value.

  3. Experienced project management leads to greater success.

  4. Clear business objectives aid in focus.

  5. Managed scope and reliable estimates improve outcomes.

Implementation Methods

  1. Immediate Cutover: Fast but high risk.

  2. Parallel Running: Lower risk, but costlier.

  3. Phased Implementation: Introduces modules in stages.

  4. Pilot System: Tests before full rollout.

Project Management Stages

  • Estimation: Identify activities (WBS).

  • Resource Allocation: Assign people.

  • Scheduling: Timeline determination.

  • Budgeting: Estimate project costs.

  • Monitoring and Control: Assess and take corrective action.

PRINCE2 Methodology

  • Stages for monitoring progress with clear roles and defined outputs to ensure project viability.