Software Testing & Project Management

Module 5 — Exam Preparation Guide

Project Organization | WBS | Scheduling | PERT | CPM | Gantt | Milestone Charts

Exam Section Questions Marks Each Total

Section A 10 Questions 2 Marks 20 Marks
Section B 5 Questions 5–6 Marks 25–30 Marks
Section C 2 Questions 15 Marks 30 Marks

📌 TIP Module 5 is diagram-heavy — PERT, CPM, Gantt, and Milestone charts. In 15-mark
answers, describe the diagram AND its steps/formula. For 2-markers, one-line
definitions with a key characteristic win marks.
 SECTION A — 2 Mark Questions
Short Answer | ~3–5 lines per answer

Definitions & Core Concepts

Q1. What is a Work Breakdown Structure (WBS)?
A WBS is a hierarchical decomposition of a project into smaller, manageable components called
work packages. It serves as the foundation for project planning, scheduling, cost estimation, and
resource allocation.
Key feature: Each level breaks the project down further — from project title → major phases → sub-
deliverables → tasks.
Q2. What is a Work Package?
A Work Package is the lowest level element in a WBS. It is the most detailed task unit that can be
scheduled, estimated, cost-controlled, and assigned to a specific team member or group.
Example: 'Implement HTML layout' under the Front-end Development work package.
Q3. Define 'Critical Path' in project scheduling.
The Critical Path is the longest sequence of dependent tasks that determines the minimum duration
required to complete a project. Any delay on a critical path task directly delays the entire project.
Slack/Float on the critical path = 0.
Q4. What is Slack (Float) in project scheduling?
Slack (or Float) is the amount of time a task can be delayed without affecting the overall project
completion date. Tasks on the critical path have zero slack.
Formula: Slack = Latest Start Time − Earliest Start Time.
Q5. What is a Milestone in project management?
A Milestone is a significant event or achievement in the project lifecycle used as a key progress
checkpoint. Milestones do not consume time or resources — they mark the completion of a phase
or deliverable.
Examples: Design completion, first prototype release, final product launch.
Q6. Define 'Dependency' in project scheduling.
A Dependency is the relationship between tasks where one task depends on another's completion
or start. The most common type is Finish-to-Start (FS): Task B cannot begin until Task A is finished.
Example: Testing can only start after coding is completed.
Q7. What is a Gantt Chart?
A Gantt Chart is a visual project management timeline that uses horizontal color-coded bars to
represent tasks along a time axis. It shows task start/end dates, dependencies, milestones, and
progress tracking.
Introduced by Henry Gantt in the early 1900s.
Q8. What is PERT?
PERT (Program Evaluation and Review Technique) is a network-based project scheduling
technique that estimates task durations using three values: Optimistic (O), Most Likely (M), and
Pessimistic (P).
Formula: Expected Time = (O + 4M + P) / 6.
Q9. What is CPM (Critical Path Method)?
CPM is a project scheduling technique that identifies the critical path — the longest chain of
dependent tasks — to determine the project's minimum completion time. It uses fixed time
estimates and focuses on task sequencing.
Best for: Complex projects with clear, interdependent tasks.
Q10. What is a Milestone Chart?
A Milestone Chart is a high-level chart that tracks only the major project events (milestones) rather
than individual tasks. It provides a quick overview of key progress points for stakeholders and
project managers.
Disadvantage: Does not show detailed task-level tracking.
Q11. Define 'Lead Time' and 'Lag Time' in scheduling.
Lead Time: The amount of time a successor task can start before its predecessor task finishes
(overlap allowed).
Lag Time: A deliberate delay between the finish of one task and the start of the next dependent task
(waiting period).
Q12. What is 'Fast Tracking' in project management?
Fast Tracking is a schedule compression technique where tasks that were originally planned in
sequence are performed in parallel to reduce the overall project duration.
Trade-off: Increases risk and may require rework if parallel tasks are interdependent.
Q13. What is 'Crashing' in project scheduling?
Crashing is a schedule compression technique where additional resources (people, equipment,
money) are added to critical path tasks to shorten the project duration.
Trade-off: Reduces time but significantly increases project cost.
Q14. Differentiate between Product and Project (any 2 points).
Product: Long-term, continuous existence with ongoing updates and market evolution (e.g.,
Microsoft Word).
Project: Temporary, has a defined start and end, delivers a specific outcome within
scope/time/budget (e.g., developing a new Word feature).
Q15. What is the difference between PERT and CPM?
PERT: Event-oriented, uses probabilistic time estimates (O/M/P), best for uncertain/research-heavy
projects.
CPM: Activity-oriented, uses fixed time estimates, links activity times to costs, best for projects with
predictable task durations.
Q16. What are Project Elements? Name any four.
Project Elements are the fundamental components that ensure a project is aligned with objectives,
delivered on time, and within budget.
Four key elements: (1) Scope — what is included/excluded. (2) Resources — human, financial,
physical assets. (3) Time/Schedule — timeline and milestones. (4) Risk — potential challenges and
uncertainties.
Q17. What is Resource Leveling?
Resource Leveling is a scheduling technique that adjusts the project schedule to balance the
workload of team members and prevent overloading or underutilization of resources.
It may extend the project duration to ensure no resource is over-committed.
Q18. What is a Bar Chart in project management?
A Bar Chart is a simple visual tool that shows tasks as horizontal bars representing their duration
along a timeline. Unlike a Gantt chart, it does not show task dependencies or relationships.
Best for: Small projects with fixed task durations.
 SECTION B — 5 Mark Questions
