Software Project Management

BOE068 | Semester 6 | Common to All Branches

Comprehensive Exam Study Guide

Session 2024-25 | AKTU | Important Questions + Detailed Answers

PART A: IMPORTANT QUESTIONS UNIT-WISE

UNIT 1 — Project Evaluation and Project Planning

Important Questions
• Q1.1 What is a project? Explain the characteristics of project.
• Q1.2 What is project management?
• Q1.3 Write short note on Software Project Management (SPM).
• Q1.4 What are the objectives of SPM?
• Q1.5 Discuss the structure of a Software Project Management Plan (SPMP) in detail.
• Q1.6 Explain the importance of Software Project Management.
• Q1.7 What are the activities involved in SPM?
• Q1.8 Explain the methodologies used in software project management.
• Q1.9 What is categorization of software projects? Explain different categories.
• Q1.10 What are management principles in software project management?
• Q1.11 Explain management control in software projects.
• Q1.12 What are the phases of project management?
• Q1.13 Explain software management principles.
• Q1.14 What is project portfolio management (PPM)? Explain its objectives.
• Q1.15 What are the benefits of PPM?
• Q1.16 Explain setting objectives in software project management.
• Q1.17 What is project portfolio management? Explain its features.
• Q1.18 What are the benefits of PPM?
• Q1.19 What is cost-benefit analysis?
• Q1.20 Explain different cost-benefit evaluation techniques.
• Q1.21 What is risk evaluation in software projects?
• Q1.22 What is strategic program management?
• Q1.23 Explain stepwise project planning in detail.
• Q1.24 What are the different types of project planning?
• Q1.25 Explain risk planning and risk management.
UNIT 2 — Project Life Cycle and Effort Estimation
Important Questions
• Q2.1 What is software process? Explain software process models.
• Q2.2 Explain the waterfall model in detail.
• Q2.3 What are the advantages and disadvantages of the waterfall model?
• Q2.4 Explain the spiral model in detail.
• Q2.5 What are the phases of the software development life cycle (SDLC)?
• Q2.6 What are the advantages and disadvantages of waterfall model?
• Q2.7 Explain Rapid Application Development (RAD) model.
• Q2.8 What are agile methods? Explain the principles of agile development.
• Q2.9 Explain Dynamic System Development Method (DSDM).
• Q2.10 Explain Extreme Programming (XP) methodology.
• Q2.11 What is managing interactive processes in software development?
• Q2.12 Explain the basics of software estimation.
• Q2.13 What are effort and cost estimation techniques?
• Q2.14 Explain COSMIC Full Function Points.
• Q2.15 What are function points? How are they calculated?
• Q2.16 Explain COCOMO model in detail.
• Q2.17 What is COCOMO II? Explain its sub-models.
• Q2.18 Explain the Basic COCOMO model with formula.
• Q2.19 What is Intermediate COCOMO? Explain cost drivers.
• Q2.20 What is Detailed COCOMO?
• Q2.21 Differentiate between Basic, Intermediate and Detailed COCOMO.
• Q2.22 What is choice of process model?
• Q2.23 Explain V-model (Verification and Validation model).
• Q2.24 Write short note on prototyping model.
• Q2.25 What is a parametric productivity model?

UNIT 3 — Activity Planning and Risk Management

Important Questions
• Q3.1 What are the objectives of activity planning?
• Q3.2 Explain project schedules in detail.
• Q3.3 What are activities in project planning? How are they sequenced and scheduled?
• Q3.4 Explain network planning models.
• Q3.5 How do you formulate a network model?
• Q3.6 Explain Forward Pass and Backward Pass techniques in CPM.
• Q3.7 What is Critical Path Method (CPM)? Explain with example.
• Q3.8 What is risk identification in software projects?
• Q3.9 What is risk assessment? How is it done?
• Q3.10 Explain risk planning in software projects.
• Q3.11 What is risk management? Explain the steps involved.
• Q3.12 Explain PERT technique with example.
• Q3.13 What is Monte Carlo simulation?
• Q3.14 Explain resource allocation in project management.
• Q3.15 How are critical paths created in a project?
• Q3.16 Explain cost schedules in project management.
• Q3.17 What is the difference between PERT and CPM?
• Q3.18 What is activity on arrow (AOA) and activity on node (AON) network?
 • Q3.19 Explain Gantt chart and its use in project management.
