31. What is the Waterfall model in software project management?
- An iterative development model where requirements change frequently during development
- A linear, sequential software development model where each phase must be completed before the next begins — flowing downward through Requirements, Design, Implementation, Testing, Deployment, and Maintenance
- A model that allows development and testing to happen simultaneously at all times
- An agile framework that uses sprints to deliver working software incrementally
Answer : B Explanation: The Waterfall model is the oldest and most traditional software development methodology. It is linear and sequential — each phase (Requirements, System Design, Implementation, Testing, Deployment, Maintenance) must be fully completed before the next begins, like water flowing downward. Advantages: simple, well-documented, easy to manage for stable projects. Disadvantages: inflexible to changing requirements, late testing means bugs are found late, and customers don’t see the product until the end. Waterfall is best suited for projects with clearly defined, fixed requirements where changes are unlikely.
32. What is Agile methodology in software project management?
- A rigid sequential development approach that freezes requirements at the start of a project
- An iterative and incremental approach to software development that emphasizes flexibility, collaboration, customer feedback, and delivering working software in short cycles called sprints or iterations
- A project management method used exclusively for hardware development projects
- A documentation-heavy approach that requires extensive planning before any coding begins
Answer : B Explanation: Agile is a set of principles for software development outlined in the Agile Manifesto (2001), which values: Individuals and interactions over processes and tools, Working software over comprehensive documentation, Customer collaboration over contract negotiation, and Responding to change over following a plan. Agile breaks work into short iterations (typically 1-4 weeks), delivering working software at the end of each. It embraces changing requirements even late in development. Popular Agile frameworks include Scrum, Kanban, XP (Extreme Programming), and SAFe. Agile is now the dominant methodology in modern software development.
33. What is Scrum in project management?
- A waterfall-based project management methodology used for hardware projects
- An Agile framework that organizes work into fixed-length iterations called Sprints (typically 2-4 weeks), with defined roles (Scrum Master, Product Owner, Development Team) and ceremonies (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective)
- A project management tool used only for tracking software bugs and defects
- A sequential development approach where one team member works on the project at a time
Answer : B Explanation: Scrum is the most widely used Agile framework. Key components: Roles — Product Owner (manages the product backlog and represents stakeholders), Scrum Master (facilitates the process and removes impediments), Development Team (self-organizing team that delivers the work). Artifacts — Product Backlog (ordered list of all desired work), Sprint Backlog (work selected for the current sprint), Increment (the usable working software delivered each sprint). Events — Sprint Planning, Daily Standup (15-minute daily sync), Sprint Review, Sprint Retrospective. Scrum promotes transparency, inspection, and adaptation — the three pillars of empirical process control.
34. What is the difference between Agile and Waterfall methodology?
- Agile is used for small projects only; Waterfall is used for large projects only
- Agile is iterative and flexible, welcoming changing requirements and delivering working software frequently; Waterfall is linear and sequential with fixed requirements, delivering the complete product at the end
- Waterfall is faster than Agile for all types of software development projects
- Agile requires more documentation than Waterfall in all development scenarios
Answer : B Explanation: Key differences: Agile welcomes changing requirements even late in development; Waterfall freezes requirements at the start. Agile delivers working software every 1-4 weeks; Waterfall delivers the complete product at the end. Agile involves continuous customer collaboration; Waterfall has limited customer involvement after requirements phase. Agile testing happens throughout development; Waterfall testing happens after implementation. Agile has minimal documentation; Waterfall is document-heavy. Use Agile when requirements are unclear or likely to change. Use Waterfall for well-defined, stable requirements (government contracts, construction-like projects).
35. What is a Gantt chart in project management?
- A pie chart used to show the proportion of budget spent on each project task
- A horizontal bar chart that visually represents a project schedule, showing tasks, their durations, start and end dates, dependencies, and milestones along a timeline
- A flowchart showing the logical sequence of decisions made during project planning
- A graph that tracks the number of bugs found versus bugs fixed during testing
Answer : B Explanation: A Gantt chart, developed by Henry Gantt in the 1910s, is one of the most widely used project management visualization tools. It displays: tasks as horizontal bars on a timeline, the start date, duration, and end date of each task, task dependencies (which tasks must finish before others can start), and milestones (key project checkpoints). Gantt charts help project managers plan schedules, track progress against the plan, identify delays, communicate timelines to stakeholders, and manage resource allocation. Popular tools for creating Gantt charts include Microsoft Project, Asana, Jira, and Smartsheet.
36. What is the Critical Path Method (CPM) in project management?
- A method for identifying the most critical team members needed for a project
- A scheduling algorithm that identifies the longest sequence of dependent tasks through a project network, determining the minimum project duration — any delay on the critical path delays the entire project
- A risk assessment technique that identifies the most critical risks in a project
- A cost estimation method that focuses on the most expensive tasks in a project
Answer : B Explanation: The Critical Path Method (CPM) is a network-based scheduling technique. Steps: List all project activities, identify dependencies between activities, estimate durations, draw the network diagram, calculate Early Start (ES), Early Finish (EF), Late Start (LS), and Late Finish (LF) for each activity, and identify the critical path — the longest path through the network where float/slack = 0. Activities on the critical path cannot be delayed without delaying the project. Activities not on the critical path have float (slack) — time they can be delayed without affecting the project end date. CPM helps managers know where to focus attention.
37. What is PERT (Program Evaluation and Review Technique) in project management?
- A performance evaluation technique used to assess individual team member contributions
- A statistical scheduling technique that uses three time estimates (optimistic, most likely, pessimistic) to calculate the expected duration of project activities under uncertainty
- A project estimation tool used exclusively for software maintenance projects
- A risk assessment method that evaluates threats using probability and impact ratings
Answer : B Explanation: PERT (Program Evaluation and Review Technique) was developed by the US Navy for the Polaris missile project in the 1950s. Unlike CPM (which uses single deterministic estimates), PERT accounts for uncertainty using three estimates: Optimistic (O) — best case, Most Likely (M) — most probable, and Pessimistic (P) — worst case. The PERT expected time formula is: TE = (O + 4M + P) / 6. PERT is used when activity durations are uncertain — common in R&D projects. It uses probabilistic analysis to estimate project completion probability. PERT and CPM are often combined as PERT/CPM.
38. What is a Work Breakdown Structure (WBS) in project management?
- A hierarchical chart showing the organizational structure of the project team
- A hierarchical decomposition of the total project scope into smaller, manageable components called work packages, providing a foundation for project planning, scheduling, and cost estimation
- A document listing all the risks identified during project risk assessment
- A breakdown of the project budget across different departments and cost centers
Answer : B Explanation: The Work Breakdown Structure (WBS) is one of the most important project planning tools. It decomposes the total project scope into progressively smaller deliverables until each component (work package) is small enough to be planned, estimated, and assigned. The WBS represents 100% of the project scope — nothing outside the WBS is part of the project. Benefits: makes complex projects manageable, enables accurate cost and time estimation, clarifies responsibilities, and provides a framework for tracking progress. The WBS is defined in the PMBOK Guide as a key output of the scope management process.
39. What is the Software Development Life Cycle (SDLC)?
- The lifespan of a software application from launch to decommissioning
- A structured process that defines the stages involved in developing software, typically including Planning, Requirements Analysis, System Design, Implementation, Testing, Deployment, and Maintenance
- The cycle of software licensing from purchase to renewal or expiration
- A framework used only by software testing teams to manage defect life cycles
Answer : B Explanation: The SDLC provides a systematic framework for planning, creating, testing, and delivering software. Key phases: Planning (feasibility study, resource allocation), Requirements Analysis (gathering and documenting user needs), System Design (architecture, database, UI design), Implementation (coding), Testing (unit, integration, system, acceptance testing), Deployment (releasing to production), and Maintenance (bug fixes, updates). Popular SDLC models include Waterfall, Agile, Spiral, V-Model, Incremental, and RAD. The SDLC ensures software is developed systematically, meeting quality standards and user requirements while staying within budget and schedule.
40. What is the role of a Project Manager in software project management?
- To write code and develop the software application personally
- To plan, execute, monitor, and close a project while managing scope, time, cost, quality, resources, communication, risk, and stakeholder expectations to achieve project objectives
- To test software and document all bugs found during the testing phase
- To negotiate software licenses and procure development tools for the team
Answer : B Explanation: A Project Manager (PM) is responsible for leading the project team and ensuring the project is delivered on time, within budget, and to the required quality standards. Key responsibilities include: defining project scope and objectives, creating project plans and schedules, estimating costs and managing the budget, identifying and mitigating risks, managing stakeholder communication, leading and motivating the team, monitoring progress and taking corrective actions, and closing the project formally. The PM must balance the project triple constraint — Scope, Time, and Cost — while maintaining quality. The PMP (Project Management Professional) certification from PMI is the most recognized credential.