Medium Answer | ~10–15 lines | Structure: Definition → Points → Example

Topic: WBS & Project Elements

Q1. Explain the Work Breakdown Structure (WBS) — its levels, steps to create, and benefits.
Definition: WBS is a hierarchical decomposition of a project into smaller, manageable work
packages.
Levels of WBS:
Level 1 — Project Title (e.g., 'Software Development Project')
Level 2 — Major Phases (e.g., Design, Development, Testing, Deployment)
Level 3 — Sub-Deliverables (e.g., UI/UX Design, Front-end Dev, Unit Testing)
Level 4 — Tasks (e.g., Draw wireframes, Write API code, Set up DB schema)
Steps to Create WBS:
1. Define project scope and objectives.
2. Identify major phases or deliverables.
3. Decompose deliverables into work packages.
4. Break work packages into specific tasks.
5. Assign responsibility and estimate resources.
6. Review for completeness and create a WBS Dictionary.
Benefits: Clarity, better resource allocation, accurate time/cost estimation, risk visibility, clear
accountability.
Example: An e-commerce app WBS: Level 2 = Design/Dev/Test/Deploy → Level 3 = UI
Design/Backend Dev/UAT → Level 4 = Create wireframes, Set up DB, Write test cases.
Q2. Describe the different types of WBS.
1. Deliverable-Based WBS (Product-Oriented) — organized around final outputs/products. Ensures
all required results align with customer expectations.
2. Phase-Based WBS (Process-Oriented) — structured around lifecycle phases (Planning, Design,
Implementation, Testing). Tracks progress through sequential stages.
3. Organizational-Based WBS — work divided by department/team (Marketing, Finance,
Engineering). Clarifies responsibility across functional units.
4. Hybrid WBS — combines deliverable-based and phase-based. Provides comprehensive view for
complex projects.
5. Cost-Based WBS — organized by cost/budget. Supports financial control and budgeting for cost-
sensitive projects.
6. Time-Based WBS — divided by timeframes or milestones. Useful for time-sensitive, deadline-
driven projects.
7. Function-Based WBS — organized by project functions (Design, Development, Testing).
Common in IT/software projects.
Key: Choose type based on project nature, industry, and primary management focus (time, cost,
deliverables, or team structure).
Q3. Explain Function, Activity, and Task in project management with examples.
These represent three levels of work granularity in a project:
1. Function — High-level, broad area of work aligned with project objectives or phases.
Characteristics: Broad, covers overall process/role, represents major departments.
 Example: 'Design' function — covers all UI, UX, database, and architecture design efforts.
2. Activity — Specific, action-oriented process within a function. Measurable and trackable.
Characteristics: Mid-level, more specific than function, can be broken into tasks.
Example: 'Create wireframes' — specific action within the Design function.
3. Task — Most granular unit. Specific, assignable, with defined deadlines and outcomes.
Characteristics: Lowest level, actionable, assigned to one person/small group.
Example: 'Draw homepage layout' — specific task within the 'Create wireframes' activity.
Relationship: Function → Activity → Task (from broad to specific).
In WBS: Function = Level 2, Activity = Level 3, Task = Level 4.

Topic: Project Life Cycle vs Product Life Cycle

