PMI PMP - Project Management Professional (PMBOK 7th Version)

 According to the PMBOK Guide, stakeholder involvement is a key factor for successful change management. Stakeholders are individuals or groups who can affect or be affected by the project outcomes. By involving stakeholders from all levels of the company, the project manager can ensure that everyone understands the need, benefits, and impacts of the change. This can help to reduce resistance, increase buy-in, and foster collaboration among the stakeholders. Additionally, by involving stakeholders early and often, the project manager can solicit their feedback, address their concerns, and incorporate their suggestions into the project plan. This can enhance the quality and acceptance of the project deliverables and outputs. Furthermore, by involving stakeholders from all levels of the company, the project manager can leverage their influence, expertise, and resources to support the project execution and implementation. This can improve the project performance and increase the likelihood of achieving the project objectives. References:

PMBOK Guide, 7th edition, Chapter 3: Project Management Principles, Section 3.5: Engage Stakeholders, pp. 41-421

PMBOK Guide, 7th edition, Chapter 9: Stakeholders, Section 9.1: Identify Stakeholders, pp. 137-1391

PMBOK Guide, 7th edition, Chapter 9: Stakeholders, Section 9.3: Engage Stakeholders, pp. 144-1451

Professional in Business Analysis (PMI-PBA) Handbook, Section 5: Exam Content Outline, Domain 2: Planning, Task 2.4: Develop a stakeholder engagement plan, pp. 22-232

Professional in Business Analysis (PMI-PBA) Handbook, Section 5: Exam Content Outline, Domain 3: Analysis, Task 3.1: Elicit and confirm information from relevant stakeholders, pp. 24-252

Making work visible using kanban boards is a technique that helps to manage the flow of work and identify bottlenecks or impediments. Kanban boards show the status of each work item, the priority, the assignee, and the dependencies. This way, the project manager can monitor the progress of the software development, communicate with the team and the stakeholders, and resolve any issues that arise. Applying lean manufacturing to limit the team’s work is not a suitable option, as it does not address the root cause of the delays or impediments. Increasing retrospectives to deliver results fast is not a realistic solution, as it may compromise the quality of the software and the team’s morale. Incorporating small batches of work into the project is a good practice for agile projects, but it does not solve the problem of lack of information or communication. References: Project Management Professional Sample Questions, page 10, question 84. [A Guide to the Project Management Body of Knowledge (PMBOK Guide)], Sixth Edition, page 188, section 6.2.2.4. [Agile Practice Guide] , page 51, section 4.2.2.

According to the PMBOK Guide, a project manager should proactively engage with stakeholders to identify and resolve issues that may impact the project’s objectives, scope, schedule, cost, quality, resources, or risks. In this scenario, the project manager faces a bottleneck in the release management process, which may delay the delivery of the joint application development module and affect the integration with other modules. Therefore, the best option is to speak to the stakeholders, such as the sponsor, the customer, the release manager, and the development team, to resolve the bottleneck and see how the entire process can be streamlined. This way, the project manager can ensure that the project delivers value to the customer and meets the expectations of the management. Pushing the team to deliver more, working toward the tighter deadline, or slowing the current pace are not effective options, as they may compromise the quality, scope, or alignment of the project. References: PMBOK Guide, 7th edition, pages 95-96, 101-102, 105-106.

According to the PMI Guide to Business Analysis, one of the key competencies of a business analyst is to facilitate collaboration and teamwork among stakeholders. This includes building trust, rapport, and respect among team members, as well as fostering a positive and supportive work environment. The guide also states that “team morale is influenced by the business analyst’s ability to communicate effectively, manage conflict, and motivate others” (p. 41).

One of the ways to build team connections and emotional bonds is to use emotional intelligence, which is defined as “the ability to perceive, understand, and manage one’s own emotions and the emotions of others” (p. 42). Emotional intelligence can help the business analyst to:

Recognize and acknowledge the feelings and perspectives of team members, especially when they are affected by a change or a loss

Express appreciation and gratitude for the contributions and achievements of team members

Provide constructive feedback and coaching to help team members improve their performance and skills

Encourage team members to share their ideas, opinions, and concerns, and listen actively and empathetically

Resolve conflicts and disagreements in a respectful and collaborative manner

Celebrate successes and milestones, and recognize the efforts and challenges of the team

By building team connections and emotional bonds, the business analyst can help to improve team morale and teamwork, as well as increase team engagement, commitment, and productivity.

A minimum viable product (MVP) is a concept from Lean Startup that stresses the impact of learning in new product development. It is the simplest version of a product that allows a team to collect the maximum amount of validated learning about customers with the least effort. An MVP can help a project manager to deliver value to the customer faster, test the market demand, and reduce the risk of failure. To create an MVP, the project manager needs to review the project backlog and prioritize the features that are essential to solve the customer’s problem or satisfy their need. The project manager can use agile methods such as user stories, story mapping, and MoSCoW prioritization to identify and rank the features. The project manager can then plan and execute the development of the MVP within the expected timeline and gather feedback from the customer and stakeholders to validate the product and make improvements. References:

MVP Definition and Examples | Project Management Glossary - Jexo

What is a Minimum Viable Product (MVP)? | Agile Alliance

MVPs and MBIs - Project Management Institute

Developing the resource management plan is the first process in the resource management knowledge area. The resource management plan describes how the project resources, including human resources, will be acquired, allocated, developed, managed, and released. One of the components of the resource management plan is the training plan, which identifies the training needs, objectives, methods, and evaluation criteria for the project team members. By developing the resource management plan and ensuring adequate training, the project manager can address the skill gaps of the team members and prepare them for the key tasks later in the project. This will also enhance the team performance, motivation, and satisfaction. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK® Guide, 6th edition, Section 9.1, pp. 308-313

PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain II: Planning, Task 2, p. 9

Business Analysis for Practitioners: A Practice Guide, Section 3.4.1, p. 66

According to the Agile Practice Guide, one of the principles of agile project management is to “respond to change over following a plan” 1. This means that agile teams should be able to adapt to changing requirements and market conditions, and deliver value to the customer as quickly as possible. Adding the competitor’s functionalities to the product backlog (option A) may not be the best way to respond to change, as it may increase the scope and complexity of the project, and delay the delivery of the product. Asking the sponsor to add more people to the team (option B) may also not be effective, as it may disrupt the team dynamics and communication, and cause the Brooks’ law effect, which states that “adding manpower to a late software project makes it later”. Asking the team to increase the velocity to launch the product as soon as possible (option D) may compromise the quality and sustainability of the product, and put undue pressure on the team. Therefore, the best option is to help the team to find a new approach to launch the product as soon as possible (option C), which may involve prioritizing the most valuable features, reducing the technical debt, applying lean principles, and collaborating with the customer and other stakeholders. References: 1: Agile Practice Guide, Chapter 2: An Introduction to Agile, page 13 2: The Mythical Man-Month: Essays on Software Engineering, by Frederick P. Brooks Jr., page 25