• Q3.20 What is risk mitigation?
• Q3.21 Explain different types of risks in software projects.
• Q3.22 Write short note on cost schedule.

UNIT 4 — Project Management and Control

Important Questions
• Q4.1 Explain the framework for management and control of software projects.
• Q4.2 How is data collected for project management? Explain.
• Q4.3 What are the methods of visualizing project progress?
• Q4.4 What is Earned Value Analysis (EVA)? Explain with formulas.
• Q4.5 Write short note on Cost Monitoring.
• Q4.6 What is prioritizing monitoring in project management?
• Q4.7 What is project tracking? Explain its importance.
• Q4.8 What is change control in software projects?
• Q4.9 What is Software Configuration Management (SCM)?
• Q4.10 Explain the activities involved in Software Configuration Management.
• Q4.11 What are the benefits of Software Configuration Management?
• Q4.12 Explain managing contracts in software projects.
• Q4.13 What is contract management?
• Q4.14 Explain different types of contracts used in software projects.
• Q4.15 What is a fixed-price contract?
• Q4.16 What is a time and materials contract?
• Q4.17 What are the stages of contract management?
• Q4.18 What are the issues faced in contract management?
• Q4.19 What are the benefits of contract management?
• Q4.20 Why is contract management necessary?
• Q4.21 Explain Earned Value Management (EVM) in detail.
• Q4.22 What is slip chart? How is it used in project monitoring?

UNIT 5 — Staffing in Software Projects

Important Questions
• Q5.1 What is managing people in software projects?
• Q5.2 What is organizational behaviour? Explain its importance in software projects.
• Q5.3 What are the best methods of staff selection?
• Q5.4 What is motivation? Explain different motivation theories.
• Q5.5 Explain the Oldham-Hackman job characteristic model.
• Q5.6 What is Maslow's Hierarchy of Needs theory?
• Q5.7 Explain Herzberg's Two-Factor theory of motivation.
• Q5.8 What is stress in software projects? How can it be managed?
• Q5.9 How is health and safety a part of an organization?
• Q5.10 What are ethical and professional concerns in software projects?
• Q5.11 What is working in teams? Explain the importance of teamwork.
• Q5.12 What is decision making in software project teams?
• Q5.13 What are organizational structures used in software projects?
• Q5.14 What are dispersed and virtual teams? How are they managed?
• Q5.15 What are communication genres in software projects?
• Q5.16 What are communication plans in software project management?
• Q5.17 What is leadership in software project management?
• Q5.18 Explain different leadership styles.
• Q5.19 Explain different types of organizational structures (functional, project-based, matrix).
• Q5.20 What are the advantages and disadvantages of virtual teams?
 PART B: DETAILED ANSWERS UNIT-WISE

UNIT 1 — Project Evaluation and Project Planning

(Answers)

Q1.1: What is a project? Explain the characteristics of project.

Definition of Project:
• A project is defined as a sequence of tasks that must be completed to attain a certain outcome.
• It is a temporary venture to produce a new and unique deliverable.
• A deliverable could be a tangible product, a service, or achievement of a required outcome.
• It is a sub-discipline of project management in which software projects are planned,
implemented, monitored and controlled.

Characteristics of a Project:
• Non-routine tasks are involved.
• Planning is required.
• Specific objectives are to be met.
• The project has a pre-determined time span.
• Work is carried out in several phases.
• The resources available for use on the project are constrained.

Q1.2: What is project management?

• Project management is the art of maximizing the probability that a project delivers its goals on
time, within budget and at the required quality.
• It is the application of knowledge, skills, tools, and techniques to project activities to meet
project requirements.
• Project management is accomplished through the use of processes such as: initiating, planning,
executing, controlling, and closing.
• The processes within project management are iterative in nature.

Q1.3: Write short note on Software Project Management (SPM).

• Software project management is an art and discipline of planning and supervising software
projects.
• It is a sub-discipline of project management in which software projects are planned,
implemented, monitored and controlled.
• It is a procedure of managing, allocating and timing resources to develop computer software
that fulfills requirements.

