Systems Analysis and Design - Managing Systems Projects Vocabulary

Overview of Project Management

• Project Management Framework

  • Definition: Project management is the process of planning, scheduling, monitoring and controlling, and reporting on the development of an information system.

  • Core Success Criteria: A project is deemed successful if it meets four mandatory criteria:

  • Completed on time.

  • Completed within budget.

  • Meets all specified functional requirements.

  • Delivers a quality product that satisfies its end users.

• The Project Triangle

  • Triangular Relationship: Information system development is defined by three interdependent factors: Cost, Scope, and Time.

  • Constraint Mechanics: Any change made to one leg of the triangle directly impacts and forces adjustments in the remaining two legs.

  • Example: Increasing the project scope typically requires an increase in budget (cost), an extension of the deadline (time), or both.

  • Project Manager Challenge: Finding and maintaining the optimal balance among cost, scope, and time while fulfilling system specifications.

• Primary Roles of a Project Manager

  • Project Planning: Identifying all project tasks, evaluating resource dependencies, and accurately estimating the completion time and cost for every activity.

  • Project Scheduling: Developing a detailed time calendar showing specific tasks, task dependencies, and the critical path that dictates overall project duration.

  • Project Monitoring: Directing, supervising, and coordinating work assignments, team resources, and workloads daily to keep the project on track.

  • Project Reporting: Generating concise, regular status updates and progress reports tailored for management, end users, and project team members.

Work Breakdown Structure (WBS)

• Definition & Fundamentals

  • Work Breakdown Structure (WBS): The process of breaking down a complex project into a logical series of smaller, discrete, and manageable tasks.

  • Task / Activity: Any unit of work that has a clearly defined beginning and end, consumes organizational resources (such as people, time, or money), and is small enough to be tracked effectively.

  • Event / Milestone: A recognizable reference point used to mark a significant achievement, completion of a key deliverable, or formal phase transition. Milestones consume zero time and zero resources directly.

• Graphical Scheduling Tools

  • Gantt Chart

  • A horizontal bar chart representing a set of tasks against a timeline.

  • Position on the vertical axis represents project tasks, while the horizontal axis displays time increments (days, weeks, or months).

  • Shows planned project duration versus actual progress achieved using visual indicators (such as inner progress bars).

  • Simplifies tracking complex projects by organizing individual tasks under broader task groups.

• PERT / CPM Charts

  • PERT (Program Evaluation Review Technique): Developed by the United States Navy to manage complex defense engineering programs.

  • CPM (Critical Path Method): Developed simultaneously by private industry for enterprise project scheduling.

  • Bottom-Up Technique: Constructs total project timelines by aggregating estimates from individual low-level tasks upwards.

  • Network Display: Visualizes complex task patterns and interrelationships using network diagrams where boxes represent tasks and directional arrows denote task flows.

• Developing a WBS

  • Decomposition Process: Transforming narrative project requirements into an structured WBS task table.

  • Version 1: Unstructured paragraph describing work sequentially.

  • Version 2: Paragraph with key actionable verbs emphasized.

  • Version 3: Bulleted task list itemizing discrete activities.

  • Final Tabular WBS: Tabulated dataset incorporating Task Number, Task Description, Duration, and Predecessor Tasks.

• Task Duration Estimation & Formulas

  • Time Measurement Units: Expressed in hours, days, or weeks based on project granularity.

  • Three-Point Estimation Method: Project managers develop three distinct time estimates for each task:

  • Best-case estimate ($B$): The minimum possible time required under optimal conditions.

  • Probable-case estimate ($P$): The most realistic, expected duration under normal conditions.

  • Worst-case estimate ($W$): The maximum required time under highly adverse conditions.

  • Weighted Task Duration Formula: $\text{Expected Duration} = \frac{B + 4P + W}{6}$

• Factors Affecting Task Durations

  • Project Size: Scope scale and total number of embedded tasks. Unplanned operational events affecting individual productivity must be factored in.

  • Human Resources: Technical skill level, project experience, team composition, turnover, and operational friction.

  • Experience with Similar Projects: Utilizing historical data, time tracking records, and cost metrics from previously completed systems.

  • Constraints: System requirements, regulatory requirements, fixed release dates, or immovable budget caps.

Identifying Task Patterns and Dependencies

• Task Box Structure

  • In PERT/CPM diagrams, every task is framed within a standardized 5-cell box format containing:

  • Top Header: Task Name

  • Middle-Left: Start Day/Date

  • Middle-Right: Task ID

  • Bottom-Left: Finish Day/Date

  • Bottom-Right: Task Duration

