Chapter1:
1. define Project Management and Explain characteristics of Project Management.
2. Explain some important measurement in project management
3. What are different knowledge areas of project management
4. Explain the different phases of project management lifecycle
Chapter 2:
1. What is Project charter in software Project management and explain its key
elements
2. What are different steps used in project initiation phase
3. What is work breakdown structure with its different types and different ways to
reinforce it
4. Describe different steps used for scope verification and ways to process the change
control process
Chapter 3:
1. What is importance of activity definition and different types of dependencies
2. What are different cost estimation technique and how to calculate final estimate
using standard deviation
3. What is Earn Value Management, and how does it contribute to project performance,
assessment and control
Chapter 1 – Introduction to Project
Management
Q1) Define Project Management and Explain characteristics of Project
Management.
● Definition
Project Management is the structured process of planning, organizing, executing,
and controlling activities to achieve specific goals within constraints such as time,
cost, scope, and quality. It ensures that projects deliver value and meet stakeholder
expectations.
● Characteristics of Project Management
1. Goal-Oriented
○ Every project exists to achieve a specific goal or objective.
○ Example: Developing a Student Attendance App within 4 months.
2. Temporary Nature
○ Projects are not ongoing operations, they have a clear start date and end
date.
○ Once the objectives are met, the project is closed.
3. Unique Deliverables
○ Each project creates a unique product, service, or result.
○ Example: Two colleges may both build attendance systems, but features
differ.
4. Progressive Elaboration
○ Project plans become more detailed as work progresses.
○ Example: Initially broad requirements → later detailed coding tasks.
5. Resource Constraints
○ Every project has limited resources like budget, manpower, technology, and
time.
○ Managers must allocate them efficiently.
6. Risk & Uncertainty
○ Projects always face risks such as budget overruns, delays, or technical
failures.
○ Risk management is a crucial part of project management.
Q2) Explain some important measurement in project management.
● Measurement is important to track success and ensure the project meets
objectives.
1. Scope Measurement
○ Determines whether all required deliverables are included.
○ Prevents “scope creep” (unwanted additions).
○ Example: A client only asks for Android app, not iOS.
2. Time Measurement
○ Compares planned schedule vs. actual progress.
○ Tools: Gantt Chart, PERT, CPM.
○ Example: Task planned for 10 days but completed in 15 → delay identified.
3. Cost Measurement
○ Tracks whether expenses are within the approved budget.
○ Example: Project estimated ₹10 lakh but actual cost ₹12 lakh → over-budget.
4. Quality Measurement
○ Checks if project outputs meet required quality standards.
○ Example: Testing a software app to ensure fewer than 2 critical bugs.
5. Performance Indicators
○ Earned Value (EV), Cost Performance Index (CPI), Schedule Performance
Index (SPI).
○ Help forecast future performance and ensure corrective actions.
Q3) What are different knowledge areas of Project Management?
The PMBOK (Project Management Body of Knowledge) defines 10 knowledge areas:
1. Integration Management
○ Ensures all project parts work together.
○ Example: Balancing scope, cost, and schedule.
2. Scope Management
○ Defines project boundaries (what’s included and excluded).
○ Prevents scope creep.
3. Time Management
○ Plans and controls schedule.
○ Example: Using CPM to identify critical path tasks.
4. Cost Management
○ Involves budget planning and controlling costs.
○ Example: Allocating ₹5 lakh for development.
5. Quality Management
○ Ensures deliverables meet client expectations.
○ Example: ISO standards, testing strategies.
6. Human Resource Management
○ Assigns roles, responsibilities, and manages team conflicts.
○ Example: Project manager, developers, testers.
7. Communication Management
○ Ensures effective communication among stakeholders.
○ Example: Weekly status reports, meetings.
8. Risk Management
○ Identifies risks and develops mitigation plans.
○ Example: Risk of server failure → backup plan created.
9. Procurement Management
○ Involves buying products/services from vendors.
○ Example: Purchasing cloud hosting or outsourcing UI design.
10.Stakeholder Management
● Identifies stakeholders and manages expectations.
● Example: Keeping sponsors updated on progress.
Q4) Explain the different phases of Project Management Lifecycle.
The Project Life Cycle has 5 phases:
1. Initiation Phase
○ Identifies project purpose, scope, and feasibility.
○ Creates Project Charter.
○ Example: Approving the creation of a Library Management System.
2. Planning Phase
○ Creates a detailed roadmap for execution.
○ Includes WBS, scheduling, resource allocation, risk analysis.
○ Example: Assigning deadlines for UI, Backend, and Testing.
3. Execution Phase
○ Work is performed according to the plan.
○ Resources are allocated, deliverables created.
○ Example: Coding modules, testing functionalities.
4. Monitoring & Controlling Phase
○ Compares planned vs. actual progress.
○ Ensures cost, schedule, and quality are maintained.
○ Example: Project manager checks delays and adjusts resources.
5. Closing Phase
○ Final deliverables are handed over.
○ Client acceptance and documentation.
○ Example: Deploying software and conducting user training.
Chapter 2 – Project Initiation and Scope
Management
Q1) What is Project Charter in Software Project Management and explain its key
elements?
● Definition:
A Project Charter is a formal document that authorizes the existence of a project.
○ It provides the project manager authority to use resources.
○ It serves as a reference document throughout the life cycle.
● Purpose:
○ Defines what the project is about, why it is needed, and who is responsible.
○ Acts as a contract between stakeholders and project team.
● Key Elements of a Project Charter:
1. Project Title & Description – Name and short summary.
○ Example: “Library Management System – to automate book lending.”
2. Project Purpose/Business Case – Why the project is needed.
○ Example: Reduce manual work and improve efficiency.
3. Objectives & Success Criteria – Measurable outcomes.
○ Example: Complete within 6 months, budget ≤ ₹5 lakh.
4. Scope Statement – Defines boundaries of the project.
5. Major Deliverables – Tangible outcomes like software, documentation, training.
6. Budget & Time Estimates – Approximate resources required.
7. Risks & Constraints – Time limits, budget limitations, technical issues.
8. Stakeholders & Roles – Sponsors, project manager, team, end users.
Q2) What are different steps used in Project Initiation Phase?
● The Initiation Phase is the first stage of the project life cycle.
● It ensures the project is feasible and worth investing in.
Steps in Project Initiation:
1. Identify Project Needs/Opportunities
○ Why the project should be started.
○ Example: College needs a system to handle online exams.
2. Conduct Feasibility Study
○ Technical, financial, and operational feasibility.
○ Example: Is existing infrastructure enough for online exams?
3. Define Objectives and Scope
○ Clear goals with measurable success criteria.
○ Example: “System should support 1000 students simultaneously.”
4. Identify Stakeholders
○ Who is involved and affected.
○ Example: Students, teachers, IT staff, management.
5. Prepare Project Charter
○ Formal approval document is created.
6. Approval/Authorization
○ Management or sponsor approves the project to move forward.
Q3) What is Work Breakdown Structure (WBS) with its different types and
different ways to reinforce it?
● Definition:
A Work Breakdown Structure (WBS) is a hierarchical decomposition of project work
into smaller, manageable tasks.
○ It ensures all work is covered and nothing is missed.
○ It forms the foundation for planning, scheduling, and costing.
● Types of WBS:
1. Deliverable-Oriented WBS
○ Based on outputs/products.
○ Example: For an app – Modules → UI, Backend, Database, Testing.
2. Phase-Oriented WBS
○ Based on project life cycle phases.
○ Example: Initiation → Planning → Execution → Closing.
3. Responsibility-Oriented WBS
○ Based on departments/teams.
○ Example: Development Team, QA Team, Support Team.
● Ways to Reinforce WBS:
1. Graphical Tree Structure – Visual hierarchical diagram.
2. Outline Numbering – 1.1, 1.2.1 style.
3. Tabular or Text-based Lists – Written breakdown of tasks.
4. Mind Maps – Used in agile/creative projects for brainstorming.
Example (Graphical WBS for Online Exam System):
Online Exam System
├── User Interface
├── Backend
│ ├── Authentication
│ ├── Question Bank
│ └── Results Module
├── Database
└── Testing
●
Q4) Describe different steps used for Scope Verification and ways to process
the Change Control Process.
● Scope Verification:
Ensures project deliverables are formally accepted by the client/stakeholders.
Steps for Scope Verification:
1. Review Deliverables – Compare work done vs. requirements.
2. Inspections and Testing – Conduct walkthroughs, demos, and QA checks.
3. Client Acceptance – Stakeholders approve deliverables formally.
4. Documentation – Sign-off documents for record-keeping.
● Change Control Process:
Projects often face changes in scope, cost, or time. Change control ensures they are
handled systematically.
Steps in Change Control Process:
1. Identify the Change Request – Any stakeholder can propose.
2. Log the Request – Document it in change request forms.
3. Analyze Impact – Check effect on schedule, cost, quality, and risks.
4. Review by Change Control Board (CCB) – Approve, reject, or defer.
5. Update Project Plan – Modify scope, cost, or timeline accordingly.
6. Communicate the Change – Inform all stakeholders.
7. Implement and Monitor – Ensure change is executed properly.
● Example:
If client requests a new payment gateway integration after development begins:
○ Team must assess extra cost and delay.
○ If approved → Update plans
○ If rejected → Stay with original scope.
Chapter 3
1) Importance of Activity Definition & Different Types of Dependencies
Definition:
● Activity definition is the process of identifying and documenting all activities
required to complete the project deliverables.
● It ensures clarity of work, proper resource allocation, and scheduling.
Importance:
● Provides a clear roadmap of what needs to be done.
● Helps in estimating time, cost, and resources accurately.
● Acts as a foundation for scheduling tools like Gantt charts, CPM, and PERT.
● Avoids confusion, duplication of effort, and scope creep.
Types of Dependencies (Logical Relationships):
1. Finish-to-Start (FS): Task B can only start after Task A finishes.
Example: Coding must finish before Testing starts.
2. Start-to-Start (SS): Task B can start only when Task A starts.
Example: Frontend and Backend development may start together.
3. Finish-to-Finish (FF): Task B can finish only when Task A finishes.
Example: Documentation and User Manual must finish together.
4. Start-to-Finish (SF): Task B can finish only when Task A starts (rare).
Example: A new shift must start before the old shift ends in operations.
2) Different Cost Estimation Techniques & Final Estimate Using Standard
Deviation
Definition:
● Cost estimation is predicting the financial resources required to complete a project.
● It ensures budget planning, monitoring, and financial feasibility.
Techniques:
1. Analogous Estimation (Top-down):
○ Based on previous project experience.
○ Example: “Last app cost ₹5 lakh, this one is similar → around ₹5–6 lakh.”
2. Parametric Estimation:
○ Uses mathematical/statistical models.
○ Example: Cost per line of code, cost per square foot in construction.
3. Bottom-up Estimation:
○ Estimate each activity separately → aggregate to total.
○ More accurate but time-consuming.
4. Three-Point Estimation (PERT method):
○ Uses Optimistic (O), Pessimistic (P), and Most Likely (M).
○ Formula: TE = (O + 4M + P) / 6
5. Expert Judgment:
○ Consulting experts for rough estimation.
Final Estimate with Standard Deviation (σ):
● Standard Deviation formula: σ = (P – O) / 6
● Helps measure uncertainty/risk in the estimate.
● Example: If O = 10 days, M = 12 days, P = 16 days →
○ TE = (10 + 4×12 + 16)/6 = 12.67 days
○ σ = (16 – 10)/6 = 1 day
→ So actual time may vary: TE ± σ (≈ 11.7 to 13.7 days).
3) Earned Value Management (EVM) – Contribution to Project Performance
Definition:
● EVM is a project management technique that measures project performance and
progress using scope, time, and cost.
● It integrates planned and actual performance.
Key Components:
1. Planned Value (PV): Budgeted cost for work planned till date.
2. Earned Value (EV): Budgeted cost of work actually completed.
3. Actual Cost (AC): Actual money spent till date.
Performance Metrics:
● Cost Variance (CV) = EV – AC → Positive = under budget.
● Schedule Variance (SV) = EV – PV → Positive = ahead of schedule.
● Cost Performance Index (CPI) = EV / AC → Efficiency of cost.
● Schedule Performance Index (SPI) = EV / PV → Efficiency of time.
Contribution:
● Provides early warning signals if project is over budget/behind schedule.
● Helps in forecasting project completion (time & cost).
● Ensures better decision making & control.
● Example: If EV < PV → project is behind schedule. If EV < AC → overspending.