Advantages of SPM:
• It helps in planning of software development.
• Implementation of software development is made easy.
• Monitoring and controlling are aspects of software project management.
 • It overall manages to save time and cost for software development.

Q1.4: What are the objectives of SPM?

• Define the project.

• Reduce it to a set of manageable tasks.
• Obtain appropriate and necessary resources.
• Build a team to perform the project work.
• Plan the work and allocate resources to the tasks.
• Monitor and control the work.
• Report progress to senior management and/or the project sponsor.
• Close down the project when completed.
• Review it to ensure the lessons are learnt and widely understood.

Q1.12: What are the phases of project management?

• Step 1 — Project initiation and conception: Initiation begins after receiving a request from a
client or discovering a business need. Stakeholders determine whether the project is feasible
and valuable.
• Step 2 — Planning and ideation: When project viability is decided, next step is to put together a
project management plan that will guide us through the execution process.
• Step 3 — Project launch and execution: Once plan is in place, it's time to put it into action;
amend plan based on changing circumstances.
• Step 4 — Project monitoring: Throughout the execution process, we need to monitor, measure,
and report project management metrics.
• Step 5 — Closure and presentation: Time to tie up all loose ends by developing final project
reports and presenting deliverables to stakeholders.

Q1.19: What is cost-benefit analysis?

• Cost-benefit analysis (CBA) is a technique used to compare the total costs of a

programme/project with its benefits, using a common metric.
• It enables the calculation of the net cost or benefit associated with the programme.
• It is used most often at the start of a programme or project when different options or courses of
action are being appraised and compared.
• CBA helps decision makers evaluate the overall impact of a programme in terms of whether it
delivers value for money.

Steps in CBA:
• List all costs associated with the project (development, maintenance, operational costs).
• List all benefits (tangible and intangible).
• Assign monetary values to costs and benefits.
• Calculate Net Present Value (NPV) = Total Benefits - Total Costs.
• Calculate Cost-Benefit Ratio = Total Benefits / Total Costs. If > 1, project is viable.

Q1.23: Explain stepwise project planning in detail.

• Stepwise project planning is a structured approach to break down the overall project into
manageable steps and plan each step carefully.
Steps in Stepwise Project Planning:
• Step 1 — Select project: Identify the project and establish feasibility.
• Step 2 — Identify project scope and objectives: Clearly define what will be delivered and the
objectives.
• Step 3 — Identify project infrastructure: Identify relationship between project, standards, and
procedures.
• Step 4 — Analyse project characteristics: Determine technical difficulty, risks, and size.
• Step 5 — Identify project products and activities: List all deliverables and work needed to
produce them.
• Step 6 — Estimate effort for each activity: Use techniques like expert judgment, historical data,
or models.
• Step 7 — Identify activity risks: Identify risks associated with each activity.
• Step 8 — Allocate resources: Assign human and material resources to activities.
• Step 9 — Review/publicize plan: Review the plan for completeness and communicate to
stakeholders.
• Step 10 — Execute the plan: Monitor and control as project progresses.

Q1.24: What are the different types of project planning?

• Project scope definition and scope planning: Document the project work that helps achieve the
project goal; includes assumptions, constraints, user expectations, and requirements.
• Quality planning: Determine relevant quality standards; define processes to deliver the product
as promised.
• Project activity definition and activity sequencing: Define all specific activities to be performed;
identify interdependence of all activities.
• Time, effort, and resource estimation: Estimate time and effort required for each activity using
function points, lines of code, complexity, benchmarks, etc.
• Risk factors identification: Identify and document risk factors based on assumptions, constraints,
user expectations, and specific circumstances.
• Schedule development: Arrive at time schedule based on activities, interdependence, and effort
required; use tools like Gantt charts.
• Cost estimation and budgeting: Estimate cost involved in executing and implementing the
project; allocate budget accordingly.
• Organizational and resource planning: Based on activities, identify resource types; ensure
project is run efficiently.
• Risk management planning: Plan for identifying, analyzing, and responding to risks throughout
the project.

UNIT 2 — Project Life Cycle and Effort Estimation

