91. What is the difference between black-box testing and white-box testing?
- Black-box testing uses dark themes in the testing tool; white-box uses light themes
- Black-box testing tests software functionality without knowledge of internal code structure; white-box testing tests internal logic, code paths, and structure with full knowledge of the source code
- Black-box testing is performed by developers; white-box testing is performed by customers
- White-box testing can only test web applications; black-box testing works for all types
Answer : B Explanation: Black-Box Testing (Behavioral/Functional Testing): treats the software as a “black box” — the tester only knows what the system should do, not how it does it. Tests are based on requirements and specifications. Techniques: Equivalence Partitioning, Boundary Value Analysis, Decision Table Testing. Performed by QA testers or end users. White-Box Testing (Glass-Box/Structural Testing): tests the internal logic, code paths, branches, and conditions. Requires knowledge of the source code. Techniques: statement coverage, branch coverage, path coverage. Typically performed by developers. Gray-Box Testing combines both — partial knowledge of internal structure. Both are necessary for comprehensive software quality.
92. What is the purpose of a Burndown Chart in Scrum?
- A chart that tracks the number of bugs burned (fixed) during a testing sprint
- A visual graph that shows the amount of remaining work in a sprint or release over time, with the ideal trend line showing linear progress to zero — helping teams see if they are on track to complete their sprint goal
- A financial chart tracking how quickly the project budget is being consumed
- A chart showing the number of team members who have left (burned out) during a project
Answer : B Explanation: The Burndown Chart is a common Agile visualization tool. The X-axis shows time (sprint days), and the Y-axis shows remaining work (story points or hours). An “ideal” diagonal line shows what progress should look like if work is completed evenly. The actual burndown line shows real progress. Interpretation: if the actual line is above the ideal line, the team is behind; if below, they are ahead. Variations: Sprint Burndown (remaining work in the current sprint), Release Burndown (remaining work in the release). The Burnup Chart is an alternative that shows completed work growing toward the sprint goal — it also makes scope changes visible. Both are highly transparent communication tools.
93. What is the purpose of a lessons learned document in project management?
- A training document that teaches new team members the project’s technical stack
- A formal document created during or after a project that captures what went well, what went wrong, and recommendations for improving future projects — building organizational knowledge
- A legal document recording all mistakes made during a project for liability purposes
- A personal journal kept by the project manager to document daily project activities
Answer : B Explanation: Lessons Learned (also called Post-Mortem or Post-Project Review) is one of the most valuable but frequently skipped project management activities. It captures: what went well and should be repeated, what went poorly and should be avoided or improved, specific recommendations for future projects, and quantitative data (actual vs. planned performance). Best practice: conduct lessons learned throughout the project (not just at the end), keep the tone constructive (blame-free focus on improvement), and ensure lessons are stored in an accessible organizational knowledge repository. Future project teams can reference lessons learned during planning to avoid repeating mistakes and replicate successes.
94. What is the concept of a project portfolio in project management?
- A collection of all the documents and reports produced during a single project
- A collection of projects, programs, subsidiary portfolios, and operations managed as a group to achieve strategic objectives — prioritized and balanced to optimize organizational value delivery
- A portfolio of skills and certifications held by the project manager
- A financial portfolio of stocks and bonds used to fund multiple software projects
Answer : B Explanation: Portfolio Management operates at the highest strategic level, above programs and projects. The Portfolio Manager: selects and prioritizes projects based on strategic alignment and ROI, balances the portfolio across risk, time horizon, and resource demands, monitors the collective performance of all portfolio components, and adjusts the portfolio as strategic objectives change. The governance framework: Portfolio (strategic) → Program (tactical benefits) → Project (operational deliverables). PMI’s Standard for Portfolio Management provides guidelines. Portfolio management answers “Are we doing the right projects?” while project management answers “Are we doing our project right?”
95. What is the Delphi technique in project management?
- A Greek mythology-inspired decision-making ceremony used in organizational change management
- A structured forecasting and estimation technique that collects expert opinions anonymously through multiple rounds, sharing summarized results after each round until consensus is reached
- A software testing technique developed by Oracle for database application testing
- A conflict resolution technique where a neutral third party makes final decisions
Answer : B Explanation: The Delphi Technique is used for expert estimation and risk identification. Process: A facilitator sends a questionnaire to a panel of experts. Experts respond anonymously (preventing group think and authority bias). Responses are summarized and shared with all experts. Experts revise their estimates based on the group summary. This repeats for 2-4 rounds until consensus emerges. The anonymity prevents dominant personalities from influencing others, encourages honest opinions, and reduces anchoring bias. Used for: risk identification, project cost estimation, technology forecasting, and policy decision-making. Also used in Agile as “Planning Poker” — a gamified variant for story point estimation.
96. What is the difference between quality assurance and quality control in project management?
- Quality assurance is done by management; quality control is done by developers
- Quality Assurance (QA) is process-oriented — ensuring processes are followed correctly to prevent defects; Quality Control (QC) is product-oriented — inspecting and testing the actual product to find defects
- Quality control happens before quality assurance in the software development process
- Both QA and QC refer to the same activities performed by the testing team
Answer : B Explanation: Quality Assurance (QA) focuses on preventing defects by ensuring the right processes are used during development — process audits, process improvement, standards compliance, training. It is proactive and addresses the entire development process. Quality Control (QC) focuses on finding defects in the actual product through inspection and testing — code reviews, testing, inspections, walkthroughs. It is reactive and product-focused. Analogy: QA is like ensuring you have a good recipe (process); QC is like tasting the food (product). Both are essential: QA makes QC easier by reducing defect injection; QC catches any defects that escaped QA.
97. What is the role of the Product Owner in Scrum?
- The most senior developer who owns and writes all the product’s core code
- The single person accountable for maximizing the value of the product by managing and prioritizing the Product Backlog, representing stakeholder interests, and ensuring the team builds the most valuable features first
- An external customer representative who attends only the Sprint Review meetings
- A project manager role responsible for tracking sprint velocity and reporting to management
Answer : B Explanation: The Product Owner (PO) is one of three Scrum roles. Key responsibilities: Creating and maintaining the Product Backlog (writing and refining user stories), Prioritizing the backlog to maximize business value (highest value items at the top), Communicating the product vision and sprint goals, Collaborating with stakeholders to gather and clarify requirements, Participating in Sprint Reviews to accept or reject completed work, and Making decisions about product direction. The PO is the single point of contact for product decisions — the team should not receive conflicting direction from multiple stakeholders. The PO must be available to the team and empowered to make decisions.
98. What is the purpose of project procurement management?
- A process for procuring (hiring) new developers for the project team
- The processes of purchasing or acquiring products, services, or results needed from outside the project team — including planning procurements, conducting procurements, controlling contracts, and closing contracts
- A process for procuring project management tools and software licenses
- A technique for procuring additional budget from organizational stakeholders mid-project
Answer : B Explanation: Procurement Management deals with acquiring goods and services from external vendors. Key processes: Plan Procurement Management (what to buy, when, contract types), Conduct Procurements (select vendors through RFP/RFQ/RFI, evaluate proposals, award contracts), Control Procurements (monitor vendor performance against contract, manage changes, process invoices), and Close Procurements (verify all work is complete, formally close contracts). Contract types: Fixed Price (seller bears cost risk), Cost Reimbursable (buyer bears cost risk — Cost Plus Fixed Fee, Cost Plus Incentive Fee), and Time and Material (hybrid — used for staff augmentation). Proper procurement management protects the project from vendor risks and ensures legal compliance.
99. What is the Agile scaling framework SAFe (Scaled Agile Framework)?
- A simplified version of Agile designed for very small teams of 3-5 developers
- An enterprise-level framework for scaling Agile practices across large organizations with multiple teams working on the same product, aligning work from team level to program level to portfolio level
- A safety-focused Agile methodology used specifically in aerospace and medical device development
- A single-team Agile framework that is safer than Scrum for regulated industries
Answer : B Explanation: SAFe (Scaled Agile Framework) is the most widely adopted framework for scaling Agile beyond a single team. It organizes work at four levels: Team Level (Scrum/Kanban teams delivering every 2 weeks), Program Level (Agile Release Train — ART — multiple teams synchronized on a Program Increment — PI — typically 8-12 weeks), Large Solution Level (coordinating multiple ARTs), and Portfolio Level (strategic alignment of investments). PI Planning is a key SAFe event where all teams plan together face-to-face for 2 days. Other scaling frameworks include LeSS (Large-Scale Scrum) and Nexus. SAFe addresses challenges like cross-team dependencies, architectural alignment, and enterprise portfolio governance.
100. What is the difference between Agile and traditional (predictive) project management?
- Traditional project management is always better; Agile is only suitable for small startup projects
- Traditional (predictive) PM plans the entire project upfront with fixed scope, schedule, and cost; Agile is adaptive, embracing change, delivering value incrementally, and adjusting plans based on continuous feedback — each suits different project environments
- Agile requires more documentation and formal processes than traditional project management
- Traditional project management is newer than Agile and is gradually replacing it globally
Answer : B Explanation: Traditional (Predictive/Waterfall) PM: works best when requirements are well-defined and stable, changes are costly and rare, a detailed plan can be created upfront, and the customer can wait for the complete product. Agile PM: works best when requirements are unclear or evolving, rapid feedback is valuable, early and frequent delivery of working software is needed, and the team is small and co-located. Hybrid approaches combine both — using Agile for development while maintaining traditional governance for budget, risk, and reporting. PMI’s PMBOK 7th Edition and Disciplined Agile Delivery (DAD) now incorporate both predictive and adaptive approaches, recognizing that the best methodology depends on the project context.