• Types of Task Dependencies

  • Dependent Tasks: Tasks arranged in strict sequential order. A successor task cannot begin until its predecessor task is completely finished.

  • Rule: Finish time of preceding task controls start time of successor task.

  • Timing Formula: $\text{Start Date (Successor)} = \text{Finish Date (Predecessor)} + 1$

• Multiple Successor Tasks: A single predecessor task whose completion triggers two or more concurrent successor tasks simultaneously.

  • Rule: Finish time of the single predecessor dictates the start date for all branching successor tasks.

• Multiple Predecessor Tasks: A single successor task that requires two or more prior tasks to be fully completed before it can begin.

  • Rule: The start date for the successor task is governed by the latest (largest) finish date among all its predecessor tasks.

• Linguistic Logic Clues

  • "Then": Signals sequential dependent tasks (e.g., "Do Task 1, then do Task 2").

  • "When / Start Two Tasks": Signals multiple successor tasks (e.g., "When Task 2 is finished, start Task 3 and Task 4").

  • "And / Done": Signals multiple predecessor tasks (e.g., "When Tasks 5 and 6 are done, start Task 7").

Calculating the Critical Path

• Critical Path Definition

  • A sequence of dependent tasks that, if delayed by even a single day, directly extends the overall project completion date.

  • Represents the longest overall duration path through the project network diagram.

  • Tasks on the critical path have zero float or slack time.

• Forward Pass Calculation Procedure

  1. Step 1: Network Construction: Arrange all tasks according to logical dependencies. Populate Task Name, ID, Duration, and Predecessors.

  2. Step 2: Start Date Calculation: Set Initial Task start to Day 1. Calculate finish date: $\text{Finish Day} = \text{Start Day} + \text{Duration} - 1$

  3. Step 3: Sequential Propagation:

  • For single predecessor tasks: $\text{Start Day (Successor)} = \text{Finish Day (Predecessor)} + 1$

  • For multiple successor tasks: Apply predecessor's finish date $+ 1$ as the start date across all branching tasks.

  • For multiple predecessor tasks: Find $\max(\text{Finish Day of Predecessors})$. The successor start date is $\max(\text{Finish Day}) + 1$

• Worked Calculation Example 1 (5-Task System)

  • Task 1 (Obtain Authorization): ID 1 | Duration: 10 days | Start: Day 1 | Finish: Day 10

  • Task 2 (Hire Analyst): ID 2 | Duration: 30 days | Predecessor: Task 1 | Start: Day 11 | Finish: Day 40

  • Task 3 (Plan Training): ID 3 | Duration: 5 days | Predecessor: Task 2 | Start: Day 41 | Finish: Day 45

  • Task 4 (Arrange Logistics): ID 4 | Duration: 25 days | Predecessor: Task 2 | Start: Day 41 | Finish: Day 65

  • Task 5 (Announce Training): ID 5 | Duration: 30 days | Predecessors: Tasks 3, 4 | Start: Day 66 ($\max(45, 65) + 1$) | Finish: Day 95

  • Critical Path: Tasks 1-2-4-5 (Total Duration: 95 Days).

• Worked Calculation Example 2 (11-Task System)

  • Task 1 (Develop Plan): Duration 1 | Start: Day 1 | Finish: Day 1

  • Task 2 (Assign Tasks): Duration 4 | Predecessor: 1 | Start: Day 2 | Finish: Day 5

  • Task 3 (Obtain Hardware): Duration 17 | Predecessor: 1 | Start: Day 2 | Finish: Day 18

  • Task 4 (Programming): Duration 70 | Predecessor: 2 | Start: Day 6 | Finish: Day 75

  • Task 5 (Install Hardware): Duration 10 | Predecessor: 3 | Start: Day 19 | Finish: Day 28

  • Task 6 (Program Test): Duration 30 | Predecessor: 4 | Start: Day 76 | Finish: Day 105

  • Task 7 (Write User Manual): Duration 25 | Predecessor: 5 | Start: Day 29 | Finish: Day 53

  • Task 8 (Convert Files): Duration 20 | Predecessor: 5 | Start: Day 29 | Finish: Day 48

  • Task 9 (System Test): Duration 25 | Predecessor: 6 | Start: Day 106 | Finish: Day 130

  • Task 10 (User Training): Duration 20 | Predecessors: 7, 8 | Start: Day 54 ($\max(53, 48) + 1$) | Finish: Day 73

  • Task 11 (User Test): Duration 25 | Predecessors: 9, 10 | Start: Day 131 ($\max(130, 73) + 1$) | Finish: Day 155

  • Critical Path: Tasks 1-2-4-6-9-11 (Total Project Duration: 155 Days).