(Answers)

Q2.2: Explain the waterfall model in detail.

• The Waterfall model is the oldest and most widely used software development life cycle (SDLC)
model.
• It is a sequential design process in which progress is seen as flowing steadily downwards (like a
waterfall) through phases.
Phases of Waterfall Model:
• Feasibility study: Assess whether the system is technically, financially, and operationally
feasible.
• Requirement analysis and specification: Gather and document all system requirements.
• System and software design: Convert requirements into system architecture and detailed
design.
• Coding and module testing: Write code and test individual modules (unit testing).
• Integration and system testing: Integrate modules and test the complete system.
• Implementation/Installation and maintenance: Deploy the system and maintain it after delivery.

Advantages:
• Easy to understand and use.
• Each stage has well-defined input and output.
• Helps in project planning.
• Provides a template into which methods for analysis, design, code, test and support can be
placed.

Disadvantages:
• Iteration not possible as it is a one-way street.
• Requirements freezing at starting stage.
• No stage can start until the previous stage is completed.
• High risk and uncertainty.

Q2.8: What are agile methods? Explain principles of agile development.

• Agile methods are a group of software development methods in which solutions evolve through
collaboration between self-organizing cross-functional teams.
• Agile promotes adaptive planning, evolutionary development, early delivery, and continuous
improvement.
• It encourages rapid and flexible response to change.

Principles of Agile (Agile Manifesto):

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

Key Agile Principles:

• Customer satisfaction through early and continuous delivery of valuable software.
• Welcome changing requirements, even late in development.
• Deliver working software frequently (weeks rather than months).
• Business people and developers must work together daily throughout the project.
• Build projects around motivated individuals; give them the environment and support they need.
• The most efficient method of conveying information is face-to-face conversation.
• Working software is the primary measure of progress.
• Sustainable development — sponsors, developers, and users should be able to maintain a
constant pace indefinitely.
• Continuous attention to technical excellence and good design enhances agility.
• Simplicity — the art of maximizing the amount of work not done — is essential.

Q2.16: Explain COCOMO model in detail.

 • COCOMO (Constructive Cost Model) was developed by Barry Boehm in 1981.
• It is an algorithmic software cost estimation model that estimates the effort, cost, and schedule
for software projects.
• COCOMO uses a regression formula with parameters derived from historical project data.

Three Versions of COCOMO:

• Basic COCOMO: Estimates effort and cost as a function of program size expressed in
estimated lines of code (KLOC). Formula: Effort (person-months) = a * (KLOC)^b. Three modes:
Organic, Semi-detached, Embedded.
• Intermediate COCOMO: Extends Basic COCOMO with cost drivers that account for product,
hardware, personnel, and project attributes. EAF (Effort Adjustment Factor) is product of cost
driver ratings.
• Detailed COCOMO: Incorporates all characteristics of Intermediate COCOMO with assessment
of cost driver impact on each phase of the SDLC.

COCOMO II Sub-models:
• Application Composition model — For prototyping and use of application builders.
• Early Design model — For early architectural design phase.
• Post-Architecture model — Most detailed; for actual development after architecture is
established.

COCOMO Project Modes:

• Organic: Small, simple projects with experienced teams; formula: E = 2.4(KLOC)^1.05
• Semi-detached: Medium projects with mixed experience; formula: E = 3.0(KLOC)^1.12
• Embedded: Complex projects with tight constraints; formula: E = 3.6(KLOC)^1.20

Q2.15: What are function points? How are they calculated?

• Function points (FP) measure the functionality of a software system from the user's point of
view.
• Developed by Allan Albrecht at IBM in 1979.
• FP is a unit of measurement to express the amount of business functionality an information
system provides to a user.

Five Components (Function Types):

• External Inputs (EI): Data or control input from outside the application boundary.
• External Outputs (EO): Data or control sent outside the application boundary.
• External Inquiries (EQ): Input-output combination that results in data retrieval.
• Internal Logical Files (ILF): User-identifiable groups of logically related data maintained within
the application.
• External Interface Files (EIF): User-identifiable groups of related data used by the application
but maintained by another application.

