In Agile project management, particularly Scrum, it is common to encounter situations where the team needs to conduct some research or spike to determine the best course of action for implementing a feature1. This is especially true when the team struggles to decide on the most efficient algorithm during sprint planning. Creating a new item in the sprint backlog allows the team to allocate time and resources specifically for this purpose, ensuring that the decision is made based on adequate information and development work2.
This approach aligns with the principles of iterative development and continuous improvement.
References:
PMI. (2017). A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Sixth Edition.
PMI. (2015). Bring certainty in agile sprint planning through estimation2.
PMI. (2011). Agile project management with Scrum1.

According to the PMP Exam Content Outline, one of the tasks for managing project work is to provide relevant stakeholders with project information and updates on cost, schedule, scope, and quality1. The business analyst is a relevant stakeholder who needs to learn about the financial and scheduling aspects of project management. Providing the business analyst with access to the financial and scheduling information is the best way to support their learning and involvement in the project. Assigning resources to coach the business analyst may not be feasible or necessary, as the business analyst may have their own methods and preferences for learning. Asking the business analyst to focus on their work allocation for the needs of the project may not address their learning objectives or expectations. Creating reports to inform the business analyst about the schedule and project cost may not be sufficient or timely, as the business analyst may need more detailed or updated information. References:
* 1: PMP Exam Content Outline, Domain III: Business Environment, Task 4: Manage project changes by following the change management plan in order to achieve project objectives.

If the customer remains dissatisfied despite frequent communication and reporting, the problem is likely not
"lack of updates" but a mismatch between delivered outcomes and customer expectations. The project lead should review the situation with the customer and adjust with the team (C). This reflects agile's inspect-and- adapt mindset: clarify what "satisfaction" means (value, usability, quality, timing), identify gaps in the current product increments, and agree on corrective actions such as reprioritizing the backlog, refining acceptance criteria, strengthening the Definition of Done, improving demo quality, or incorporating customer feedback more effectively. Reducing communication (A) typically worsens alignment. Explaining the team is new to agile (B) is not a solution and can reduce confidence; customers care about outcomes, not excuses. Changing sprint review frequency (D) treats a symptom and may reduce transparency. Collaborative review and adjustment restores alignment, reinforces customer collaboration, and ensures future iterations target the customer's real needs-key PMP and agile objectives for stakeholder engagement and value delivery.

Recognizing and rewarding team members for their hard work and contributions is a key aspect of project management. It helps to motivate the team, improve morale, and foster a positive work environment1. In this context, the project manager should reward the developer according to their motivations and interests2. This could involve understanding what motivates the developer, such as opportunities for learning, career advancement, or other forms of recognition, and then providing rewards that align with these motivations. This approach ensures that the reward is meaningful and appreciated by the developer, thereby enhancing its effectiveness in promoting motivation and engagement2. References: Project Risk Coach, How Are You Work Blog

According to the PMBOK Guide, 7th edition, one of the challenges of agile project management is to align the expectations and understanding of the stakeholders with the agile values and principles. This is especially important when the organization is transitioning from a predictive to an agile approach, as there may be resistance or confusion from the executives who are used to a different way of working. Therefore, the best way to resolve the conflicts between the project team and the executives is to train the executives on agile practices, such as iterative development, adaptive planning, customer collaboration, and continuous improvement. This will help the executives to appreciate the benefits of agile, support the project team, and provide constructive feedback. Training the executives on agile practices will also foster a culture of trust, respect, and empowerment, which are essential for agile project success. References: PMBOK Guide, 7th edition, page 14, Section 1.3.2, Agile Project Management; page 17, Section 1.4.2, Agile Mindset; page 19, Section 1.5, Agile Principles.