41. What is the triple constraint in project management?
- The three constraints of People, Process, and Product that every project must manage
- The interdependent relationship between Scope, Time (Schedule), and Cost (Budget) — changing one constraint affects the others, and quality is often at the center
- The three types of project risks: technical, financial, and organizational risks
- Three mandatory documents: project charter, project plan, and project closure report
Answer : B Explanation: The Triple Constraint (also called the Iron Triangle or Project Management Triangle) represents the three competing demands that every project must balance: Scope (what is to be delivered — features, requirements), Time (how long it takes — schedule, deadline), and Cost (how much it costs — budget, resources). These three are interdependent: if scope increases without more time or money, quality suffers. If the deadline is shortened without reducing scope, costs must increase or quality decreases. Quality is often shown at the center of the triangle as the outcome of balancing all three. The triple constraint is the most fundamental concept in project management.
42. What is risk management in software project management?
- The process of eliminating all possible risks before a software project begins
- The systematic process of identifying, analyzing, prioritizing, and responding to potential threats and opportunities that could affect project objectives
- A process of managing only financial risks associated with software development costs
- The testing process that identifies risks in the final software product before delivery
Answer : B Explanation: Risk Management involves proactively dealing with uncertainty in projects. The process includes: Risk Identification (finding potential risks using techniques like brainstorming, checklists, SWOT analysis), Risk Analysis — Qualitative (assessing probability and impact, creating a Risk Matrix) and Quantitative (numerical analysis using Monte Carlo simulation, decision trees), Risk Prioritization (focusing on high-probability, high-impact risks), Risk Response Planning (four strategies: Avoid, Transfer, Mitigate, Accept for threats; Exploit, Share, Enhance, Accept for opportunities), and Risk Monitoring and Control (tracking risks throughout the project). The Risk Register documents all identified risks and their responses.
43. What is a milestone in project management?
- A detailed task in the project schedule with an assigned team member and deadline
- A significant point or event in the project timeline that marks the completion of a major deliverable or phase, used to track progress and communicate achievements to stakeholders
- A project management metric that measures the distance traveled toward project goals
- A financial checkpoint where project costs are reviewed and approved by management
Answer : B Explanation: A milestone is a zero-duration marker in the project schedule that signifies a major achievement or decision point. Examples: “Requirements approved,” “Design complete,” “First prototype delivered,” “User acceptance testing passed,” “Go-live date.” Milestones help project managers: track progress at a high level, communicate project status to stakeholders and executives, identify schedule slippage early, trigger go/no-go decisions, and mark contract payment points. On a Gantt chart, milestones are typically shown as diamond shapes. They differ from tasks in that tasks have duration and consume resources; milestones are instantaneous markers.
44. What is the Spiral model in software development?
- A linear development model that spirals through the same phases multiple times
- A risk-driven software development model that combines iterative development with systematic risk assessment, progressing through planning, risk analysis, engineering, and evaluation in repeated cycles
- A model used specifically for developing spiral-shaped user interface components
- A project management model where team members rotate roles in a spiral sequence
Answer : B Explanation: The Spiral Model, proposed by Barry Boehm in 1986, is a risk-driven, iterative development model. Each loop of the spiral represents a phase and consists of four sectors: Planning (determine objectives, alternatives, constraints), Risk Analysis (identify and resolve risks, prototype development), Engineering (develop and test the product), and Evaluation (customer evaluation and planning for next iteration). The spiral grows outward with each iteration. The key differentiator from other models is its explicit focus on risk analysis at every iteration. It is best suited for large, complex, high-risk projects where requirements are uncertain or likely to evolve.
45. What is Kanban in project management?
- A Japanese project management methodology focused only on hardware manufacturing
- A visual Agile workflow management method that uses a board with columns (To Do, In Progress, Done) to visualize work, limit work-in-progress, and optimize flow
- A project management tool used exclusively for financial budget tracking
- A sequential waterfall-like methodology with a strict phase gate review process
Answer : B Explanation: Kanban (Japanese for “visual signal” or “card”) originated in Toyota’s manufacturing system and was adapted for software development by David Anderson. Core principles: Visualize the workflow (using a Kanban board with columns representing stages), Limit Work-In-Progress (WIP limits prevent overloading), Manage flow (optimize how work moves through the system), Make process policies explicit, Implement feedback loops, and Improve collaboratively. Unlike Scrum, Kanban has no fixed iterations or roles — work is pulled as capacity allows. Kanban is ideal for maintenance, support, and operations teams with continuous incoming work.
46. What is Earned Value Management (EVM) in project management?
- A method for calculating the monetary value that a project will earn after completion
- A project performance measurement technique that integrates scope, schedule, and cost to objectively assess project progress using metrics like CV, SV, CPI, and SPI
- A financial accounting technique for recording project revenues and expenses
- A customer satisfaction measurement tool that evaluates the earned value of delivered features
Answer : B Explanation: EVM measures project performance using three key values: Planned Value (PV) — the budgeted cost of work scheduled, Earned Value (EV) — the budgeted cost of work actually performed, and Actual Cost (AC) — the actual cost of work performed. Key metrics: Cost Variance (CV) = EV – AC (negative = over budget), Schedule Variance (SV) = EV – PV (negative = behind schedule), Cost Performance Index (CPI) = EV/AC (less than 1 = over budget), Schedule Performance Index (SPI) = EV/PV (less than 1 = behind schedule). EVM enables objective, data-driven project performance reporting and forecasting.
47. What is the purpose of a project charter in project management?
- A detailed technical specification document listing all software features to be developed
- A formal document that officially authorizes a project, defines its objectives, scope, and stakeholders, and grants the project manager authority to apply organizational resources
- A contract between the software development team and the end users of the system
- A daily status report submitted by the project manager to senior management
Answer : B Explanation: The Project Charter is the first formal project document — it officially initiates the project and provides the project manager with the authority to use organizational resources. Key contents include: project purpose and justification, high-level requirements and scope, project objectives and success criteria, identified risks, summary milestone schedule, summary budget, key stakeholders, and project manager assignment and authority level. The charter is created during the Initiating process group and signed by the project sponsor. Without a charter, the project lacks formal authorization — it is essentially the project’s “birth certificate.”
48. What is the difference between project scope and product scope?
- Project scope refers to software features; product scope refers to project timelines
- Product scope defines the features and functions of the deliverable; project scope defines the work required to deliver the product — including all activities, processes, and project management tasks
- Project scope is defined by the customer; product scope is defined by the developer
- Both terms refer to the same concept and are used interchangeably in PMBOK
Answer : B Explanation: Product Scope describes the features, functions, and characteristics that a product must have — measured against the product requirements. Example: “The software shall support 10,000 concurrent users.” Project Scope describes all the work that must be performed to deliver the product — measured against the project management plan. Example: “Conduct user testing with 50 participants.” Scope creep — the uncontrolled expansion of scope without adjusting time, cost, or resources — is one of the most common causes of project failure. The WBS is the primary tool for defining and managing project scope.
49. What is stakeholder management in project management?
- A process of hiring and firing project team members based on project performance
- The process of identifying all people or organizations affected by a project, analyzing their interests and influence, and developing strategies to effectively engage them throughout the project
- A technique for managing conflicts between different software development teams
- A financial process of managing payments to external vendors and contractors
Answer : B Explanation: Stakeholder management is critical to project success. The process: Identify Stakeholders (who is affected by or can affect the project — customers, sponsors, end users, regulators, team members), Analyze stakeholders (their interests, power, influence — using a Power/Interest Grid), Plan Stakeholder Engagement (strategies for communicating and involving each stakeholder), Manage Engagement (actively working with stakeholders, resolving issues, managing expectations), and Monitor Engagement (tracking stakeholder attitudes and adjusting strategies). Poor stakeholder management is one of the leading causes of project failure — requirements misalignment, insufficient buy-in, and resistance to change are common results.
50. What is the Agile Manifesto and what are its four core values?
- A legal document signed by software companies committing to agile development practices
- A declaration published in 2001 by 17 software practitioners that defines the values and principles of Agile software development: Individuals and interactions, Working software, Customer collaboration, and Responding to change — each valued over its counterpart
- A project charter template specifically designed for agile software development projects
- A government regulation mandating agile practices for all federal software projects
Answer : B Explanation: The Agile Manifesto was published in February 2001 by 17 software developers at a ski resort in Utah. Its four values: (1) Individuals and interactions over processes and tools, (2) Working software over comprehensive documentation, (3) Customer collaboration over contract negotiation, (4) Responding to change over following a plan. Importantly, the manifesto states “while there is value in the items on the right, we value the items on the left more” — it doesn’t reject the right-side items entirely. The manifesto also includes 12 supporting principles. It has fundamentally changed software development globally, spawning numerous frameworks (Scrum, Kanban, XP, SAFe).