Calculation Steps:
• Step 1: Count each function type (EI, EO, EQ, ILF, EIF) and classify as simple, average, or
complex.
• Step 2: Calculate Unadjusted Function Points (UFP) by multiplying count by weight and
summing.
• Step 3: Calculate Value Adjustment Factor (VAF) based on 14 general system characteristics.
• Step 4: Adjusted FP = UFP x (0.65 + 0.01 x VAF).
UNIT 3 — Activity Planning and Risk Management
(Answers)

Q3.1: What are the objectives of activity planning?

• To produce a feasible plan that shows how the project can be completed successfully.
• To identify the sequence of activities that need to be performed.
• To show the time schedule for all activities.
• To identify resource requirements for each activity.
• To enable project monitoring and control by providing a baseline against which actual progress
can be measured.
• To determine the critical path — the sequence of activities that determines the minimum project
duration.
• To identify resource conflicts and help resolve them through resource leveling.

Q3.7: What is Critical Path Method (CPM)? Explain with example.

• CPM is a step-by-step project management technique for process planning that defines critical
and non-critical tasks with the goal of preventing time-frame problems and process bottlenecks.
• CPM identifies the longest stretch of dependent activities and measures the time required to
complete them from start to finish.
• The critical path is the longest duration path through the network — any delay in activities on the
critical path will delay the entire project.

Steps in CPM:
• Step 1: List all activities in the project.
• Step 2: Determine the sequence of activities and draw the network diagram.
• Step 3: Estimate the duration of each activity.
• Step 4: Calculate the Critical Path (longest path from start to finish).
• Step 5: Identify the Critical Path.
• Step 6: Update the Critical Path Diagram as the project progresses.

Key Terms:
• Earliest Start Time (EST): The earliest an activity can begin.
• Earliest Finish Time (EFT): EST + Duration.
• Latest Start Time (LST): The latest an activity can start without delaying the project.
• Latest Finish Time (LFT): LST + Duration.
• Float/Slack: LFT - EFT (zero float means activity is on critical path).

Q3.11: What is risk management? Explain the steps involved.

• Risk management is the process of identifying, assessing, and prioritizing risks followed by
coordinated application of resources to minimize, monitor, and control the probability or impact
of unfortunate events.

Steps in Risk Management:

• Risk Identification: Identify all possible risks that could affect the project. Types: technical risks,
project risks, business risks, and product risks.
 • Risk Assessment/Analysis: Assess the probability and impact of each risk. Risk Exposure =
Probability x Impact.
• Risk Planning: Develop strategies to deal with each risk: Avoidance (eliminate risk), Reduction
(reduce probability or impact), Transference (transfer risk to third party), Acceptance (accept the
consequences).
• Risk Monitoring: Continuously monitor risks and check whether risk factors are changing.
Review risks at each project milestone.
• Risk Control: Take corrective action when risk monitoring indicates risk is becoming a problem.

Q3.12: Explain PERT technique with example.

• PERT (Program Evaluation and Review Technique) is a statistical tool used in project
management to analyze and represent the tasks involved in completing a given project.
• PERT was developed by the US Navy in 1958 for the Polaris missile project.
• Unlike CPM which uses a single time estimate, PERT uses three time estimates for each
activity.

Three Time Estimates in PERT:

• Optimistic time (to): Minimum time if everything goes perfectly well.
• Most likely time (tm): The most realistic time estimate under normal conditions.
• Pessimistic time (tp): Maximum time if everything goes wrong.
• Expected time (te) = (to + 4tm + tp) / 6
• Standard deviation (sigma) = (tp - to) / 6

Difference between PERT and CPM:

• PERT uses three time estimates (optimistic, most likely, pessimistic); CPM uses single time
estimates.
• PERT is event-oriented; CPM is activity-oriented.
• PERT is used for research & development projects with uncertain durations; CPM is used for
construction and well-defined projects.
• PERT is probabilistic; CPM is deterministic.

UNIT 4 — Project Management and Control (Answers)

Q4.3: What are the methods of visualizing project progress?

A. Gantt Chart:
• Named after Henry Gantt (1861-1919).
• Simplest and oldest technique for tracking project progress.
• Indicates scheduled activity dates and durations.
• Reported progress is recorded on the chart by shading activity bars.

