Chapter 3: Software Project Management

What is a Project?

Definition

  • Project: “A project is a problem scheduled for solution.”

Causes

  • Projects arise to solve problems that need structured effort and time.

Goals / Objectives

  • Emphasize that correct problem definition is essential to project success.

Importance

  • Shows failure to define the problem properly often causes project trouble.

Procedures

  • Not applicable to this topic

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • A clear problem statement guides planning and execution; unclear definitions cause failure.

Examples

  • Not specified in notes

Key Takeaways

  • Projects solve problems within a schedule.
  • Defining the problem correctly is critical.

Project Management (Software)

Definition

  • Software Project Management: An umbrella activity in software engineering that plans, monitors and controls people, processes and events as software evolves from concept to operational implementation.

Causes

  • Need to coordinate people, processes and events across software creation and support.

Goals / Objectives

  • Plan, monitor and control the software development lifecycle from definition through support.

Importance

  • Project management begins before technical work and continues through definition, development and support phases; it ensures coherence and delivery.

Procedures

  • Management involves:
    • Planning
    • Monitoring
    • Control of people, process and events

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • Proper project management helps align resources, schedule and quality across software evolution.

Examples

  • Not specified in notes

Key Takeaways

  • Project management coordinates the whole software lifecycle.
  • It is active from pre-technical planning through maintenance.

Why Companies Use Project Management

Definition

  • Reasons organizations adopt formal project management practices.

Causes

  • Organizational need to deliver projects reliably and communicate with customers.

Goals / Objectives

  • Handle projects effectively; define scope with customer; plan resources; estimate costs; schedule activities; allocate resources; assess risks; lead teams and communicate.

Importance

  • Ensures alignment between customer expectations and internal execution; prepares for contingencies and resource needs.

Procedures

  • Typical company PM activities listed:
    • Define project and agree with customer
    • Plan and assess resource needs
    • Estimate project cost and make proposals
    • Plan & schedule activities
    • Allocate the right resource at the right time
    • Assess risk and failure points and make backup plans
    • Lead project team and communicate effectively

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • Better resource use, clearer customer agreement, risk mitigation and improved team leadership.

Examples

  • Not specified in notes

Key Takeaways

  • Companies use PM to plan, estimate, allocate and mitigate risk.
  • Good leadership and communication are part of effective PM.

Tasks of Software Project Management

Definition

  • The main responsibilities and activities a project manager performs.

Causes

  • Need to deliver software on time, on budget and meeting quality.

Goals / Objectives

  • Summarize principal manager tasks and management activities.

Importance

  • Clarifies role expectations for IT project managers and management teams.

Procedures

  • Main responsibilities (as shown in notes/figure): supervise, planning, schedule, monitor progress.
  • Management activities listed explicitly:
    • Proposal writing
    • Project planning and scheduling
    • Project costing
    • Project monitoring and reviews
    • Personnel selection and evaluation
    • Report writing and presentation

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • These tasks, when performed, support controlled project delivery and stakeholder communication.

Examples

  • Not specified in notes

Key Takeaways

  • Project managers supervise planning, scheduling and monitoring.
  • Core management activities include proposal, planning, costing, monitoring, staffing and reporting.

Proposal Writing

Definition

  • Activity of preparing a formal project proposal for stakeholders or clients.

Causes

  • Need to define objectives, cost, schedule and execution approach before project approval.

Goals / Objectives

  • Describe objectives, cost, how to carry out the project, and schedule.

Importance

  • Proposal forms basis for client agreement and project approval.

Procedures

  • Proposal components (from notes figure):
    • Objectives
    • Cost
    • How to carry out
    • Schedule

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • A clear proposal aligns expectations and enables resource/cost planning.

Examples

  • Not specified in notes

Key Takeaways

  • Proposals capture objectives, costs and schedules for client agreement.
  • They are the starting document for project planning.

Project Planning

Definition

  • The activity of breaking down work, scheduling tasks and defining deliverables and milestones.

