Missed Questions 6 Flashcards
You are the project manager of a large project to install 10,000 fixtures across a college campus. Your project team has been late on their assigned work, and you fear the project will be late. Which one of the following provides forecasting for the project?
- The program evaluation and review technique
- Risk analysis
- The estimate at completion
- The graphical evaluation and review technique
The estimate at completion
Overall explanation
The earned value management formula—estimate at completion (EAC)—provides forecasting for the project’s success. The program evaluation and review technique (PERT) provides time estimates, not forecasting. The graphical evaluation and review technique (GERT) provides branching and loopbacks in network diagramming, not forecasting. Risk analysis does not provide forecasting at the level that EAC does.
Paul is an agile practitioner on a newly created scrum team. During the backlog refinement meeting, a few of the team members said that one of the features in the backlog could have multiple technical approaches. When some team members believe doing it one way would be better, others lean toward the alternative. Although the feature is of high value, the team is concerned that if they do not take the correct approach, it will add risk to the project and result in serious performance problems downstream. What is the best thing for the team to do next?
- Research and document the right approach first and then start work on the feature.
- Move the feature to the end of the backlog.
- Move the feature to the start of the backlog.
- Update the risk register with the anticipated risk information and inform the stakeholders.
Move the feature to the start of the backlog.
Overall explanation
It is recommended that high business value, high-risk features/items are worked on first. While that may seem counterintuitive, the sooner this work is done, the sooner the team will mitigate the issues and unknowns, leading to a higher quality product. That way, if there is a failure, it will occur early and relatively inexpensively. Risk management is the discipline of identifying, monitoring, and limiting risks. Several approaches to risk planning and management can be taken in an agile software development project. However, a prioritization process is often followed where the risks with the greatest loss and probability of occurring are handled first, and risks with lower loss and probability of occurrence are handled in descending order.
You are the project manager for your company, and you have recently been assigned to a new high-profile project. When should the project kick-off meeting happen?
- When the project manager has approved the project plan
- When management has approved the initial project plan
- At the start of scope validation
- When the project manager has the project team assembled for the first time
When management has approved the initial project plan
Overall explanation
The project kick-off meeting happens after the initial project plan has been approved. This does not answer the question as well as answer C, which outlines when management has approved the initial project plan. The project manager does not necessarily approve the project plan—management does. Scope validation is an inspection-driven process that aims for the project customer to accept the project work.
At Massive Dynamic, they use agile project accounting. What is the most likely benefit of this approach regarding procurement?
- Procurement is consistent regardless of the approach.
- The legal review must be completed within the timebox related to each sprint.
- Contracts must be evaluated each day as part of scrum sessions.
- The process is often much faster due to smaller statements of work and less legal wrangling.
The process is often much faster due to smaller statements of work and less legal wrangling.
Overall explanation
It is likely that the SOW’s are shorter due to planning occurring along the way. They would be issued for smaller amounts of work or would have less defined scope information. Procurement is not consistent across all projects. Contracts are not discussed daily. Contracts should not be evaluated daily or within a certain timebox.
Johann is reviewing a recently accepted project scope statement before discussing it with his team. In addition to the mechanical parts his team is expected to provide, Johann notices that his team is expected to write status reports and documentation. Johann is surprised since his team consists mostly of tradespeople who seldom write reports. He checks with his sponsor to see if the reports and documentation are required. The sponsor confirms that they are. This is an example of which part of the project scope statement?
- Project exclusions
- Deliverables
- Acceptance criteria
- Product scope description
Deliverables
Overall explanation
Deliverables are products, results, or capabilities required to complete a process, phase, or project. The product scope description explains the characteristics of a given service or product in accordance with the project charter and any requirements documentation. Acceptance criteria are conditions that must be fulfilled for deliverables to be accepted. Project exclusions are explicit statements or descriptions of what is out of scope for the project.
Samantha’s agile development team has just moved to Test-Driven Development. They are focusing on two new areas in their development model. They are most likely
- Development and production smoke tests.
- Manual peer testing and writing of automated test scripts.
- Creation of unit tests prior to code being written and refactoring code once it is written.
- Writing of automated test scripts for the future release of code and paired programming.
Creation of unit tests prior to code being written and refactoring code once it is written.
Overall explanation
Test-Driven Development is focused on unit tests written before code and refactoring for maintainability. Paired programming is irrelevant to TDD. Manual peer testing is a fictional term. Production smoke tests are irrelevant to TDD.
The organization has decided to remodel and improve their employee lounge. A large team of cross-functional stakeholders is arguing about the layout and equipment to be included in a new employee lounge. The group generates four ideas, and all members vote for their preferred idea. One idea receives 44% of the votes, more than any other option. Thus, this idea is chosen. Which decision-making technique was used?
- Consensus
- Plurality
- Autocratic
- Creativity Voting
✘ Consensus
Explanation:Reaching consensus is a desired outcome, but this question states that a minority opinion “won” over other options.
✓ Plurality
Explanation:The item under discussion (in this case, style) is decided by plurality when the item receives the highest percentage of votes, even if that percentage is not greater than 50%.
Autocratic
Explanation:This decision-making technique generally involves one individual deciding, regardless of the opinions of others.
Creativity Voting
There are four key values specified in the PMI Code of Ethics and Professional conduct? All of the following are key values except: [Pick Two]
- Fairness
- Quality
- Certification
- Responsibility
- Respect
Quality
Explanation:PMI’s four values in the Code of Ethics and Professional Conduct are responsibility, respect, fairness, and honesty.
Certification
Explanation:PMI’s four values in the Code of Ethics and Professional Conduct are responsibility, respect, fairness, and honesty.
Question 7:Submit a CommentA large project team for a major annual event is reforming with all the same team members. To prepare for the preliminary meeting with the team, the newly assigned project manager reviews the lessons learned repository and sees this highlighted comment: “Team members were distracted at the live matches. The team leads were ineffective at redirecting team member effort.”
How should the project manager approach this situation?
- Coach the team members from the previous year about professionalism at the live matches.
- Replace the team leads from the previous year with stronger, experienced team leads.
- Implement appropriate behavior guidelines and penalties for team members at live matches.
- Establish clearer ground rules with the team and team leads, including disciplinary actions for breaches.
Establish clearer ground rules with the team and team leads, including disciplinary actions for breaches.
Explanation:This team needs improved ground rules. The project manager should recognize that the team’s behavior may not change unless something forces it to change–and establishing clearer ground rules can do this. Because the project manager is new, coaching team members about past behavior will seem theoretical to them; the team leads need to be coached as well! Deselecting team leads or implementing guidelines and penalties seems too heavy-handed for a new project manager. The goal is to create a positive dynamic with this new team so they do not make the same mistakes again.
A planned task in a sprint does not get completed due to an issue that appeared three days ago but did not get resolved. The Project Manager wants to prevent this type of situation in the future.
What should the Project Manager do?
- In the next daily standup meeting, review the issue.
- During the retrospective, examine the issue.
- In the demo, address the issue.
- During the next iteration planning meeting, discuss the issue.
During the retrospective, examine the issue.
Explanation: A retrospective is a great opportunity to talk about what went right, what went wrong, lessons learned and what to improve for next time.
The organization has decided to remodel and improve their employee lounge. The large team of cross-functional stakeholders is arguing about the layout and equipment to be included in a new employee lounge. The group generates four ideas. Optimally, which decision-making technique should be pursued for the new lounge?
- Majority voting
- Plurality
- Consensus/unanimity
- Autocratic
Consensus/unanimity
Explanation: Reaching consensus is a desired outcome. All other options involve a portion of the stakeholders exerting their will at the expense of other stakeholders.
Review the following steps.
- A project has been successfully delivered.
- The project manager is executing formal closure.
- ______________________________________.
What is Step 3?
1. The project manager should obtain stakeholder acceptance.
2. The project manager should reallocate the unused funds.
3. The project manager should update the bid documents.
4. The project manager should reassign the project team.
The project manager should obtain stakeholder acceptance.
Explanation: Accepted deliverables that were formally signed off by the customer or sponsor in Validate scope are then forwarded to the Close Project or phase process. Formal documentation is then signed by the customer or sponsor acknowledging final acceptance of the project’s deliverables.
A customer is not satisfied with the delivered product, saying that it was not what they expected. The Project Manager is surprised, because the agile development team delivered the product several iterations early.
What is one way that the Project Manager could have avoided this result?
- Required team sign off for each of the constant changes to the requirements
- Ensured that the team fully participated in developing the project scope
- Made sure that the customer was aware of the value of demos
- Set aside more resources for product testing after changes are made
Made sure that the customer was aware of the value of demos
Explanation: The customer was not engaged enough in the project. The iteration review is the best mechanism for the team to demonstrate the product and for the customer to give feedback to ensure that their expectations are met.
A company in the food industry creates, markets, and produces a variety of baked goods. They sell their products through supermarkets. They introduce approximately ten new products per year. What type of organization probably best describes this company?
- Functional
- Multidivisional
- Projectized/Project-oriented
- A matrix organization
Functional
Explanation:Functional organizations generally departmentalize similar types of resources (e.g., engineering, manufacturing, accounting), and most resources work on functional or operational activities most of the time.
Multidivisional
Explanation:A multidivisional organization segregates aspects of the business, such as regions or product lines, with potentially little centralization between those aspects. There is no indication of different product lines, regions, or customer to suggest they are multidivisional.
✘ Projectized/Project-oriented
Explanation:Project-oriented organizations likely perform a very large number of complex projects. Most human resources work on projects, and projects account for most organizational spending.
✓ A matrix organization
Explanation:As they produce new products, this involves projects. As they produce a large volume of their products, this involves operations. Thus, matrix is the best answer.
A team was in the execution stage of the project management plan when three necessary changes were brought to their attention. The team members all have differing opinions regarding how to implement the changes.
What should the Project Manager do?
- Organize a meeting with team members to review the issues and request changes where needed.
- Confirm that all team members and stakeholders understand and follow the change management plan.
- Ensure all requested changes are applied to the project and communicate directly with all team members.
- Hold a meeting with the board and project sponsor to address the issue.
Confirm that all team members and stakeholders understand and follow the change management plan.
Explanation: The team and Project Manager must follow the documented and agreed upon change management processes.
Which of the following options is the weakest justification for initiating a project?
- To ensure compliance with a regulation
- To reduce technology costs
- To increase revenue generated
- To increase the transaction speed of an application
To increase the transaction speed of an application
Explanation: Projects are justified for a variety of high-level reasons, often falling into categories such as profit, revenue, cost reduction, customer or employee satisfaction, regulation compliance, etc. In this answer, there’s no indication that increasing transaction speed would provide value to the customer.
A Project Manager believes that a delay in developing a prototype was due to a lack of knowledge in a specific skill that was needed by the cross-functional team.
How could the Project Manager prevent this situation on future projects?
1. Identify required strengths, and organize the team based on those strengths.
2. Offer more skill-specific training throughout the project.
3. Meet with the project sponsor and team members to assign training for specific skills.
4. Empower team members to problem solve in situations where skills may be lacking.
Identify required strengths, and organize the team based on those strengths.
Explanation: Developing the team is an important part of servant leadership. If the Project Manager knows the required strengths and skill sets needed for a project, then they can build the team around those strengths.
A project to migrate the email system of the client to another platform creates an unexpected, but significant, issue on another business-critical system. What should the project manager do?
- Ask the project team to resolve the issue.
- Inform the stakeholders of the issue.
- Revise the project management plan to include the issue.
- Update the issue log.
Inform the stakeholders of the issue.
Explanation: Since the affected system is business-critical, immediate communication is needed.
An oil and gas company is redesigning their oil storage tanks to meet updated international industry standards. A vendor is contracted to perform the work. During the latest inspection, a critical flaw is detected in the tank venting systems.
The vendor states this is a design flaw and they notified the team lead 3 weeks ago to inspect the tanks, but they did not perform the inspection. The vendor kept working, using the designs they were given, to meet the next milestone. The team lead says the inspection was not on the schedule.
What should the project manager do first?
1. Schedule a quality assessment to fix the problem as soon as possible.
2. Consult the project schedule to verify the inspection dates.
3. Escalate to operations and log the problem in the issue log.
4. Consult the responsible, accountable, consulted, and informed (RACI) chart to find out who is responsible and accountable for the inspections.
Schedule a quality assessment to fix the problem as soon as possible.
Explanation: The project manager needs to get this problem fixed as soon as possible. The RACI chart and the conflict between the vendor and the team lead should also be addressed but this can be done later. Escalation is typically the option taken when the issue is beyond your authority and too complex to solve on your own.
The legal team informs the product owner that another company owns a patent for an innovation used in the product of the agile team, now 75% complete.
What should the product owner do to determine the appropriate way forward?
- Work with the legal department to find markets where the patent is not registered
- Continue work on the product after removing the patented component
- Terminate project immediately to prevent any further sunken costs
- Perform marginal economics analyisis and identify minimum releasable features
Perform marginal economics analyisis and identify minimum releasable features
Explanation: A foundational assumption to release the product is now a show-stopper. Marginal economic analysis determines if there is a viable way forward. Identifying minimal releasable features can mitigate the economic loss. Distractors are either unrealistic (unpatented markets, removing component) or uninformed (terminate project).