B. Slip Chart:
• A version of the Gantt chart where a line is drawn from top to bottom.
• To the left of the line are all completed activities; to the right are those not yet completed.
• Provides more striking visual indication of activities not progressing to schedule.
• The more the slip line bends, greater variation from the plan.
C. The Timeline:
• Records the way that targets have changed throughout the project.
• Planned time is plotted on the horizontal axis and actual time on the vertical axis.
• The bendy lines from top to bottom represent the scheduled completion date for each activity.

Q4.4: What is Earned Value Analysis (EVA)? Explain with formulas.

• Earned Value Analysis (EVA) is a project management technique for measuring project
performance and progress in an objective manner.
• EVA integrates scope, schedule, and cost to provide an objective measure of project progress.

Key EVA Terms and Formulas:

• Planned Value (PV) / BCWS: Budgeted Cost of Work Scheduled — what was planned to be
done by a certain point.
• Earned Value (EV) / BCWP: Budgeted Cost of Work Performed — value of the work actually
completed.
• Actual Cost (AC) / ACWP: Actual Cost of Work Performed — actual money spent.
• Budget at Completion (BAC): Total approved budget for the project.
• Schedule Variance (SV) = EV - PV. Positive = ahead of schedule; Negative = behind schedule.
• Cost Variance (CV) = EV - AC. Positive = under budget; Negative = over budget.
• Schedule Performance Index (SPI) = EV / PV. >1 = ahead of schedule; <1 = behind.
• Cost Performance Index (CPI) = EV / AC. >1 = under budget; <1 = over budget.
• Estimate at Completion (EAC) = BAC / CPI.
• Estimate to Complete (ETC) = EAC - AC.

Q4.9: What is Software Configuration Management (SCM)?

• Software Configuration Management (SCM) is a set of activities designed to control change by

identifying the work products that are likely to change, establishing relationships among them,
defining mechanisms for managing different versions, controlling the changes imposed and
auditing and reporting on the changes made.
• SCM is a part of software quality assurance.

Activities in SCM:
• Configuration Identification: Identify all items (documents, code, data) that form part of the
software configuration. Each item is given a unique identifier.
• Configuration Control: Process of evaluating, approving or disapproving, and coordinating
changes to configuration items.
• Configuration Status Accounting: Recording and reporting of the information needed to manage
a configuration effectively.
• Configuration Audit: Verification that a configuration item conforms to its specified requirements
and that the configuration management process is being followed correctly.

Benefits of SCM:
• Controlled and traceable changes.
• Systematic management of versions.
• Ability to reproduce past versions.
• Reduction in errors caused by changes.
• Improved team coordination.
 Q4.18: What are the issues faced in contract management?

• Contract Execution: Poor contract management often leads to lost or missing files, and final
contract approvals and signatures take significantly longer to obtain.
• Contract Tracking: Monitoring and tracking signed contracts that are passed along to other team
members or departments who may not be familiar with them is crucial to avoiding delays.
Project delays lead to project overspending.
• Contract Revisions: Managing contract changes before and after contract approval is important
to project success.
• Contract Compliance: Contracts help ensure compliance within the parameters agreed upon.
Effective contract management establishes compliance and regulation across the project.

UNIT 5 — Staffing in Software Projects (Answers)

Q5.4: What is motivation? Explain different motivation theories.

• Motivation is the reason why a person engages in a particular behavior. In the workplace,
motivation refers to the forces that direct and drive employees to achieve goals.

Maslow's Hierarchy of Needs:

• Abraham Maslow proposed that human needs can be arranged in a hierarchy of five levels.
• Physiological needs: Basic needs — food, water, shelter, sleep.
• Safety needs: Security, stability, freedom from fear.
• Social needs: Belonging, love, friendship, acceptance.
• Esteem needs: Achievement, recognition, respect, status.
• Self-actualization needs: Realizing full potential, creativity, problem-solving.
• Lower-level needs must be satisfied before higher-level needs motivate behavior.

Herzberg's Two-Factor Theory:

