Software Project Management (SPM) AKTU Notes & Answers

1

Explain the significance of Software Project Management in today's industry. Highlight the key activities and methodologies involved.

🔥 Must Do 7 Marks 2024-25

Definition: Software Project Management (SPM) is the discipline of planning, organizing, directing, and controlling the development of software to achieve the desired outcome within time, budget, and quality constraints.

Significance of SPM in Today's Industry

Complexity Management: Modern software systems involve hundreds of developers across geographies. SPM provides structure to manage this complexity.
Cost Control: Without SPM, projects overrun budgets. The Chaos Report shows ~50% of IT projects fail due to poor management. SPM enforces cost baselines.
Time-to-Market: Competitive industries demand quick delivery. SPM scheduling techniques ensure milestones are met.
Quality Assurance: SPM integrates quality gates throughout the SDLC rather than testing only at the end.
Risk Mitigation: SPM identifies and mitigates risks before they become project failures.
Stakeholder Satisfaction: Clear communication plans and progress reports keep stakeholders informed and confident.
Resource Optimization: SPM prevents over-allocation or under-utilization of team members, tools, and infrastructure.

Key Activities in SPM

SPM Activity Lifecycle

Project
Initiation

→

Planning &
Estimation

→

Execution &
Monitoring

→

Risk
Management

→

Closure &
Review

Planning: Defining scope, WBS, milestones, and resource allocation.
Effort Estimation: Using COCOMO II, function points, or expert judgment to predict effort.
Scheduling: Building Gantt charts, PERT/CPM networks to track time.
Risk Management: Identify, assess, plan, and monitor risks continuously.
Quality Management: Code reviews, testing plans, acceptance criteria.
Configuration Management: Version control, change management.
Progress Monitoring: Earned Value Analysis, burn-down charts.

Key Methodologies

Traditional

Waterfall Model
V-Model
Incremental Model
Spiral Model

Agile / Modern

Scrum
Extreme Programming (XP)
DSDM
Kanban

SPM is the backbone of successful software delivery. It transforms ad-hoc development into a controlled, predictable process that delivers value to both developers and clients.

2

Discuss in detail the stepwise project planning process. Illustrate with a suitable example.

🔥 Must Do 7 Marks 2024-25

Stepwise Project Planning is a structured approach (by Hughes & Cotterell) that breaks planning into ordered, logical steps to manage scope, effort, resources, and risks progressively.

Mnemonic S-S-I-A-I-E-I-A-R-E: Select, Scope, Infrastructure, Analyze, Identify products, Estimate effort, Identify risks, Allocate resources, Review plan, Execute.

The 10 Steps of Stepwise Project Planning

Select project: Identify the project scope, feasibility, and strategic fit. Conduct cost-benefit analysis. Example: Decide to build an Online Examination System for a university.
Identify project scope and objectives: Define what is in scope (student registration, exam scheduling, result generation) and what is not (fee management).
Identify project infrastructure: Determine reporting structure, existing standards, and project management tools (Jira, Git).
Analyze project characteristics: Is it data-intensive? Real-time? Classify it to choose the right lifecycle model. Our system is data-intensive → use incremental model.
Identify products and activities: Break work into a Work Breakdown Structure (WBS). Products = SRS, design docs, code modules, test reports.
Estimate effort for each activity: Use function points or COCOMO II. E.g., login module = 5 person-days, exam engine = 20 person-days.
Identify activity risks: List risks for each activity. E.g., "Exam concurrency risk" if 500 students take exam simultaneously.
Allocate resources: Assign team members to tasks. Ensure no over-allocation. Developer A → login; Developer B → exam engine.
Review/publicize plan: Get sign-off from stakeholders. Publish the project plan document and schedule (Gantt chart).
Execute plan & lower-level planning: Kick off sprints/phases. Do detailed planning for each sprint iteratively as more information is known.

Example: Online Exam System

Step	Activity	Output
1-2	Feasibility, scope definition	Feasibility report, SRS
3-4	Infrastructure, classification	Tech stack decision (Java, MySQL)
5-6	WBS, effort estimation	Project schedule, 150 person-days
7	Risk identification	Risk register (server crash, data loss)
8-9	Resource allocation, review	Gantt chart, approved plan
10	Execution	Working system delivered in 6 months

Exam Focus

Write the 10 steps in order from selection to execution.
Explain where scope, effort, risk, and resources are handled.
Use the online exam system example to make the answer concrete.

Stepwise planning transforms vague project ideas into executable plans. Each step builds on the previous, reducing ambiguity and increasing confidence in delivery.

3

Discuss the various types of risk evaluation techniques used during project planning.

🔥 Must Do 7 Marks 2024-25

Risk Evaluation is the process of assessing identified risks in terms of their likelihood of occurrence and the magnitude of their impact on the project.

1. Risk Probability × Impact Matrix

Each risk is assigned a probability (0–1) and an impact score (1–10). The risk exposure = Probability × Impact.

Risk	Probability	Impact	Exposure	Priority
Staff turnover	0.4	8	3.2	High
Requirements change	0.6	7	4.2	Very High
Server downtime	0.2	9	1.8	Medium

2. Risk Register

A tabular document maintained throughout the project recording: risk ID, description, probability, impact, owner, mitigation strategy, and current status. It is the primary tool for tracking risks over time.

3. PERT (Program Evaluation and Review Technique) for Time Risk

PERT Expected Time Formula

t_e = (O + 4M + P) / 6

SD = (P − O) / 6

Where: O = Optimistic, M = Most likely, P = Pessimistic

4. Monte Carlo Simulation

A computerized statistical technique that models uncertainty by running thousands of simulations with random inputs drawn from probability distributions. Output: probability distribution of project completion dates and costs. Especially useful for large complex projects.

5. Decision Tree Analysis

