Which methodologies below are more flexible in nature and provide an iterative approach for project management?
Answer : C
The correct answer is C. Agile. Agile methodologies are more flexible in nature because they use iterative and incremental approaches to project management. Instead of defining all work in detail at the beginning and executing it through a rigid sequence, agile approaches allow the project team to deliver value progressively, inspect results frequently, and adapt the solution based on stakeholder feedback, emerging risks, and changing requirements. This is particularly useful in environments where uncertainty is high, requirements are expected to evolve, or early user feedback is essential. Traditional methodologies are generally more predictive and sequential, with stronger emphasis on upfront planning, baselines, and formal change control. Change management is not a project delivery methodology in this context; it is a management discipline used to control and implement changes affecting the project, product, organization, or stakeholders. Therefore, among the given options, agile is the methodology that best fits the description of being flexible and iterative. The source question set identifies ''Agile'' as the relevant choice among change management, traditional, and agile approaches.
Reference topics: agile methodology, iterative delivery, adaptive project management, traditional methodology, flexibility.
Among others, how can the project oversight be done?
Answer : A
The correct answer is A. Project oversight can be carried out through ad hoc escalations and interventions, among other mechanisms. Oversight is the governance-level observation, review, and direction applied to ensure that the project remains aligned with objectives, risks are understood, decisions are escalated appropriately, and corrective action is taken when necessary. It can include formal reviews, stage gates, assurance reviews, reporting, audits, steering committee decisions, exception handling, escalations, and targeted interventions. Ad hoc escalation is appropriate when an issue, risk, decision, or exception arises outside routine reporting cycles and requires higher-level attention. Option B is not the best answer because oversight does not mean mechanically ensuring that the plan is followed in detail under all circumstances. Projects may require controlled change, replanning, or adaptation. Option C is incorrect because appointing more than one project manager does not inherently provide oversight and may create confusion if responsibilities are not clear. Oversight should be performed through defined governance mechanisms, not by duplicating the project manager role. The uploaded source question identifies ad hoc escalations and interventions as a valid oversight method.
Reference topics: project oversight, escalation, intervention, governance review, project control, assurance.
Scenario:
Exhibix is a video game developer headquartered in Zagreb, Croatia, which is known for producing therapeutic video games for children dealing with ADHD. In order to improve users' experience, Exhibix suggested undertaking a project that would enable users to interact with the virtual content in the form of holograms through augmented reality glasses in the video games. For this project, the management decided to follow the guidelines of ISO 21502 on project management.
Prior to formalizing project management, the management of Exhibix assessed, among others, the potential impacts that the project management approach may have on both internal and external stakeholders. In addition, they determined if there were sufficient resources, both human and financial, for the formalized project management. Furthermore, during this period, the management decided to assess only the nature of previous projects, due to their successful delivery.
After formalizing project management, the project board organized a meeting during which they delegated their responsibilities to the project sponsor. Following this meeting, the project sponsor and project manager proceeded to define the project phases and their time frames. Considering the complexity of the project, the project manager suggested leaving open the possibility of overlapping certain phases of the project.
The preparations began in June, and the project manager and the team, consisting of 20 highly skilled professionals, had approximately six months to implement the project. During the implementation of the project, the project team noticed that the low maturity level of the company's project management and the limited availability of resources were likely to have a negative impact on the performance of the project. With the deadline approaching, the team was also under a lot of pressure to close the project on time.
They were confronted with numerous challenges with the AR software, which led to the extension of the deadline for the project completion. During this period, the project office assisted the project manager and the team by providing administrative support and managing information regarding the project. Following these events, the project manager and the team were able to complete the project within the new set deadline. After the project sponsor confirmed the project closure, the AR glasses were released for use.
Considering the complexity of the project, the project manager suggested leaving open the possibility of overlapping certain phases of the project. Is this acceptable?
Answer : B
Yes. It is possible for project phases to overlap when the project life cycle and management approach justify it. Project phases are used to structure work, manage decision points, organize resources, control risks, and support progressive delivery. However, phases do not always have to be strictly sequential. Depending on complexity, urgency, uncertainty, and delivery strategy, a project may use overlapping, iterative, incremental, adaptive, or hybrid approaches. In Exhibix's case, the project involves augmented reality glasses, holographic interaction, and software development for therapeutic video games. This type of project may benefit from overlapping phases because design, software development, technical validation, user experience testing, and integration may need to proceed in parallel or through repeated feedback cycles. Overlapping phases can reduce schedule duration and expose technical issues earlier, but they must be controlled carefully because they can increase rework, coordination complexity, dependency risk, and change management demands. The project manager's suggestion is therefore acceptable, provided the sponsor and governance structure maintain appropriate oversight, decision points, and controls. The key issue is not whether phases overlap, but whether the overlap is intentional, justified, authorized, and managed.
Reference topics: project life cycle, phase overlap, tailoring, complexity, adaptive delivery, phase control.
What should the project manager do, among others, to avoid exceeding the project budget?
Answer : B
The correct answer is B. To avoid exceeding the project budget, the project manager should retain records of project costs and monitor expenses. Cost control depends on accurate, timely, and traceable cost information. The project manager should compare actual costs against the approved budget, analyze variances, forecast future expenditure, review commitments, track approved changes, and take corrective action when trends indicate potential overspend. Retaining cost records also supports transparency, auditability, lessons learned, and financial reporting. Option A is incorrect because ''exploitation costs'' or post-project operational costs may need to be estimated and managed, but they cannot simply be eliminated as a budget-control technique. Option C is also incorrect because avoiding all changes at any cost is not sound project management. Some changes may be necessary, beneficial, or required for compliance, safety, quality, or value realization. The issue is not to prohibit change, but to assess cost impact, approve changes through the proper authority, and update baselines where required. PMBOK defines project cost management as the processes involved in planning, estimating, budgeting, financing, funding, managing, and controlling costs so the project can be completed within the approved budget. The source question set identifies retaining records and monitoring expenses as the correct answer.
Reference topics: cost management, budget control, cost records, expense monitoring, variance analysis, project financial control.
What is the purpose of reporting?
Answer : A
The correct answer is A. The purpose of reporting is to provide the current status, forecast, and analysis of the project. Reporting converts project management information into useful, structured communication for decision-making and control. It should explain where the project currently stands, what is expected to happen next, what variances or trends exist, and what decisions or actions may be required. Effective reports may cover scope, schedule, cost, quality, resources, risks, issues, changes, stakeholder engagement, benefits, and overall confidence. Option B is related to communication management because project communications should meet stakeholder information needs, but reporting specifically focuses on presenting project status, forecasts, and analysis. Option C is incorrect because reporting is not limited to the end of the project; it occurs throughout the project life cycle. Waiting until completion would prevent timely governance decisions, corrective actions, escalation, and stakeholder alignment. PMBOK also supports this by describing project reporting as collecting performance data, producing performance measures, and reporting and disseminating performance information. The uploaded question set identifies current status, forecast, and analysis as the reporting purpose.
Reference topics: project reporting, current status, forecasting, performance analysis, project control, stakeholder information.
Who should be consulted as part of project management progress evaluations?
Answer : A
The correct answer is A. Project management progress evaluations should consult the project sponsor, project manager, and project team because these roles collectively hold the business, management, and delivery perspectives required to assess progress accurately. The sponsor is concerned with continued justification, business alignment, benefits, risks, funding, and stakeholder expectations. The project manager is responsible for directing and controlling the project work, integrating information, reporting performance, managing issues, and recommending corrective action. The project team provides direct insight into completed work, remaining work, quality conditions, technical problems, dependencies, assumptions, and emerging risks. Consulting only governance or assurance roles would provide oversight but may miss operational delivery realities. Consulting only work package leaders would be too narrow because it would exclude business justification and integrated project control. Progress evaluation requires evidence from the people who sponsor, manage, and perform the work. PMBOK similarly describes the project team as individuals who support the project manager in performing project work to achieve objectives. The source question set lists project sponsors, project managers, and their teams as the relevant consultation group.
Reference topics: progress evaluation, project sponsor, project manager, project team, project control, integrated reporting.
Which of the following statements regarding lessons learned is correct?
Answer : B
The correct answer is B. Lessons learned should be captured, compiled, formalized, and stored. Lessons learned are a structured form of organizational knowledge that helps current and future projects improve performance and avoid repeated mistakes. They should capture what was planned, what actually happened, why variances occurred, what worked well, what failed, what actions were effective, and what recommendations should be reused or avoided. Option A is incorrect because lessons learned should not describe only what happened; they should also compare actual performance against the plan and examine causes, effects, and improvement opportunities. Option C is also incorrect because lessons should not be used only after all project activities are complete. They can and should be captured throughout the project so that the team can apply learning immediately where useful. At closure, they are consolidated and stored for future use. PMBOK recognizes a lessons learned register as a project document that records knowledge gained during a project and supports future performance improvement. The uploaded question set identifies capture, compilation, formalization, and storage as the correct statement.
Reference topics: lessons learned, knowledge management, formalization, storage, continuous improvement, project closure.