Q4. Compare Product Life Cycle (PLC) and Project Life Cycle (PjLC).
Product Life Cycle (PLC) — the stages a product goes through from market introduction to decline.
Stages: Introduction → Growth → Maturity → Decline.
• Introduction: High investment, low sales, product is new to market.
• Growth: Increasing sales, competitors enter, profitability improves.
• Maturity: Sales peak and stabilize; price wars; focus on differentiation.
• Decline: Falling demand; product discontinued or updated.
Example: Windows OS — Dev → Windows 95 (Intro) → XP (Growth) → Win10 (Maturity) → Win7
discontinued (Decline).
Project Life Cycle (PjLC) — the process of managing a project from start to finish.
Stages: Initiation → Planning → Execution → Closure.
• Temporary and goal-oriented; ends when project objectives are achieved.
Example: Windows 11 development — feasibility study → feature planning → build & test → Oct
2021 launch.
Key Distinction: A product is long-term and market-driven; a project is temporary and objective-
driven. A product may involve many projects over its lifetime.

Topic: Personnel Organization

Q5. Describe the different ways to organize personnel in a software project.
1. Functional Organization — teams grouped by skill/expertise (Dev team, Testing team, Design
team).
Best for: Large organizations with multiple projects. Advantage: Specialized expertise.
Disadvantage: Communication gaps between teams.
2. Project-Based (Dedicated) — dedicated team assigned to one project start to finish.
Best for: Short-term, intensive projects. Advantage: High focus. Disadvantage: Resource
underutilization.
3. Matrix Organization — hybrid; team members report to both functional manager AND project
manager.
Best for: Companies managing multiple projects. Advantage: Efficient resource sharing.
Disadvantage: Dual reporting conflicts.
4. Agile Team Organization — Scrum/Kanban; roles: Product Owner, Scrum Master, Dev Team.
Best for: Fast-paced, iterative development. Advantage: Flexibility. Disadvantage: Requires Agile
expertise.
 5. Component-Based — teams organized by software component (Frontend, Backend, Security).
Best for: Large, complex systems. Advantage: Deep specialization. Disadvantage: Siloed teams.
6. Decentralized/Open-Source — self-organizing; work contributed based on expertise/interest.
Best for: Open-source projects. Advantage: Global collaboration. Disadvantage: Hard to enforce
deadlines.

Topic: Scheduling Techniques

Q6. Explain Gantt Charts — components, uses, advantages, and disadvantages.
Definition: A Gantt Chart is a visual timeline using horizontal color-coded bars to represent tasks
across a time axis. Introduced by Henry Gantt in the early 1900s.
Components of a Gantt Chart:
1. Task List — all project tasks listed vertically.
2. Timeline — horizontal time axis (days/weeks/months).
3. Dateline — current date indicator for tracking.
4. Bars — horizontal bars showing task duration.
5. Milestones — key events marked as points on the chart.
6. Dependencies — lines/arrows showing task relationships.
7. Progress — visual fill of bars showing % completion.
8. Resource Assigned — who is responsible for each task.
Uses: Resource management, project planning, scheduling, and tracking.
Advantages: Easy to understand, shows dependencies and progress, visual and intuitive.
Disadvantages: Becomes complex for large projects; updating frequently is time-consuming.
Example: Tracking UI Design → Coding → Testing → Deployment phases of a software project.
Q7. Explain CPM (Critical Path Method) — how it works, advantages, and disadvantages.
Definition: CPM is a scheduling technique that identifies the critical path — the longest sequence of
dependent tasks that determines the minimum project duration.
How CPM Works:
1. Task Definition: Break project into individual tasks, activities, and dependencies.
2. Estimate Durations: Assign fixed time estimates to each task.
3. Network Diagram: Create a visual map of task sequence and dependencies.
4. Critical Path Calculation: Calculate Earliest Start (ES), Earliest Finish (EF), Latest Start (LS),
Latest Finish (LF) for each task.
5. Identify Zero-Float Tasks: Tasks with zero slack form the critical path.
6. Monitor & Control: Track progress on critical tasks; take corrective action for delays.
Key Concepts: Slack = LS − ES = 0 on critical path; any delay on critical path = project delay.
Advantages: Identifies tasks that directly impact deadlines; enables better resource allocation.
Disadvantages: Doesn't handle time uncertainty; requires detailed task-level data.
Example: In a software project — coding must finish before testing starts (Finish-to-Start
dependency).
Q8. Explain PERT — how it works, its formula, benefits, and comparison with CPM.
Definition: PERT (Program Evaluation and Review Technique) is a network-based technique that
plans and schedules tasks using probabilistic time estimates.
How PERT Works:
1. Create Network Diagram: Map all activities, dependencies, and their sequence.
2. Estimate Task Durations using three values:
 O = Optimistic (best case), M = Most Likely, P = Pessimistic (worst case).