A graphical tool to evaluate decisions under uncertainty. Each branch represents a possible outcome with a probability and monetary value. The Expected Monetary Value (EMV) is calculated for each path.

EMV Formula

EMV = Probability × Impact (in money)

6. Risk Categories (Boehm's Top-10 Risks)

Personnel shortfalls
Unrealistic schedules and budgets
Developing wrong software
Gold-plating (adding unnecessary features)
Continuous requirements changes
Shortfalls in externally supplied components

Risk Response Strategies

Negative Risks

Avoid – change plan
Transfer – insurance/contract
Mitigate – reduce probability
Accept – acknowledge and monitor

Positive Risks (Opportunities)

Exploit – make it certain
Share – partner with others
Enhance – increase probability
Accept – take advantage if it occurs

Risk evaluation is proactive rather than reactive. Projects that rigorously evaluate risks early save significantly more time and money than those that discover risks during execution.

4

Explain why the Discounted Cash Flow (DCF) technique provides better criteria for project selection than Net Profit or Return on Investment.

🔥 Important 10 Marks 2023-24

Limitations of Net Profit (NP)

NP = Total Income − Total Cost. It does not consider when income is received.
A project earning ₹1,00,000 in Year 1 is treated the same as one earning it in Year 5 — even though the Year-1 money is more valuable.
NP ignores the time value of money.

Limitations of Return on Investment (ROI)

ROI = (Net Profit / Investment) × 100. It gives a percentage but again ignores timing of cash flows.
Two projects can have the same ROI but very different risk profiles and cash flow patterns.
ROI doesn't account for project duration — a 2-year and a 10-year project with same ROI are not equivalent.

Why DCF / Net Present Value (NPV) is Superior

NPV Formula

NPV = Σ [ CF_t / (1 + r)^t ] − Initial Investment

where CF_t = Cash flow at time t, r = discount rate

Time Value of Money: DCF discounts future cash flows to their present value, reflecting that ₹100 today > ₹100 tomorrow.
Risk Adjustment: The discount rate r can be adjusted to reflect project risk — riskier projects use a higher rate.
Comparison across durations: NPV allows fair comparison of projects with different lifespans.
Absolute value: NPV gives an absolute monetary figure (positive = value added, negative = value destroyed).
Decision Rule: Accept all projects where NPV > 0; choose the project with the highest NPV among alternatives.

Criteria	Net Profit	ROI	DCF / NPV
Time value of money	No	No	✓ Yes
Accounts for risk	No	No	✓ Via discount rate
Compares duration	No	No	✓ Yes
Clear decision rule	Partial	Partial	✓ NPV > 0

DCF is the gold standard for project selection because it acknowledges that a pound today is worth more than a pound tomorrow, and allows projects of different durations, risks, and cash flow patterns to be compared on a common basis.

5

Calculate Net Profit (NP), Payback Period (PP), Return on Investment (ROI) and Net Present Value (NPV) for the four projects (discount rate = 10%).

🔥 Numerical 10 Marks 2023-24

Year	Project 1	Project 2	Project 3	Project 4
0 (Investment)	−1,00,000	−10,00,000	−1,00,000	−1,20,000
1	10,000	2,00,000	30,000	30,000
2	10,000	2,00,000	30,000	30,000
3	10,000	2,00,000	30,000	30,000
4	20,000	2,00,000	30,000	30,000
5	1,00,000	3,00,000	30,000	75,000

Discount Factors at r = 10%

Year 1: 1/1.1¹ = 0.909

Year 2: 1/1.1² = 0.826

Year 3: 1/1.1³ = 0.751

Year 4: 1/1.1⁴ = 0.683

Year 5: 1/1.1⁵ = 0.621

Project 1

Total Income = 10k+10k+10k+20k+100k = ₹1,50,000

NP = 1,50,000 − 1,00,000 = ₹50,000

ROI = (50,000 / 1,00,000) × 100 = 50%

PP: Cumulative: Y1=10k, Y2=20k, Y3=30k, Y4=50k, Y5=1,50,000 → Between Y4 and Y5

NPV = 10000×0.909 + 10000×0.826 + 10000×0.751 + 20000×0.683 + 100000×0.621 − 100000

= 9090+8260+7510+13660+62100 − 100000 = 100620 − 100000 = NPV = ₹620

Project 2

Total Income = 200k×4 + 300k = ₹11,00,000

NP = 11,00,000 − 10,00,000 = ₹1,00,000

ROI = (1,00,000 / 10,00,000) × 100 = 10%

PP: Cumulative: Y1=2L, Y2=4L, Y3=6L, Y4=8L, Y5=11L → Between Y4 and Y5

NPV = 200000×(0.909+0.826+0.751+0.683) + 300000×0.621 − 1000000

= 200000×3.169 + 186300 − 1000000 = 633800 + 186300 − 1000000 = NPV = −₹1,79,900

Project 3

Total Income = 30,000 × 5 = ₹1,50,000

NP = 1,50,000 − 1,00,000 = ₹50,000

ROI = 50%

PP: Cumulative Y1=30k, Y2=60k, Y3=90k, Y4=1,20,000 → ~3.33 years (midway Y3-Y4)

NPV = 30000×(0.909+0.826+0.751+0.683+0.621) − 100000

= 30000×3.79 − 100000 = 113700 − 100000 = NPV = ₹13,700

Project 4

Total Income = 30k×4 + 75k = ₹1,95,000

NP = 1,95,000 − 1,20,000 = ₹75,000

ROI = (75,000 / 1,20,000) × 100 = 62.5%

PP: Y1=30k, Y2=60k, Y3=90k, Y4=1,20,000 → Exactly 4 years

NPV = 30000×(0.909+0.826+0.751+0.683) + 75000×0.621 − 120000

= 30000×3.169 + 46575 − 120000 = 95070 + 46575 − 120000 = NPV = ₹21,645

Summary & Best Project

Project	NP	ROI	Payback	NPV
1	50,000	50%	~5 yrs	₹620
2	1,00,000	10%	~5 yrs	−₹1,79,900 ❌
3	50,000	50%	~3.3 yrs	₹13,700
4	75,000	62.5%	4 yrs	₹21,645 ✅ Best

Project 4 is the best choice: highest NPV (₹21,645), highest ROI (62.5%), and a reasonable payback period of 4 years. Project 2 should be rejected as its NPV is negative.

6

What is the COCOMO II model? Explain its components and how it is used in software cost estimation.

🔥 Must Do 7 Marks 2024-25

COCOMO II (Constructive Cost Model II) is a parametric software cost estimation model developed by Barry Boehm in 1995. It is the updated version of original COCOMO (1981) and supports modern software development practices including object-oriented development, component-based development, and spiral models.

Three Sub-Models of COCOMO II

1. Application Composition

Used in early prototyping. Estimates based on Object Points (screens, reports, modules). Low detail needed.

2. Early Design

Used when requirements are stabilizing. Uses Function Points. Helps in early budgeting and feasibility.

3. Post-Architecture

Most detailed. Used after architecture is established. Uses SLOC (Source Lines of Code). Most accurate.

Post-Architecture Formula (Most Important)

COCOMO II Post-Architecture Equations

PM = A × Size^E × ∏EM_i

TDEV = C × PM^F

Where:

PM = Person-Months effort | A = 2.94 (constant)

Size = in KSLOC | EM_i = Effort Multipliers

E = Exponent from Scale Factors (B + 0.01 × ΣSF)

B = 0.91 | TDEV = Development time

Scale Factors (SF) — 5 Factors

Scale Factor	Description
PREC (Precedentedness)	How similar is this to previous projects?
FLEX (Development Flexibility)	How rigid are the requirements?
RESL (Risk Resolution)	How well is the architecture designed?
TEAM (Team Cohesion)	How well does the team work together?
PMAT (Process Maturity)	CMM level of the organization

Effort Multipliers (EM) — 17 Cost Drivers

These adjust the base estimate based on product, platform, personnel, and project factors. Key ones:

RELY — Required software reliability
CPLX — Product complexity
ACAP — Analyst capability
PCAP — Programmer capability
TOOL — Use of software tools

Example Calculation

Given: Size = 100 KSLOC, E = 1.10, EM product = 1.2

PM = 2.94 × 100^1.10 × 1.2

100^1.10 = 158.49

PM = 2.94 × 158.49 × 1.2 = ≈ 559 person-months

TDEV = 3.67 × 559^0.28+0.2E ≈ ~42 months

COCOMO II is the industry-preferred parametric model because it accounts for modern development practices, organizational maturity, and team factors — making estimates far more realistic than simple LOC-based approaches.

7

Explain the significant features of the RAD (Rapid Application Development) model for software development.

🔥 Must Do 7-10 Marks Both Years

RAD (Rapid Application Development) is a type of incremental software process model that emphasizes an extremely short development cycle (60–90 days) using component-based construction and heavy use of CASE tools.

RAD Phases

RAD Development Cycle

Business
Modelling

→

Data
Modelling

→

Process
Modelling

→

Application
Generation

→

Testing &
Turnover

Business Modelling: Models information flow between business functions — what drives the business process?
Data Modelling: Identifies data objects, their attributes, and relationships defined in the business model.
Process Modelling: Describes how data objects are transformed using information flow. Functions are created to add, modify, delete, or retrieve data.
Application Generation: Uses 4GL tools, GUI builders, and reusable components. Code is generated rather than written manually.
Testing & Turnover: Since reusable components are already tested, only new components need extensive testing. Integration testing is primary focus.

Key Features of RAD

Speed: Full functional system in 60–90 days using parallel development teams.
Prototyping: Heavy use of prototyping to quickly elicit requirements from users.
Component reuse: Prebuilt components from previous projects dramatically reduce coding time.
CASE tools: Computer-Aided Software Engineering tools automate design and code generation.
User involvement: Users actively participate in design sessions (JAD — Joint Application Development).
Iterative: Multiple teams work in parallel on different subsystems.

Advantages vs Disadvantages

Advantages

Fast delivery
Reduced development cost
High user satisfaction
Easy adaptability to changes

Limitations

Not suitable for large-scale systems
Requires modularizable requirements
Needs committed, skilled teams
Poor for computationally intensive apps

RAD is ideal for business application development where time-to-market is critical and requirements can be compartmentalized. It is not suitable for safety-critical, real-time, or highly integrated systems.

8

Outline Agile methods for software development.

🔥 Must Do 10 Marks 2023-24

Agile is a set of iterative, incremental software development methods based on the Agile Manifesto (2001) that prioritizes working software, customer collaboration, responding to change, and individuals over processes and tools.

Agile Manifesto — 4 Values

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

12 Agile Principles (Key ones)

Deliver working software frequently (weeks, not months)
Welcome changing requirements, even late in development
Business people and developers must work together daily
Sustainable development — constant pace indefinitely
Simplicity — maximize work not done — is essential

Major Agile Methods

Method	Key Feature	Best For
Scrum	Time-boxed Sprints (2-4 weeks), Product Backlog, Daily Standup	Product development teams
XP (Extreme Programming)	Pair programming, TDD, continuous integration, small releases	High-change requirements
DSDM	Time-boxing, 9 principles, full lifecycle framework	Business-critical systems
Kanban	Visual board, WIP limits, continuous flow	Maintenance/support teams
Crystal	People-centric, scales with team size	Various team sizes

Scrum Framework (Most Common in Exams)

Scrum Sprint Cycle

Product
Backlog

→

Sprint
Planning

→

Sprint
(2-4 wks)

→

Sprint
Review

→

Potentially
Shippable

Agile vs Traditional

Aspect	Agile	Traditional (Waterfall)
Requirements	Evolving	Fixed upfront
Delivery	Incremental (every sprint)	Single final delivery
Customer involvement	Continuous	At start and end
Documentation	Minimal (just enough)	Heavy
Team size	Small, co-located (5–9)	Any size

Agile has become the dominant methodology in the software industry. Its focus on iterative delivery, continuous feedback, and flexibility makes it highly effective for projects where requirements evolve.

9

What are Full Function Points in the COSMIC model? How do they contribute to estimation?

🔥 Important 7 Marks 2024-25

COSMIC (Common Software Measurement International Consortium) is a functional size measurement method (ISO 19761) that measures software size in COSMIC Function Points (CFP) by counting data movements in and out of software processes.

Core Concept — Data Movements

COSMIC models software as a set of functional processes. Each functional process consists of data movements of 4 types:

Data Movement	Symbol	Description	Example
Entry (E)	E	Data moves INTO a functional process from a user or another layer	User enters username & password
Exit (X)	X	Data moves OUT of a functional process to a user or another layer	System displays error message
Read (R)	R	Data moves from persistent storage INTO a process	Read user record from database
Write (W)	W	Data moves from a process INTO persistent storage	Save new user record to database

COSMIC Size Formula

Size (CFP) = Number of Entries + Exits + Reads + Writes

1 CFP = 1 data movement of any type

Example: "User Login" Functional Process

E: User enters username → 1 CFP

E: User enters password → 1 CFP

R: Read user credentials from DB → 1 CFP

X: Display "Login Successful" → 1 CFP

X: Display "Login Failed" → 1 CFP

Total for Login Process = 5 CFP

How COSMIC Contributes to Estimation

Technology-independent: CFP counts are independent of programming language or platform, making them useful for early estimation.
Productivity benchmarking: Once a team knows their historical productivity (e.g., 5 person-hours per CFP), they can directly estimate effort: Effort = Size × Productivity.
Applicable to real-time systems: Unlike FPA, COSMIC supports embedded and real-time software.
ISO standard: ISO 19761 gives it international credibility for contractual sizing.

Effort Estimation

Effort = Total CFP × Productivity Rate

E.g., 200 CFP × 4 hrs/CFP = 800 person-hours

COSMIC FFP is superior to traditional LOC-based estimation because it measures what the software does (functional size) rather than how it is coded, making it language-agnostic and applicable from requirements stage.

10

Calculate Function Point value: EI=30, EO=42, EQ=08, ILF=07, EIF=06. Assume average complexity. TCF = 1.0 (all DI moderate).

🔥 Numerical 10 Marks 2023-24

Weighting Table (Average)

Component	Count	Avg Weight	Weighted Count
External Inputs (EI)	30	10	300
External Outputs (EO)	42	7	294
External Inquiries (EQ)	08	4	32
Internal Logical Files (ILF)	07	5	35
External Interface Files (EIF)	06	4	24
Total (UFP)			685

Step-by-Step Calculation

Unadjusted FP (UFP) = 300 + 294 + 32 + 35 + 24 = 685

Technical Complexity Factor (TCF) = 0.65 + (0.01 × ΣDI)

All 14 DIs are moderate = 3 each → ΣDI = 14 × 3 = 42

TCF = 0.65 + (0.01 × 42) = 0.65 + 0.42 = 1.07

FP = UFP × TCF = 685 × 1.07 = FP = 732.95 ≈ 733

The estimated size of the project is approximately 733 Function Points. This can be converted to SLOC using language-specific ratios or used directly for effort estimation with historical productivity data.

11

What is Critical Path Method (CPM)? How is it used to identify project bottlenecks?

🔥 Must Do 7 Marks 2024-25

CPM (Critical Path Method) is a step-by-step project scheduling technique used to determine the longest path of planned activities from start to finish of a project, and the earliest and latest that each activity can start and finish.

Summary CPM finds the critical path, shows the zero-float tasks, and helps managers focus on the activities that can delay the whole project.

Mnemonic L-D-F-B-F-C: List activities, Draw the network, Forward pass, Backward pass, Find float, Critical path.

Key Terminologies

Term	Full Form	Meaning
ES	Earliest Start	Earliest time an activity can begin
EF	Earliest Finish	ES + Duration
LS	Latest Start	Latest time activity can start without delaying project
LF	Latest Finish	LS + Duration
Float/Slack	—	LS − ES = LF − EF (allowable delay)
Critical Path	—	Path where Float = 0 for all activities

Steps in CPM

List all activities with durations and precedence relationships.
Draw the Activity-on-Node (AON) network diagram.
Perform Forward Pass to calculate ES and EF for every node.
Rule: ES of successor = max(EF of all predecessors)
Perform Backward Pass to calculate LS and LF for every node.
Rule: LF of predecessor = min(LS of all successors)
Calculate Float = LS − ES for each activity.
Activities with Float = 0 form the Critical Path.

How CPM Identifies Bottlenecks

Critical activities: Any delay in a critical path activity directly delays the project. These are the bottlenecks.
Near-critical paths: Paths with very small float (e.g., 1-2 days) are at risk of becoming critical — secondary bottlenecks.
Resource conflicts: Two critical activities requiring the same resource simultaneously create a resource bottleneck.
Crashing: To reduce project duration, CPM tells you which activities to crash (reduce duration by adding resources) — only crashing critical activities reduces total project time.

CPM Rules

Forward Pass: EF = ES + Duration

Backward Pass: LS = LF − Duration

Float = LS − ES = LF − EF

Critical Path: Float = 0

Exam Focus

Define CPM and explain ES, EF, LS, LF.
State how float is found and why the critical path matters.
Mention bottlenecks and crashing as control techniques.

CPM transforms a complex project into a manageable map of dependencies, clearly showing which tasks are bottlenecks. Project managers focus control efforts on critical activities while allowing non-critical tasks flexibility.

12

Formulate an AON activity network, carry out forward and backward pass, and identify critical paths for the given 8-activity project.

🔥 Numerical — Must Do 10 Marks 2023-24

Activity	Description	Duration (wks)	Precedents
A	Hardware selection	8	—
B	System configuration	5	—
C	Install hardware	3	A
D	Data migration	4	B
E	Draft office procedures	4	B
F	Recruit staff	12	—
G	User training	5	E, F
H	Install and test system	3	C, D

Forward Pass (ES, EF)

ES = max(EF of predecessors), EF = ES + Duration

A: ES=0, EF=0+8=8

B: ES=0, EF=0+5=5

F: ES=0, EF=0+12=12

C: ES=EF(A)=8, EF=8+3=11

D: ES=EF(B)=5, EF=5+4=9

E: ES=EF(B)=5, EF=5+4=9

G: ES=max(EF(E),EF(F))=max(9,12)=12, EF=12+5=17

H: ES=max(EF(C),EF(D))=max(11,9)=11, EF=11+3=14

Project Duration = max(EF(G),EF(H)) = max(17,14) = 17 weeks

Backward Pass (LF, LS, Float)

LF = min(LS of successors), LS = LF − Duration, Float = LS − ES

G: LF=17, LS=17−5=12, Float=12−12=0 ← Critical

H: LF=17, LS=17−3=14, Float=14−11=3

F: LF=LS(G)=12, LS=12−12=0, Float=0−0=0 ← Critical

E: LF=LS(G)=12, LS=12−4=8, Float=8−5=3

D: LF=LS(H)=14, LS=14−4=10, Float=10−5=5

C: LF=LS(H)=14, LS=14−3=11, Float=11−8=3

B: LF=min(LS(D),LS(E))=min(10,8)=8, LS=8−5=3, Float=3−0=3

A: LF=LS(C)=11, LS=11−8=3, Float=3−0=3

Summary Table

Activity	ES	EF	LS	LF	Float	Critical?
A	0	8	3	11	3	No
B	0	5	3	8	3	No
C	8	11	11	14	3	No
D	5	9	10	14	5	No
E	5	9	8	12	3	No
F	0	12	0	12	0	✓ YES
G	12	17	12	17	0	✓ YES
H	11	14	14	17	3	No

Critical Path: F → G with duration = 17 weeks. Any delay in recruiting staff (F) or user training (G) will directly delay the entire project. All other activities have float and are non-critical.

13

Write about: (i) Risk Identification (ii) PERT Technique

🔥 Must Do 7 Marks 2024-25

(i) Risk Identification

Risk Identification is the systematic process of finding, recognizing, and documenting risks that could potentially affect the software project's objectives.

Techniques for Risk Identification:

Brainstorming: Team sessions where members freely suggest potential risks without judgment. Most common technique.
Checklists: Pre-built lists of common risks based on past projects (Boehm's Top-10, CMM checklists).
Expert Judgment: Senior developers/managers identify risks based on experience.
Assumption Analysis: Examining project assumptions to find risks if assumptions prove false.
Delphi Technique: Anonymous expert opinions collected and iterated until consensus on risks.
SWOT Analysis: Identifies risks from Weaknesses and Threats.

Categories of Risks (Boehm):

Technical Risks: Unproven technology, complex algorithms, integration problems
Project Risks: Schedule slippage, staff turnover, scope creep
Business Risks: Market changes, budget cuts, competitor products
External Risks: Regulatory changes, vendor delays, natural disasters

Output: Risk Register — a document listing all identified risks with descriptions, likelihood, impact, and owners.

(ii) PERT (Program Evaluation and Review Technique)

PERT is a statistical project scheduling tool developed by the US Navy in 1957. It handles uncertainty in activity duration estimates using three time estimates.

PERT Formulas

Expected Time: t_e = (O + 4M + P) / 6

Standard Deviation: σ = (P − O) / 6

Variance: V = σ² = [(P − O) / 6]²

O = Optimistic, M = Most Likely, P = Pessimistic

PERT Example

Activity	O	M	P	t_e	σ
Design	3	5	9	(3+20+9)/6 = 5.33	(9-3)/6 = 1
Coding	5	8	15	(5+32+15)/6 = 8.67	(15-5)/6 = 1.67
Testing	2	4	8	(2+16+8)/6 = 4.33	(8-2)/6 = 1

PERT vs CPM:

PERT: probabilistic (3 estimates), used for R&D/uncertain projects
CPM: deterministic (1 estimate), used for construction/well-defined projects
Both use network diagrams and find critical paths

14

Explain the framework for managing and controlling software projects.

🔥 Must Do 7 Marks 2024-25

The Project Management and Control Framework is a structured system that enables project managers to continuously monitor project status, compare actual progress against the plan, and take corrective action when deviations occur.

Framework Components

Control Cycle

Plan
Baseline

→

Collect
Data

→

Visualize
Progress

→

Analyze
Variances

→

Take
Action

1. Data Collection

Timesheets: hours logged per task
Defect reports: number and severity of bugs found
Milestone completion: achieved vs. planned
Deliverable reviews: quality of outputs

2. Visualizing Progress

Gantt Charts: Bar chart showing planned vs. actual activity timelines
Burn-down Charts: Shows remaining work vs. time (Agile)
S-Curves: Cumulative cost or effort over time
Slip Charts: Revised milestones plotted against original schedule

3. Earned Value Analysis (EVA)

The most powerful quantitative control technique. Three key metrics:

EVA Key Metrics

BCWS (PV) = Planned Value — what should be done by now

BCWP (EV) = Earned Value — what has actually been done

ACWP (AC) = Actual Cost — what has been spent

SV = EV − PV (Schedule Variance)

CV = EV − AC (Cost Variance)

SPI = EV/PV (Schedule Performance Index)

CPI = EV/AC (Cost Performance Index)

4. Change Control

All changes must go through a formal Change Control Board (CCB)
Change requests are assessed for impact on scope, time, cost, quality
Approved changes trigger re-baselining of the plan

5. Project Tracking Tools

Issue logs: Track open problems and resolutions
Risk registers: Monitor changing risk status
Status reports: Weekly/monthly summaries for stakeholders

An effective project control framework is the difference between a project that discovers problems when it's too late and one that detects deviations early and corrects course while recovery is still possible.

15

Calculate EAC and VAC when both SPI and CPI influence project work. BAC=$22,000, EV=$13,000, PV=$14,000, AC=$15,000.

🔥 Numerical 10 Marks 2023-24

Step 1 — Basic Metrics

BAC = $22,000 | EV = $13,000 | PV = $14,000 | AC = $15,000

SV = EV − PV = 13,000 − 14,000 = −$1,000 (Behind schedule)

CV = EV − AC = 13,000 − 15,000 = −$2,000 (Over budget)

SPI = EV/PV = 13,000/14,000 = 0.929 (Below 1 = behind)

CPI = EV/AC = 13,000/15,000 = 0.867 (Below 1 = over budget)

Step 2 — EAC (when both SPI & CPI influence)

EAC = AC + [(BAC − EV) / (CPI × SPI)]

EAC = 15,000 + [(22,000 − 13,000) / (0.867 × 0.929)]

EAC = 15,000 + [9,000 / 0.806]

EAC = 15,000 + 11,165.01

EAC = $26,165

Step 3 — VAC (Variance at Completion)

VAC = BAC − EAC = 22,000 − 26,165 = −$4,165

Negative VAC means the project will OVERRUN budget by $4,165

Interpretation

Metric	Value	Interpretation
SPI = 0.929	< 1	Project is behind schedule
CPI = 0.867	< 1	Project is over budget
EAC = $26,165	> BAC	Project will cost $4,165 more than planned
VAC = −$4,165	Negative	Budget overrun expected

Both schedule and cost performance are unfavorable. The project manager must take immediate corrective action — either crash the schedule, reduce scope, or request additional budget to bring the project back on track.

16

Calculate SPI and CPI. Activity A: AC=₹2,00,000, PV=₹1,80,000, 100% complete. Activity B: AC=₹1,00,000, PV=₹80,000, 75% complete.

🔥 Numerical 10 Marks 2023-24

Step 1 — Calculate Earned Value (EV) for each activity

EV = PV × % Complete

EV(A) = 1,80,000 × 1.00 = ₹1,80,000

EV(B) = 80,000 × 0.75 = ₹60,000

Total EV = 1,80,000 + 60,000 = ₹2,40,000

Step 2 — Total Planned Value (PV) and Actual Cost (AC)

Total PV = 1,80,000 + 80,000 = ₹2,60,000

Total AC = 2,00,000 + 1,00,000 = ₹3,00,000

Step 3 — Calculate SPI and CPI

SPI = EV / PV = 2,40,000 / 2,60,000 = 0.923

CPI = EV / AC = 2,40,000 / 3,00,000 = 0.800

Schedule Variance (SV) = EV − PV = 2,40,000 − 2,60,000 = −₹20,000

Cost Variance (CV) = EV − AC = 2,40,000 − 3,00,000 = −₹60,000

Interpretation

Metric	Value	Meaning
SPI = 0.923	< 1.0	Only 92.3% of scheduled work completed — behind schedule
CPI = 0.800	< 1.0	Spending ₹1.25 for every ₹1 of value — over budget
SV = −₹20,000	Negative	₹20,000 worth of work is behind plan
CV = −₹60,000	Negative	₹60,000 over budget

The project is both behind schedule (SPI < 1) and over budget (CPI < 1). Activity B is the primary concern as it is only 75% complete despite consuming its full planned budget. Immediate corrective action is required.

17

Discuss Software Configuration Management (SCM) and the steps to handle the change control process.

🔥 Important 7-10 Marks 2023-24

Software Configuration Management (SCM) is the discipline of tracking and controlling changes in software to ensure integrity, consistency, and traceability throughout the software lifecycle. It is defined in IEEE 828.

Summary SCM protects the baseline, tracks every version, and controls change so the project stays traceable, testable, and safe to release.

SCM Activities (IEEE 828)

Configuration Identification: Labeling and numbering all software products (code, docs, data) as configuration items (CIs). Establishes baselines.
Configuration Control: Managing changes to CIs. Every change requires formal approval.
Configuration Status Accounting: Recording and reporting the status of CIs and changes. Answers "what version is deployed?"
Configuration Auditing: Verifying that CIs conform to their specifications (functional) and that all changes are properly documented (physical).
Release Management: Managing the packaging and delivery of releases to customers.

Change Control Process — Steps

Change Request (CR) Submission: Developer/user raises a change request describing the desired change, reason, and urgency via a CR form.
Impact Analysis: Technical team analyzes the impact on cost, schedule, quality, and other CIs. Documents ripple effects.
CCB Review: Change Control Board (project manager, QA lead, client) evaluates the CR. Decision: Approve / Reject / Defer.
Change Implementation: If approved, developer implements the change in a controlled branch. Original baseline is preserved.
Testing & Verification: Changed code is unit-tested, integration-tested, and regression-tested. QA verifies the change works as intended.
Re-baselining: After verification, the new version becomes the current baseline. Version number is incremented (e.g., v1.2 → v1.3).
Status Accounting Update: CR status updated to "Closed". Change log updated. All stakeholders notified.

Mnemonic R-I-B-I-T-R-C: Request, Impact, Board, Implement, Test, Rebaseline, Close.

Exam Focus

Explain how SCM protects the baseline and the version history.
Write the change control process from CR submission to status update in order.
Mention the role of the CCB and testing before release.

Version Control Tools

Git (most popular), SVN, Mercurial, CVS
Features: branching, merging, history, tagging releases

SCM is the safety net of software development. Without it, teams face the "software crisis" — no one knows which version is current, changes break other modules, and rollback is impossible. With SCM, every change is traceable, reversible, and controlled.

18

What is the Oldham-Hackman Job Characteristic Model? How does it help in enhancing team performance?

🔥 Must Do 7 Marks 2024-25

The Hackman-Oldham Job Characteristics Model (JCM) (1976) proposes that five core job dimensions influence three critical psychological states, which in turn lead to high motivation, performance, and satisfaction.

Five Core Job Dimensions

Dimension	Definition	Software Example
Skill Variety	Range of different activities requiring different skills	Developer does coding, design, and testing
Task Identity	Completing a whole, identifiable piece of work	Developer owns a complete feature end-to-end
Task Significance	Degree the job impacts others' lives	"My payment module processes 10,000 daily transactions"
Autonomy	Freedom in scheduling and methods	Choose your own tools and work schedule
Feedback	Clear information about job performance	Automated test results, code review comments

Motivating Potential Score (MPS)

MPS Formula

MPS = [(Skill Variety + Task Identity + Task Significance) / 3] × Autonomy × Feedback

Higher MPS → Higher intrinsic motivation

Three Critical Psychological States

Experienced Meaningfulness: Work feels important and valuable (driven by SV + TI + TS)
Experienced Responsibility: Employee feels accountable for outcomes (driven by Autonomy)
Knowledge of Results: Employee knows how well they are performing (driven by Feedback)

Outcomes

When all three psychological states are present:

High internal work motivation
High quality work performance
High job satisfaction
Low absenteeism and turnover

Application in Software Teams

Assign developers to complete features rather than isolated tasks (↑ Task Identity)
Rotate roles — let developers do design, coding, and testing (↑ Skill Variety)
Give teams freedom to choose their technology stack (↑ Autonomy)
Implement CI/CD with automated testing for instant feedback (↑ Feedback)
Communicate how the software impacts end-users (↑ Task Significance)

The Hackman-Oldham model explains why software teams with high autonomy and rich job designs outperform those with repetitive, fragmented tasks. It's a roadmap for designing jobs that developers find intrinsically rewarding.

19

Explain the Organizational Behavior approach to software staffing and team dynamics.

🔥 Must Do — Both Years 7-10 Marks Both Years

Organizational Behavior (OB) is the study of how individuals and groups behave within organizations. In SPM, OB principles guide hiring, team formation, motivation, conflict resolution, and leadership.

1. Staff Selection Best Practices

Skills matrix: Map required technical and soft skills, then hire to fill gaps.
Psychometric testing: Assess problem-solving ability, personality, and team compatibility.
Technical interviews: Code challenges and design problems assess actual capability.
Cultural fit: Assess alignment with team values and communication styles.

2. Motivation Theories in Software Teams

Theory	Author	Application in Software
Maslow's Hierarchy	Maslow	Ensure basic needs (salary, safety) before expecting self-actualization (creative coding)
Two-Factor Theory	Herzberg	Hygiene: fair pay, safe office. Motivators: challenging work, recognition
ERG Theory	Alderfer	Existence, Relatedness, Growth needs in teams
Expectancy Theory	Vroom	Reward systems must be fair and achievable to motivate

3. Team Dynamics — Tuckman's Stages

Forming: Team assembles. Roles unclear. High dependence on leader. Manager must provide direction.
Storming: Conflicts emerge over methods, authority, roles. Manager must mediate and establish ground rules.
Norming: Consensus reached. Norms established. Team starts collaborating effectively.
Performing: Team is high-functioning, autonomous, and productive. Manager can delegate freely.
Adjourning: Project ends. Team disbands. Recognition and transition planning important.

4. Organizational Structures

Functional Structure

Grouped by skill (dev, QA, design)
Deep expertise
Poor project focus

Matrix Structure

Cross-functional project teams
Dual reporting (PM + Function Head)
Best for complex software projects

5. Communication in Teams

Communication channels: n(n-1)/2 where n = team size. A team of 10 has 45 channels — complexity of coordination grows rapidly.
Use structured communication: daily standups, sprint reviews, wikis, issue trackers
Virtual teams require extra discipline: defined time zones, async communication tools (Slack, Confluence)

OB transforms technical project management into human-centered leadership. Understanding why people behave as they do — and designing work, structures, and incentives accordingly — is what separates great software project managers from average ones.

20

Explain various stress management techniques used for project staff.

🔥 Important 7 Marks 2024-25

Stress in software projects arises from tight deadlines, unclear requirements, long hours, and interpersonal conflicts. Unmanaged stress leads to burnout, errors, absenteeism, and talent attrition.

Causes of Stress in Software Teams

Unrealistic schedules and deadlines
Scope creep without additional resources
Lack of clarity in requirements
Poor team communication and conflicts
Job insecurity and organizational change
Work-life imbalance (crunch culture)

Stress Management Techniques

A. Organizational Level

Realistic scheduling: Use proper estimation (COCOMO II, FP) to avoid impossible deadlines.
Clear role definition: Job descriptions, RACI matrices eliminate ambiguity about responsibilities.
Flexible working: Remote work options, flexible hours reduce commute stress.
Employee Assistance Programs (EAP): Counseling and mental health support.
Recognition and reward: Regular acknowledgment of achievement reduces anxiety about job security.

B. Team Level

Regular retrospectives: Agile retrospectives allow teams to surface and resolve team-level stressors every sprint.
Conflict resolution: Trained mediators or manager-led resolution of interpersonal conflicts.
Team building: Social activities, hackathons, and team lunches build cohesion and reduce tension.
Workload balancing: Kanban WIP limits prevent any individual from being overloaded.

C. Individual Level

Time management: Prioritization techniques (Eisenhower matrix, Pomodoro technique).
Exercise and physical health: Regular breaks, walking meetings, gym memberships.
Mindfulness and meditation: Apps like Headspace offered as corporate benefits.
Cognitive restructuring: Reframing stressful situations as challenges rather than threats.

D. Health & Safety Considerations

Ergonomic workstations to prevent RSI and eye strain
Mandatory rest periods and maximum working hours policies
Mental health days as recognized leave

Stress management is not a luxury but a productivity imperative. Teams that operate in psychologically safe, well-managed environments consistently outperform those under chronic stress in both output quality and creativity.

21

Three mental obstacles to good decision-making: faulty heuristics, escalation of commitment, and information overload. Formulate steps to reduce the danger of each.

🔥 Important 10 Marks 2023-24

1. Faulty Heuristics (Cognitive Biases)

Heuristics are mental shortcuts used to make quick decisions. They are usually helpful but can lead to systematic errors (biases).

Common faulty heuristics in SPM:

Anchoring: Over-relying on the first estimate given. E.g., if a developer says "2 weeks", the whole estimate anchors around that.
Availability bias: Judging likelihood of events based on how easily examples come to mind. Recent project failures seem more likely than they are.
Optimism bias: Consistently underestimating time and cost ("planning fallacy").

Steps to reduce faulty heuristics:

Use structured estimation methods (Delphi, FP, COCOMO) rather than gut feel.
Seek independent estimates from multiple team members before revealing others' estimates.
Use historical data from past projects as reference classes.
Appoint a "devil's advocate" to challenge all assumptions in key decisions.

2. Escalation of Commitment

Escalation of Commitment (sunk cost fallacy) is the tendency to continue investing in a failing course of action because of already-invested resources, rather than based on future prospects.

Example: Continuing to develop a failing software product because "we've already spent ₹50 lakhs on it" rather than cutting losses.

Steps to reduce escalation of commitment:

Establish clear "kill criteria" at project start — predefined thresholds at which the project will be cancelled.
Separate the decision-maker from the project champion to reduce emotional attachment.
Conduct regular independent project audits and stage-gate reviews.
Reframe: ask "If we hadn't invested anything yet, would we start this project today?" If no, stop.
Reward managers for stopping bad projects, not just completing them.

3. Information Overload

Information Overload occurs when the volume of information a decision-maker must process exceeds their cognitive capacity, leading to poor decisions or decision paralysis.

In software projects: too many KPIs, dashboards, reports, and status meetings create noise rather than clarity.

Steps to reduce information overload:

Define a small set of key metrics (KPIs) that truly matter — SPI, CPI, defect rate, velocity.
Use exception reporting: only report when metrics deviate beyond agreed thresholds.
Create a single source of truth (project dashboard) rather than multiple conflicting reports.
Apply the "management by exception" principle — managers are informed only when action is needed.
Filter and summarize: project managers should receive executive summaries, not raw data dumps.

Obstacle	Core Problem	Key Solution
Faulty Heuristics	Subjective biases in estimation	Use structured, data-driven methods
Escalation of Commitment	Emotional attachment to past decisions	Pre-set kill criteria; independent review
Information Overload	Too much data, too little insight	Exception reporting; focused KPIs

Awareness of these cognitive traps is the first step. Combining structured processes, independent oversight, and clear decision rules protects project managers from their own psychology — which is as important as any technical skill.

SoftwareProjectManagement

Significance of SPM in Today's Industry

Key Activities in SPM

Key Methodologies

Traditional

Agile / Modern

The 10 Steps of Stepwise Project Planning

Example: Online Exam System

1. Risk Probability × Impact Matrix

2. Risk Register

3. PERT (Program Evaluation and Review Technique) for Time Risk

4. Monte Carlo Simulation

5. Decision Tree Analysis

6. Risk Categories (Boehm's Top-10 Risks)

Risk Response Strategies

Negative Risks

Positive Risks (Opportunities)

Limitations of Net Profit (NP)

Limitations of Return on Investment (ROI)

Why DCF / Net Present Value (NPV) is Superior

Project 1

Project 2

Project 3

Project 4

Summary & Best Project

Three Sub-Models of COCOMO II

1. Application Composition

2. Early Design

3. Post-Architecture

Post-Architecture Formula (Most Important)

Scale Factors (SF) — 5 Factors

Effort Multipliers (EM) — 17 Cost Drivers

Example Calculation

RAD Phases

Key Features of RAD

Advantages vs Disadvantages

Advantages

Limitations

Agile Manifesto — 4 Values

12 Agile Principles (Key ones)

Major Agile Methods

Scrum Framework (Most Common in Exams)

Agile vs Traditional

Core Concept — Data Movements

Example: "User Login" Functional Process

How COSMIC Contributes to Estimation

Weighting Table (Average)

Key Terminologies

Steps in CPM

How CPM Identifies Bottlenecks

Forward Pass (ES, EF)

Backward Pass (LF, LS, Float)

Summary Table

(i) Risk Identification

(ii) PERT (Program Evaluation and Review Technique)

PERT Example

Framework Components

1. Data Collection

2. Visualizing Progress

3. Earned Value Analysis (EVA)

4. Change Control

5. Project Tracking Tools

Interpretation

Interpretation

SCM Activities (IEEE 828)

Change Control Process — Steps

Version Control Tools

Five Core Job Dimensions

Motivating Potential Score (MPS)

Three Critical Psychological States

Outcomes

Application in Software Teams

1. Staff Selection Best Practices

2. Motivation Theories in Software Teams

3. Team Dynamics — Tuckman's Stages

4. Organizational Structures

Functional Structure

Matrix Structure

5. Communication in Teams

Causes of Stress in Software Teams

Software
Project
Management