Project Monitoring, Control, and Reporting

• Structured Walk-Throughs

  • A peer review process where project team members review the work of another team member.

  • Conducted continuously throughout all phases of the Systems Development Life Cycle (SDLC).

  • Formally categorized based on project phase as design reviews, code reviews, or testing reviews.

• Schedule Maintenance & Variance Control

  • Project managers proactively monitor schedule performance by:

  • Anticipating potential bottlenecks and risks in advance.

  • Developing alternative path mitigation strategies to limit schedule impact.

  • Selecting optimal problem-solving interventions when delays occur.

• Project Status Meetings & Reports

  • Project Status Meetings: Regularly scheduled team interactions used to communicate updates, align technical approaches, analyze shared issues, and hold brainstorming sessions.

  • Project Status Reports: Structured periodic formal reporting distributed to management, project sponsors, and clients.

  • Critical Rule: Project managers must communicate potential project risks and problems to executive management early to preserve corrective options.

Project Management Software & Tools

• Software Tool Options

  • Microsoft Project: Full-featured, commercial software application holding dominant market share.

  • GanttProject: Free, open-source desktop project management software.

  • Gantter: Free cloud-based project management utility.

  • Apptivo & Smartsheet: Paid, web-based enterprise project management platforms.

• Multi-View System Interfaces

  • Gantt Chart View: Tracks timeline progress across hierarchical WBS levels.

  • PERT/Network View: Displays topological dependencies and highlights critical path chains in red.

  • Calendar View: Displays schedule commitments overlaid directly on conventional calendar days.

  • Practical Execution Scenario: On September 25th during a system investigation, parallel active tasks include Observing Operations (2 days), Conducting User Survey (3 days), Conducting Interviews (2 days), and Reviewing Documentation (1 day). The project manager must prioritize Conducting User Survey because it resides directly on the critical path leading to Step 4 Analysis.

Risk Management

• Five Core Steps in Risk Management

  1. Develop a Risk Management Plan

  • Review project scope, stakeholder requirements, budget, schedule, internal/external variables.

  • Formally define team roles, risk evaluation methodologies, risk categories, and emergency procedures.

  1. Identify the Risks

  • Comprehensive cataloging of potential operational, technical, financial, or environmental hazards.

  1. Analyze the Risks

  • Qualitative Risk Analysis: Evaluates risk by estimating probability of occurrence and severity of potential impact.

  • Quantitative Risk Analysis: Quantifies numerical impact in exact financial figures (dollars), lost days (time), scope reduction, or quality degradation metrics.

  1. Create a Risk Response Plan

  • Proactive formulation of specific action steps and contingency contingencies to mitigate identified risk events.

  1. Monitor Risks

  • Continuous ongoing tracking throughout the SDLC to reassess risk indicators and trigger response plans when necessary.

• Risk Matrix Visualization

  • Plotted on a two-axis grid comparing Risk Probability (horizontal axis, scale 0–10) versus Risk Impact (vertical axis, scale 0–10):

  • Low Impact / Low Probability (e.g., coordinates (1,1) - Green marker).

  • High Impact / Low Probability (e.g., coordinates (1,9) - Yellow marker).

  • Medium Impact / Medium Probability (e.g., coordinates (5,5) - Yellow marker).

  • Low Impact / High Probability (e.g., coordinates (9,1) - Yellow marker).

  • High Impact / High Probability (e.g., coordinates (9,9) - Red marker, requires immediate top-priority mitigation).

• Risk Management Software Functionality

  • Enforces date constraints, links dependent task chains, factors external dependencies, tracks real-time progress, and automatically flags overdue tasks.

Managing for Success and Reasons Projects Fail

• Business Alignment Issues

  • Every information system must provide a clear business solution to a tangible organizational problem or market opportunity. Alignment failures guarantee system rejection.

• Budget Issues & Cost Overrun Causes

  • Unrealistic, overly optimistic initial estimations.

  • Failure to establish accurate financial forecasts.

  • Poor progress monitoring and ignoring early warning signs.

  • Unforeseen schedule delays and technical complications.

  • Human resource inefficiencies or staffing shortages.

• Schedule Issues & Timetable Slippage Causes

  • Failure to identify task dependencies during initial WBS design.

  • Confusing effort (person-hours spent) with progress (deliverables completed).

  • Inadequate monitoring and control mechanisms.

  • Interpersonal friction and personality conflicts within the project team.

  • High turnover rates among key technical personnel.