3. Calculate Expected Duration: E = (O + 4M + P) / 6
4. Identify the Critical Path: Longest sequence of activities; delays here = project delay.
Benefits of PERT:
• Improved Accuracy — probabilistic estimates reflect realistic scenarios.
• Better Risk Management — considers all time scenarios upfront.
• Clear Communication — network diagram makes plans visible to stakeholders.
PERT vs CPM:
• PERT: Event-oriented, uncertain durations, not linked to cost. Best for R&D/research.
• CPM: Activity-oriented, fixed durations, linked to cost. Best for construction/IT projects.
Example: Estimating software module development time when requirements are not fully defined.
 SECTION C — 15 Mark Questions
Long Answer | ~35–45 lines | Structure: Intro → Body (6–8 points) → Table/Diagram description →
Conclusion

📌 15-mark structure: Introduction (2) + Numbered points with explanation (10–11) +

FORMULA Comparison table or diagram description (2) + Conclusion (1). Minimum 6 well-
developed points.

Q1. Explain Project Scheduling in detail — objectives, terminology, and techniques.

Introduction:
Project Scheduling is a critical aspect of Software Project Management that ensures tasks are
planned, assigned, and executed within a defined timeframe. It aligns work with available resources
and business deadlines.
What is a Project Schedule?
A Project Schedule is a timeline that defines: Tasks (activities to complete), Dependencies (task
relationships), Milestones (key checkpoints), Resources (people/tools/materials), and Deadlines
(start and end dates).
Scheduling Objectives:
1. Ensure Timely Completion — use CPM and PERT to identify key tasks; deliver within the
planned timeframe.
2. Optimize Resource Utilization — use Resource Leveling and Gantt Charts to balance workloads
efficiently.
3. Manage Task Dependencies — use Dependency Mapping (Finish-to-Start, Start-to-Start, etc.) to
prevent bottlenecks.
4. Meet Budget Constraints — align schedule with financial limits; delays increase resource costs.
5. Accommodate Changes & Risks — build buffer time; maintain risk management plans for
flexibility.
Key Scheduling Terminology:
• Task: Specific work unit in the project.
• Milestone: Significant project event/checkpoint.
• Dependency: Relationship between tasks (e.g., B starts after A finishes).
• Critical Path: Longest dependent task chain; determines minimum project duration.
• Slack/Float: Time a task can slip without delaying the project.
• Lead Time: Time successor task can start before predecessor finishes.
• Lag Time: Deliberate delay between tasks.
• Fast Tracking: Running tasks in parallel to save time (more risk).
• Crashing: Adding resources to critical tasks to shorten duration (more cost).
• Resource Leveling: Adjusting schedule to balance team workload.
• Baseline Schedule: Original approved schedule used for comparison.
Scheduling Techniques:
• Gantt Chart — visual horizontal bar timeline; easy to track; best for small-medium projects.
• CPM — identifies critical path with fixed durations; best for interdependent task projects.
• PERT — probabilistic estimates using O/M/P formula; best for uncertain/high-risk projects.
• Bar Chart — simple task duration bars; no dependencies shown; best for small projects.
• Milestone Chart — tracks only major events; good for stakeholder communication.
 • Agile Scheduling — iterative sprints and backlogs; best for fast-changing requirements.
Conclusion:
Effective project scheduling is the backbone of successful software delivery. By choosing the right
technique — Gantt for visibility, CPM for control, PERT for uncertainty — project managers can
minimize delays, optimize resources, and meet stakeholder expectations.

