In a functional organizational structure, departments such as purchasing operate independently and are managed by their respective department heads12. When project tasks are delayed due to other priorities within a department, it is essential for the project manager to engage directly with the department causing the delay- in this case, the purchasing department. By meeting with the purchasing manager, the project manager can discuss the importance of the project's tasks, understand the reasons for the delay, and work collaboratively to establish a purchasing schedule that aligns with the project's needs while respecting the department's constraints345. This approach fosters communication and collaboration, which are key in a functional structure where the project manager has limited authority over departmental resources.
: = The role of the project manager in a functional organizational structure and the importance of direct communication with department heads to resolve delays and align schedules are well-documented in project management literature12345.

The project manager should prioritize removing barriers that impede team performance and autonomy. This action aligns with the principles of agile project management, which emphasize empowering team members to make decisions and take ownership of their work12. By addressing the internal procedures that are hindering progress, the project manager can facilitate a more efficient and autonomous environment, allowing the team to focus on delivering value more effectively3.
References:
PMI's resources on team building and the importance of removing barriers to enhance team performance1.
Literature on expected behaviors for project team performance, which includes empowering team members and promoting autonomy2.
Agile methodologies that advocate for team empowerment and the removal of impediments to improve project outcomes3.

With repeated vendor delays and no option to replace the vendor, the project manager must actively manage the supplier relationship and develop a realistic recovery plan. Reaching out to the vendor to create a plan (C) is the most effective action: confirm root causes, agree on an achievable delivery schedule, identify acceleration options (expedite shipping, partial deliveries, priority allocation, additional shifts), and define monitoring and escalation checkpoints. This aligns with procurement management and issue management:
collaborate first to restore performance while protecting the 90-day constraint. Threatening penalties (A) may be part of the contract strategy, but leading with penalties can damage collaboration and may not produce a practical recovery plan. Waiting to use contingency funds (B) is reactive and risks missing the hard deadline.
Reviewing lessons learned (D) is helpful, but it does not directly address the immediate supplier performance problem. A vendor recovery plan with clear commitments, accountability, and frequent tracking best supports schedule control under tight constraints.

According to the PMBOK Guide, the project manager should ensure that all the required approvals are received per the organizational procedures before implementing any project deliverables. This is part of the control quality process, which involves validating and verifying that the project deliverables meet the quality standards and requirements. By obtaining the necessary approvals, the project manager can avoid any liabilities, penalties, or disputes that may arise from the implementation of the project deliverables. The project manager should not rely on resolving defects, completing tasks, or documenting results alone, as these may not be sufficient to ensure that the project deliverables are acceptable and compliant with the organizational policies and regulations. References: PMBOK Guide, 7th edition, pages 237-238, 241-242.

According to the Project Management Professional (PMP) guidelines, when a team is struggling to complete work due to unclear requirements, it's often beneficial to review the backlog refinement processes. The product owner, who is responsible for managing the product backlog, should review and refine the backlog items regularly to ensure they are clear, actionable, and prioritized. This process includes detailing the requirements, ordering the items in the backlog to best achieve goals and missions, and optimizing the value of the work the development team performs. By doing so, the team can have a better understanding of the requirements, which can help them complete the iterations successfully. References: Agile Practice Guide, PMI, Chapter 4: Implementing Agile: Delivering in an Agile Environment, Section: Backlog Refinement.
Project Management Professional (PMP) Certification Handbook, PMBOK Guide 6th Edition, Chapter 5:
Project Scope Management.