Causes

  • Need to organize work, assign staff and set measurable milestones.

Goals / Objectives

  • Produce activities list, project plan, milestones and deliverables such as preliminary investigation report, requirement specification, design specification, prototype.

Importance

  • Planning provides structure and timelines, enabling predictable execution.

Procedures

  • Planning elements and tools in notes:
    • Work breakdown (Work Breakdown Chart)
    • Activity dependencies
    • Project scheduling (Gantt Chart, PERT Chart)
    • Staff allocations
    • Gantt chart examples and task scheduling (Microsoft Project example)
    • Project Plan with stage exits, QA plan, in-stage assessment, test plans, acceptance test plan and final requirements specification

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • Good planning clarifies tasks, timings and responsibilities and supports monitoring.

Examples

  • Gantt Chart (multiple detailed examples in notes)
  • PERT Chart shown as planning tool
  • Example Gantt table with tasks like conduct interviews, administer questionnaires, introduce prototype, prepare/present proposal

Key Takeaways

  • Project planning uses WBS, activity dependencies and Gantt/PERT charts.
  • Plans list deliverables and define stage exits and assessments.

Project Scheduling (Gantt & PERT)

Definition

  • Scheduling is mapping tasks across time using charts like Gantt and PERT.

Causes

  • Need to visualize task durations, dependencies and staffing over calendar time.

Goals / Objectives

  • Show task durations, resources, milestones and dependencies across calendar weeks or months.

Importance

  • Helps track progress, allocate staff and identify schedule conflicts.

Procedures

  • Tools and artifacts shown in notes:
    • Gantt Chart with task durations, resource names and calendar dates
    • PERT Chart for dependency and critical path analysis
    • Staff allocation summaries
    • Example Gantt tables with weekly columns and task rows

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • Visual schedules improve clarity of who does what and when; facilitate monitoring.

Examples

  • Microsoft Project Gantt example (detailed table rows with tasks and durations)
  • Gantt Chart listing stages: Planning Stage, Requirements Definition Stage, test plans and stage exits

Key Takeaways

  • Use Gantt for time/resource view and PERT for dependencies.
  • Scheduling is central to planning and monitoring.

Project Costing

Definition

  • Estimating the monetary resources required for hardware, software and people.

Causes

  • Need to budget and evaluate project feasibility and ROI.

Goals / Objectives

  • Estimate resources and perform cost-benefit analysis.

Importance

  • Determines project affordability and supports proposals.

Procedures

  • Costing steps and techniques shown:
    • Estimate resources: hardware, software, people
    • Cost-benefit analysis techniques: Payback Period, Return on Investment (ROI), Net Present Value (NPV)

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • Costing informs decision-making, proposals and funding requests.

Examples

  • Not specified in notes (techniques listed without numeric example)

Key Takeaways

  • Costing requires estimating hardware, software and people costs.
  • Apply payback, ROI and NPV to evaluate financial viability.

Project Monitoring

Definition

  • Activity of comparing actual progress versus planned progress and taking corrective actions.

Causes

  • Projects deviate from plan due to delays, budget changes or quality issues.

Goals / Objectives

  • Detect deviations in time, cost and quality and apply corrective action to realign project.

Importance

  • Monitoring prevents unnoticed drift and supports timely corrective measures.

Procedures

  • Monitoring concepts and steps from notes:
    • Track the triple constraints: time, cost, quality
    • Compare actual project progress vs planned project progress
    • Identify problems (behind schedule, over budget, failing quality)
    • Apply corrective actions (add staff, reassign tasks, use overtime, encourage staff)
    • Conduct formal vs informal reviews

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • Enables corrective intervention to restore schedule, budget or quality targets.

Examples

  • Not specified in notes

Key Takeaways

  • Monitor time, cost and quality; compare actual vs planned.
  • Use corrective actions and reviews when problems appear.

Personnel Selection & Management

Definition

  • Selecting, organizing and motivating project team members.