Q2. Explain WBS in detail — purpose, levels, types, steps, and benefits.
Introduction:
A Work Breakdown Structure (WBS) is a hierarchical decomposition of a project into smaller,
manageable components. It is the foundation for planning, scheduling, cost estimation, and
resource allocation in any software project.
Key Features of WBS:
• Hierarchical Structure: Organized from broadest (project) to most specific (tasks).
• Work Packages: The lowest-level units — schedulable, estimable, and assignable.
• Clear Deliverables: Each level produces a tangible/measurable output.
• Measurable Outcomes: Progress can be tracked per work package.
Levels of WBS (with example: E-commerce Web App):
Level 1 — Project Title: 'Development of E-commerce Application'
Level 2 — Major Phases: Design | Development | Testing | Deployment
Level 3 — Sub-Deliverables: UI/UX Design, Front-end Dev, Unit Testing, Production Setup
Level 4 — Tasks: 'Create wireframes', 'Implement HTML layout', 'Write unit test cases'
Steps to Create WBS:
1. Define Project Scope — identify overall objective and deliverables.
2. Identify Major Phases — create Level 2 of the WBS.
3. Decompose into Work Packages — Level 3 sub-deliverables per phase.
4. Break into Tasks — specific, assignable Level 4 items.
5. Assign Responsibility & Estimate Resources — person, time, cost per task.
6. Review & Refine — check completeness, feasibility, and coverage.
7. Create WBS Dictionary — additional detail: descriptions, timelines, responsible parties.
Types of WBS:
1. Deliverable-Based — organized around outputs (product-focused).
2. Phase-Based — organized around lifecycle stages (process-focused).
3. Organizational-Based — organized by team/department.
4. Hybrid — combines deliverable + phase approaches.
5. Cost-Based — organized around budgets/cost centers.
6. Time-Based — organized around milestones/timeframes.
7. Function-Based — organized around project functions (Design, Dev, Test).
Benefits of WBS:
1. Clarity & Focus — well-defined tasks for everyone.
2. Better Resource Allocation — resources mapped to specific work packages.
3. Accurate Time & Cost Estimation — granular breakdown enables precise budgeting.
4. Enhanced Risk Management — risks identified at work-package level.
5. Improved Monitoring & Control — baseline for tracking progress and correcting deviations.
6. Clear Accountability — every task has an owner.
Conclusion:
 WBS transforms a complex project into a structured, manageable framework. Without it, projects
risk scope creep, unclear responsibilities, and uncontrolled costs. It is the single most important
planning tool in software project management.

Q3. Explain PERT and CPM in detail. Compare them and explain their use in software
projects.
Introduction:
PERT and CPM are two of the most important network-based scheduling techniques in Software
Project Management. Both use network diagrams to represent tasks and dependencies, but they
differ in their approach to time estimation and project type.
PERT — Program Evaluation and Review Technique:
Definition: A scheduling method that uses probabilistic time estimates to plan and schedule tasks in
projects with high uncertainty.
How PERT Works:
1. Create a Network Diagram: Map all activities, dependencies, and their required sequence.
2. Estimate Task Durations — THREE estimates per task:
O = Optimistic (best-case minimum time)
M = Most Likely (most realistic duration)
P = Pessimistic (worst-case maximum time)
3. Calculate Expected Duration: E = (O + 4M + P) / 6
4. Identify the Critical Path: Longest sequence of activities in the network diagram.
5. Analyze Variance: Helps quantify schedule risk.
PERT Network Diagram Elements: Nodes = events/milestones; Arrows = activities/tasks; Numbers
on arrows = expected duration.
Benefits: Realistic estimates, better risk management, clear stakeholder communication.
Disadvantages: Requires continuous monitoring; three estimates per task is time-consuming.
Best for: R&D projects, software development with undefined requirements, high-uncertainty
projects.
CPM — Critical Path Method:
Definition: A scheduling technique that uses fixed time estimates and a network diagram to identify
the critical path — the sequence of tasks that determines minimum project duration.
How CPM Works:
1. List all tasks and their dependencies.
2. Assign fixed duration estimates to each task.
3. Draw a Network Diagram (Activity-on-Node or Activity-on-Arrow).
4. Calculate for each task: ES (Earliest Start), EF (Earliest Finish), LS (Latest Start), LF (Latest
Finish).
5. Compute Slack = LS − ES. Tasks with Slack = 0 form the Critical Path.
6. Monitor critical tasks; any delay delays the whole project.
Benefits: Identifies tasks that control project deadline; enables resource optimization.
Disadvantages: Does not handle uncertainty; assumes fixed, deterministic durations.
Best for: Construction, IT projects, manufacturing — any project with clear, predictable task
durations.
PERT vs CPM Comparison:
• Orientation: PERT = Event-oriented | CPM = Activity-oriented.
• Time Estimates: PERT = Probabilistic (O/M/P) | CPM = Deterministic (single fixed value).
• Cost Linkage: PERT = Not linked to cost | CPM = Activity times linked to costs.
 • Best For: PERT = Uncertain, research-heavy projects | CPM = Predictable, interdependent