• Frederick Herzberg identified two categories of factors affecting motivation.
• Hygiene factors (dissatisfiers): Company policy, supervision, salary, working conditions.
Absence causes dissatisfaction but presence does NOT motivate.
• Motivators (satisfiers): Achievement, recognition, work itself, responsibility, advancement,
growth. Presence motivates and gives satisfaction.

Q5.5: Explain the Oldham-Hackman job characteristic model.

• The Oldham-Hackman Job Characteristic Model (also called the Job Characteristics Model) was
developed by J. Richard Hackman and Greg Oldham in 1976.
• The model proposes that three critical psychological states lead to high motivation, high
performance, and high satisfaction.

Five Core Job Dimensions:

• Skill variety: The degree to which the job requires use of different skills and talents.
• Task identity: The degree to which the job requires completing a whole and identifiable piece of
work.
• Task significance: The degree to which the job has a substantial impact on the lives of others.
 • Autonomy: The degree to which the job gives the employee substantial freedom, independence,
and discretion.
• Feedback: The degree to which carrying out the activities gives the employee direct and clear
information about their performance.

Three Critical Psychological States:

• Experienced meaningfulness of work (from skill variety, task identity, task significance).
• Experienced responsibility for outcomes (from autonomy).
• Knowledge of actual results (from feedback).
• Motivating Potential Score (MPS) = [(Skill variety + Task identity + Task significance)/3] x
Autonomy x Feedback.

Q5.13: What are organizational structures used in software projects?

1. Functional Organization:
• Work is divided by specialization — departments are created based on function (e.g., design,
development, testing).
• Advantages: Deep expertise in each area, clear career paths, efficient use of resources.
• Disadvantages: Poor cross-functional coordination, project manager has limited authority.

2. Project-Based (Projectized) Organization:

• Teams are organized entirely around projects. Project managers have full authority over
resources.
• Advantages: Clear project focus, strong team identity, fast decision-making.
• Disadvantages: Duplication of resources, team members may feel insecure about job continuity
after project ends.

3. Matrix Organization:
• Combination of functional and project organizations. Employees report to both a functional
manager and a project manager.
• Types: Weak matrix (functional manager has more authority), Balanced matrix (equal authority),
Strong matrix (project manager has more authority).
• Advantages: Efficient use of resources, cross-functional knowledge sharing.
• Disadvantages: Dual reporting can create confusion, potential conflict between managers.

Q5.14: What are dispersed and virtual teams? How are they managed?

• A dispersed team is a team whose members are located in different physical locations but work
together on common goals.
• A virtual team is a group of people who work independently with shared purpose across space,
time, and organizational boundaries using technology to communicate and collaborate.

Challenges of Virtual Teams:

• Lack of face-to-face communication.
• Time zone differences.
• Cultural differences.
• Technology issues.
• Reduced team cohesion and trust.
Managing Virtual Teams:
• Establish clear communication protocols and channels.
• Use collaboration tools (video conferencing, project management tools, shared drives).
• Set clear expectations and goals.
• Schedule regular virtual meetings.
• Build trust through transparency and accountability.
• Celebrate team successes to build team spirit.
• Be sensitive to cultural differences.

Q5.17: What is leadership in software project management?

• Leadership in software project management is the ability to guide, inspire, and influence a team
toward achieving project goals.
• A project leader must have technical knowledge, interpersonal skills, and the ability to make
decisions under uncertainty.

Leadership Styles:
• Autocratic: Leader makes decisions without consulting team members. Effective in crisis
situations but lowers morale.
• Democratic/Participative: Leader involves team in decision-making. Builds morale, encourages
creativity but can be slow.
• Laissez-faire: Leader gives team complete freedom to make decisions. Effective with highly
skilled, self-motivated teams.
• Transformational: Leader inspires and motivates team to achieve more than they thought
possible. Focuses on vision and change.
• Transactional: Based on reward and punishment. Clear expectations set; performance
rewarded or penalized accordingly.

Qualities of a Good Project Leader:

• Clear communication skills.
• Ability to motivate and inspire team members.
• Decision-making and problem-solving skills.
• Ability to manage conflict.
• Technical competence.
• Adaptability and flexibility.

END OF STUDY GUIDE — Best of luck in your SPM exams!