Causes

  • Need for right skills, attitudes and communication ability to deliver project work.

Goals / Objectives

  • Select suitable staff; motivate and manage them; ensure appropriate team composition.

Importance

  • Right personnel and good management increase productivity and project success.

Procedures

  • Staff selection factors (from notes figures):
    • Application domain knowledge
    • Programming language experience
    • Attitude
    • Communication ability
    • Adaptability
  • Motivation and management factors:
    • Money, leadership, job satisfaction, thoughtful job design
    • Use Maslow’s Motivation Model to recognize needs from physiological up to self-actualization
  • Group working factors:
    • Group composition: balance of skills, experience, personalities (task-, interaction-, self-oriented)
    • Group cohesiveness: encourage group identity, team-building activities, treating members as responsible and trustworthy
    • Group communication: assess if members communicate effectively; improve communication (notes mention “How to improve group communication?” but details not specified)
    • Group organization: ensure role satisfaction and right job assignment

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • Proper selection, motivation and organization improve cohesiveness, communication and team effectiveness.

Examples

  • Maslow’s hierarchy diagram used to discuss motivation levels.

Key Takeaways

  • Select people for domain skill, language experience and attitude.
  • Promote cohesiveness via identity, team-building and trust.
  • Organize roles so everyone feels valued.

Group Composition

Definition

  • Makeup of the team in terms of skills, experience and personalities.

Causes

  • Project requirements and tasks determine needed team roles.

Goals / Objectives

  • Ensure the team has the right balance of task-, interaction- and self-oriented members.

Importance

  • Proper composition enables task completion and good team dynamics.

Procedures

  • Assess team balance: skills, experience, personalities.

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • Balanced composition supports performance and reduces conflict.

Examples

  • Not specified in notes

Key Takeaways

  • Check team for appropriate skills and personalities.
  • Balance task focus with interpersonal strengths.

Group Cohesiveness

Definition

  • Degree to which the group thinks of itself as a team rather than a collection of individuals.

Causes

  • Shared identity, trust and meaningful team activities promote cohesiveness.

Goals / Objectives

  • Create a sense of team identity and shared responsibility.

Importance

  • Cohesive teams collaborate better and stay productive.

Procedures

  • How to promote cohesiveness (from notes):
    1. Establish group identity
    2. Team building activities
    3. Treat members as responsible & trustworthy

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • Better teamwork, higher morale and improved outcomes.

Examples

  • Not specified in notes

Key Takeaways

  • Build identity and trust to promote cohesiveness.
  • Team-building and responsibility assignment help.

Group Communication

Definition

  • The effectiveness of information exchange among team members.

Causes

  • Team structure, tools and culture determine communication quality.

Goals / Objectives

  • Ensure members communicate effectively to coordinate work and resolve issues.

Importance

  • Poor communication leads to misunderstandings and delays.

Procedures

  • Notes ask “How to improve group communication?” but do not list explicit steps; topic is raised for discussion.

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • Effective communication increases coordination and reduces rework.

Examples

  • Not specified in notes

Key Takeaways

  • Communication quality is a key factor in group working.
  • The chapter raises this as an issue to address (explicit improvement methods not listed).

Group Organization

Definition

  • The team’s structure and role assignments.

Causes

  • Need to assign tasks, clarify roles and ensure member satisfaction.

Goals / Objectives

  • Organize team so everyone feels valued and satisfied with their role; assign right jobs to right people.

Importance

  • Proper organization reduces role conflict and increases efficiency.

Procedures

  • Evaluate role-fit and reassign as needed to ensure satisfaction (notes ask “Did you assign the right job to the right people?”).

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • Better organization leads to higher motivation and productivity.

Examples

  • Not specified in notes

Key Takeaways

  • Assign roles that match skills and preferences.
  • Ensure organization supports team morale.

Report Writing and Presentation

Definition

  • Documenting and presenting project status, findings and deliverables.

Causes

  • Need to communicate progress and results to stakeholders.