projects.
• Uncertainty Handling: PERT = Handles well | CPM = Does not handle well.
• Usage: PERT = NASA/defense projects | CPM = Software dev, construction.
Conclusion:
PERT and CPM are complementary tools. In practice, both are often used together — PERT for
realistic duration estimation and risk awareness, CPM for critical path identification and resource
control. Understanding both is essential for managing complex software projects.

Q4. Explain project scheduling charts — Gantt Chart, Bar Chart, and Milestone Chart in
detail.
Introduction:
Scheduling charts are visual tools that help project managers plan, communicate, and track project
progress. The three main bar-based charts are the Gantt Chart, Bar Chart, and Milestone Chart.
1. Gantt Chart:
Definition: A visual project management timeline using horizontal color-coded bars to represent
tasks across a time axis. Developed by Henry Gantt in the early 1900s.
Components:
• Task List — all project tasks listed vertically on the left.
• Timeline — horizontal time axis (days/weeks/months).
• Dateline — today's date indicator showing current position.
• Bars — horizontal bars representing task start and end dates.
• Milestones — diamond symbols marking key project events.
• Dependencies — arrows/lines showing task relationships.
• Progress — partially filled bars showing % completion.
• Resource Assigned — person/team responsible for each task.
Uses: Project planning, resource management, scheduling, and progress tracking.
Advantages: Easy to understand, visually clear, shows dependencies and progress.
Disadvantages: Complex for large projects; not efficient for projects with many dependencies.
Example: Tracking Design → Coding → Testing → Deployment for a mobile app.
2. Bar Chart:
Definition: A simplified visual tool that shows tasks as horizontal bars representing their duration
along a timeline. Unlike Gantt, it does NOT show dependencies or relationships.
Advantages: Easy to create and understand; good for small, simple projects.
Disadvantages: Cannot show task dependencies, relationships, or resource allocation.
Best For: Small IT projects with fixed, independent task durations.
Example: A short web maintenance project with 5 independent tasks.
3. Milestone Chart:
Definition: A high-level chart that tracks only major project events (milestones) rather than individual
tasks. Milestones are specific points in time, not duration.
Common Milestones: Project kick-off, design completion, first prototype release, beta testing, final
product launch.
Advantages: Provides clear overview of project progress; excellent for stakeholder communication.
Disadvantages: Does not provide detailed task-level information or resource tracking.
Best For: Executive-level reporting, stakeholder updates, high-level project tracking.
Example: Tracking the release stages of a software product: v1.0 Alpha → Beta → RC → Launch.
Comparison of All Three Charts:
 Gantt Chart — shows tasks + dependencies + progress → Detailed scheduling.
Bar Chart — shows tasks + duration only → Simple, small project tracking.
Milestone Chart — shows key events only → High-level executive tracking.
Conclusion:
The choice of chart depends on project complexity and audience. Gantt charts are the most
comprehensive for day-to-day management, Bar Charts for simple projects, and Milestone Charts
for stakeholder communication. Skilled project managers often use all three at different levels.

