Chapter 2

Introduction

• CIOs face the challenge of choosing IT projects with the highest return on investment.
• Project portfolio management is crucial for IT departments.
• Thorough project management is essential for chosen system development projects.
• A key to successful project management is a realistic work assessment followed by plan adherence.

Project Selection

• Project evaluations are made considering the entire project portfolio.
• A feasibility study is needed to determine a project's portfolio contribution.
• Project portfolio management considers an organization's different project types.
• Approval committees must be selective with resource allocation given limited funds.
• Multiple high-payoff projects with similar risk might only have one chosen.

Creating the Project Plan

• Project management phases include:
  • Initiation
  • Planning
  • Execution
  • Control
  • Enclosure
• Formalized approaches to SDLC implementation are called methodologies.
• Methodologies include:
  • Waterfall Development
  • Parallel Development
  • V-model (a Waterfall Development variation)
  • Rapid Application Development (RAD)
    • Iterative Development
    • System prototyping
  • Agile Development

Waterfall Development

• Sequential project phases (requirements, design, implementation, testing, deployment, maintenance)

Parallel Development

• Dividing the project into smaller, parallel phases for faster completion.

V-model

• Combines Waterfall Development with concurrent verification and testing.

Rapid Application Development (RAD)

• Iterative Development
  • Rapid development cycles with frequent iterations
  • Incorporates user feedback throughout the process
• System Prototyping
  • Early system prototypes are built and tested
  • Iteration occurs based on user feedback

Throwaway Prototyping

• Prototypes are discarded after user requirements are clarified.

Agile Development

• A group of programming-centric methodologies focused on streamlining the SDLC.
• Emphasizes face-to-face communication.
• Extreme Programming prioritizes customer satisfaction and teamwork.

Extreme Programming

• Constant feedback cycles, pair programming, and test-driven development

Selecting the Appropriate Development Methodology

• Key factors to consider when choosing a methodology:
  • User requirement clarity
  • Technology familiarity
  • System complexity
  • System reliability
  • Short time schedules
  • Schedule visibility

Estimating the Project Time Frame

• Estimating Project Time Using Industry Standards
  • Utilizing historical data and standard industry estimates
• Function Point Approach
  • Quantifying system functionality to estimate development efforts

Developing the Work Plan

• Identifying Tasks
  • Breaking down the project into manageable tasks
• Work Breakdown Structure
  • Hierarchical breakdown of tasks
• The Project Work Plan
  • Defines the project work breakdown structure, scheduling, and resources.

Staffing the Project

• Staffing Plan
  • Describes staff allocations throughout the project's life cycle
  • Adding staff can increase overhead costs.
  • Hierarchical team structures (8-10 people) can reduce complexity
• Reporting Structure
  • Defines reporting relationships within the team
• Staffing Plan
  • Details the project team's composition
• Project Charter
  • Outlines the project's objectives and rules
• Functional Lead
  • Manages a group of analysts
• Technical Lead
  • Oversees programmers and technical staff

Motivation

• Use monetary rewards judiciously.
• Utilize intrinsic rewards:
  • Recognition
  • Achievement
  • The work itself
  • Responsibility
  • Advancement
  • Opportunities to learn new skills

Handling Conflict

• Clearly defined project plans
• Recognition of project importance
• Project charter outlining norms and ground rules
• Prior schedule commitments
• Forecasting potential impacts of other priorities

Coordinating Project Activities

• CASE (Computer-Aided Software Engineering) Tools
  • Software automating parts or the entire development process
  • Upper CASE: early phase automation (requirements, design)
  • Lower CASE: later phase automation (coding, testing)
  • Integrated CASE: automation across the SDLC
• Standards
  • Formal rules for file naming
  • Forms for progress tracking
  • Programming guidelines
• Documentation
  • Project binder
  • Table of contents
  • Continuous updates

Managing and Controlling the Project

• Project management involves balancing:
  • System size
  • Project completion time
  • Project cost
• Tools for Project Management
  • Gantt Chart: graphical representation of project schedule

Refining Estimates

• Updating estimates based on ongoing project progress

Managing Scope

• Scope Creep
  • The most common reason for schedule and cost overruns
  • Occurs when new requirements are added after project initiation
• Project Manager Role
  • Only essential requirements should be added after the project starts.

Timeboxing

• Setting a fixed deadline for the project
• Reducing functionality if necessary
• Focusing on core features instead of minor details

Timeboxing Steps

• Identifying key features
• Setting a deadline
• Iteratively developing and testing

Managing Risk

• Risk Assessment
  • Identifying potential risks and their impact
• Actions to Reduce Risk
  • Developing strategies to mitigate or avoid identified risks
• Revised Assessment
  • Periodically evaluating the effectiveness of risk management actions

Summary

• The project selection process utilizes project portfolio management to consider all organizational projects.
• The project plan defines tasks, time estimates, and other crucial information.
• Project management requires staffing and coordinating activities.
• Managing and controlling a project involve timeboxing and risk assessment.

Explore the key principles and phases of IT project management, focusing on project selection and portfolio management. This quiz covers essential methodologies for successful system development and realistic planning. Understand how to evaluate projects and allocate resources effectively within an IT department.