Goals / Objectives

  • Produce project documents and present the project clearly.

Importance

  • Reporting records decisions, progress and supports stakeholder communication.

Procedures

  • Report on the project through documentation and presentations (notes list “Document” and “Presentation”).

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • Good reports improve transparency and stakeholder trust.

Examples

  • Not specified in notes

Key Takeaways

  • Regular documentation and presentations are part of PM responsibilities.
  • Reports support monitoring and reviews.

Can Good Project Management Guarantee Project Success?

Definition

  • The question of whether management alone can ensure success.

Causes

  • Projects can fail for many reasons beyond management control.

Goals / Objectives

  • Clarify limits of management and highlight the harm of bad management.

Importance

  • Sets realistic expectations: management helps but does not guarantee success.

Procedures

  • Not applicable

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • Good management reduces risk but does not ensure success; bad management usually results in failure.

Examples / Notes

  • The software may be delivered late, cost more and fail to meet requirements if management is poor.

Key Takeaways

  • Good management cannot guarantee success, but bad management often causes failure.
  • Management reduces risk but is not a certainty.

Quote (Teamwork)

Definition

  • Inspirational quote included in notes.

Causes

  • Not applicable

Goals / Objectives

  • Emphasize stages of teamwork: coming together, keeping together, working together.

Importance

  • Highlights the value of sustained collaboration.

Procedures

  • Not applicable

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • Reinforces chapter emphasis on teamwork and cohesion.

Examples

  • “Coming together is a beginning, Keeping together is progress & Working together is success.” — Henry Ford

Key Takeaways

  • Teamwork requires assembly, cohesion and collaboration to succeed.

Exercise: Create a Gantt Chart

Definition

  • Practical assignment to build a schedule visualization.

Causes

  • Illustrate project scheduling skills using given activity data.

Goals / Objectives

  • Create a Gantt chart assuming project starts in July.

Importance

  • Applies planning and scheduling concepts from the chapter.

Procedures

  • Use the provided activity table to place tasks on a July+ timeline.

  • Activity data (preserved exactly):

    • Activity A: Duration 1/2 month; Predecessor: None; Overlap: None
    • Activity B: Duration 1 month; Predecessor: A; Overlap: None
    • Activity C: Duration 2 months; Predecessor: B; Overlap: 1/4 month
    • Activity D: Duration 1 month; Predecessor: B; Overlap: None
    • Activity E: Duration 1/2 month; Predecessor: C, D; Overlap: None
  • Assume project start: July (as stated).

Advantages & Disadvantages

  • Not applicable to this topic

Impact / Effect

  • Students must compute start/end dates and overlaps and draw a Gantt table similar to examples earlier in the chapter.

Examples

  • The notes include blank calendar tables across July–October for plotting the Gantt chart.

Key Takeaways

  • Use predecessor and overlap rules to place each activity on the timeline starting in July.
  • Translate fractional-month durations to calendar spans when drawing the chart.

Final Key Points Across the Chapter

Definition

  • Summary of core project management concepts covered.

Causes

  • Not specified in notes

Goals / Objectives

  • Reinforce tasks, planning tools, costing, monitoring and people management as central PM activities.

Importance

  • Effective project management organizes scope, schedule, cost and people to reduce failure risk.

Procedures

  • Use proposal writing, planning (WBS, Gantt, PERT), costing (ROI/NPV), monitoring (compare actual vs planned), staffing (selection & motivation), reporting and team-building methods.

Advantages & Disadvantages

  • Not specified in notes

Impact / Effect

  • Good PM reduces the chance of delays, budget overruns and quality failures but cannot guarantee success.

Examples

  • Multiple Gantt chart and scheduling examples; Maslow’s motivation model used for staff motivation.

Key Takeaways

  • Plan thoroughly, monitor the triple constraints (time, cost, quality), select and motivate the right people, and use scheduling tools (Gantt/PERT) to manage work.
  • Team composition, communication and cohesion are as important as technical planning.