Q5. Explain the ways to organize personnel in Software Project Management. Which is most
effective?
Introduction:
Organizing personnel effectively is one of the most critical factors in software project success. The
right team structure defines reporting relationships, decision-making authority, communication flow,
and responsibility distribution.
1. Functional Organization:
Structure: Teams grouped by skill area — Development, Testing, Design.
Best for: Large organizations with multiple ongoing projects.
Advantage: Specialized expertise; clear roles; easy skill development.
Disadvantage: Communication silos between teams; inflexible for cross-functional work.
2. Project-Based (Dedicated) Organization:
Structure: One dedicated team works on a single project from start to finish.
Best for: Short-term, intensive projects requiring deep collaboration.
Advantage: High focus; fast decision-making; project-specific expertise.
Disadvantage: Resources may be underutilized; knowledge not shared across projects.
3. Matrix Organization (Hybrid):
Structure: Team members report to both a Functional Manager AND a Project Manager.
Best for: Companies managing multiple simultaneous projects.
Advantage: Efficient resource sharing; balances specialization and project focus; knowledge
sharing.
Disadvantage: Dual reporting creates confusion and potential conflicts between managers.
4. Agile Team Organization:
Structure: Scrum/Kanban-based; roles: Product Owner, Scrum Master, Development Team.
Best for: Startups, fast-paced environments with frequent requirement changes.
Advantage: High flexibility; rapid feedback cycles; encourages collaboration.
Disadvantage: Requires experienced Agile practitioners; hard to scale in large enterprises.
5. Component-Based Organization:
Structure: Teams organized by software component — Frontend, Backend, Security, Database.
Best for: Large, complex systems requiring deep technical specialization.
Advantage: Deep expertise in each domain; clear ownership of components.
Disadvantage: Risk of silos; dependencies between components can slow progress.
6. Decentralized/Open-Source Organization:
Structure: Self-organizing contributors based on expertise and interest; no central authority.
Best for: Open-source projects and highly innovative environments.
Advantage: Global collaboration; innovation; reduces dependency on one organization.
Disadvantage: Difficult to enforce deadlines; quality control and accountability challenges.
Most Effective Structure:
The Matrix Organization is widely considered most effective for professional software development
as it balances specialization with project focus and enables efficient resource use across multiple
projects simultaneously.
Conclusion:
No single structure fits all projects. The best approach depends on project size, duration,
complexity, and team maturity. Modern organizations often adopt hybrid structures combining Agile
teams within a Matrix framework for maximum flexibility and efficiency.
 Quick Revision — Key Facts & Comparisons

📌 PERT Expected Time E = (O + 4M + P) / 6 | O=Optimistic, M=Most Likely, P=Pessimistic

Formula

📌 Critical Sequence of tasks with Slack = 0. Any delay on critical path = project delay. Slack =
Path LS − ES.

⚡ Fast Fast Track = tasks in parallel (saves time, adds risk) | Crashing = add resources
Track vs (saves time, adds cost)
Crash

Scheduling Techniques — Quick Comparison

Technique Focus Dependencies? Time Estimates Best For
PERT Time & Yes O/M/P Uncertain, R&D
uncertainty (probabilistic) projects
CPM Critical path Yes Fixed Complex,
(deterministic) interdependent
tasks
Gantt Chart Task scheduling Yes Fixed durations Detailed task
& progress management
Bar Chart Task duration No Fixed durations Small, simple
projects
Milestone Chart Major events only No Not applicable High-level
tracking
Agile Iterative sprints Implicit Story Points Fast-changing
requirements

Personnel Organization — Summary

Structure Best For Key Advantage Key Challenge
Functional Large, specialized Domain expertise Communication silos
teams
Project-Based Short-term projects High focus & speed Resource
underutilization
Matrix Multiple concurrent Efficient resource use Dual reporting conflicts
projects
Agile Iterative, fast-changing Flexibility Requires Agile skills
projects
Component-Based Large complex Deep specialization Siloed teams
systems
Decentralized Open-source projects Global collaboration Accountability issues

WBS Levels — At a Glance

WBS Level Description Example
Level 1 Project Title / Goal E-commerce Web Application
Level 2 Major Phases / Deliverables Design | Development | Testing
| Deployment
Level 3 Sub-Deliverables / Work UI/UX Design | Front-end Dev |
Packages Unit Testing
Level 4 Tasks / Sub-Tasks Draw wireframes | Implement
HTML | Write test cases

Product vs Project & PLC vs PjLC — Quick Recap

Feature Product Project

Duration Long-term, continuous Temporary, fixed end

Objective Deliver market value Complete specific task
Lifecycle Intro → Growth → Maturity → Initiation → Planning →
Decline Execution → Closure
Management Product Manager Project Manager
Scope Evolves with market Defined at start
Example Microsoft Word (ongoing) Developing a new Word feature

Key Scheduling Terms — Flash Reference

Term Definition
Milestone Significant project event; no duration
Dependency Task B cannot start/finish until Task A does
Critical Path Longest task chain; Float = 0; controls project
deadline
Slack / Float Time a task can slip without delaying the project
Lead Time Successor starts before predecessor finishes
(overlap)
Lag Time Deliberate delay between predecessor finish and
successor start
Fast Tracking Parallel tasks to compress schedule (more risk)
Crashing Extra resources on critical tasks to save time
(more cost)
Resource Leveling Adjust schedule to balance team workload
Baseline Schedule Original approved plan used for progress
comparison

All 5 modules done! You're fully prepared, Merlin. Crush that exam! 📌