A finish-to-start dependency is a type of relationship dependency in project management, where the start of
one task depends on the finish of another task12. In this case, the project manager is using a finish-to-start
dependency, because testing cannot start until requirements development is finished. This implies that testing
is a successor task, and requirements development is a predecessor task. A finish-to-start dependency is the
most common type of dependency in project management, and it ensures that tasks are performed in a logical
sequence34. References = CompTIA Project+ Certification Study Guide5, CompTIA Project+ Certification
Exam Objectives6, Understanding Dependencies in Project Management [2023] * Asana1, Dependencies in
Project Management | Smartsheet2, Understanding Task Dependencies in Project Management3, What are
Dependencies in Project Management? - KnowledgeHut4

The preliminary scope statement must be completed because it defines the expected deliverables, boundaries, assumptions, constraints, and high-level work needed for the project. During planning, the project manager reviews deliverables to ensure the scope is complete enough to support more detailed planning, including the work breakdown structure, schedule, budget, quality expectations, and resource needs. Project objectives are important, but they are usually established earlier during initiation and provide the reason for the project rather than a detailed description of deliverables. Access requirements may be needed for implementation or operations, but they do not validate deliverable completeness. A QA plan defines how quality will be managed and verified, but it depends on the scope and deliverables being clearly understood first.

This answer is based on the best practice of choosing a project management methodology that suits the project
characteristics and environment12. Scrum is an agile framework that is designed to handle complex and
uncertain projects with frequent changes and tight deadlines34. Scrum involves a small, cross-functional team
that works in short iterations called sprints, delivering incremental and potentially shippable products at the
end of each sprint5. Scrum also allows for continuous feedback and improvement through daily stand-up
meetings, sprint reviews, and retrospectives6. Scrum is suitable for this project because it can accommodate
the high uncertainty, the risk of requirement changes, and the tight deadlines, while also enabling the two
developers to collaborate effectively and deliver value to the customer. References = CompTIA Project+
Certification Study Guide7, CompTIA Project+ Certification Exam Objectives8, Project Management
Methodologies Comparison (11 PM Methods)6, Project Management Methodologies: 12 Best Frameworks
[2023]7, What is Scrum?5, Scrum Methodology: The Ultimate Guide6

The project manager should distribute an agenda before a call to ensure all meeting items are addressed and the correct participants attend. An agenda is a document that outlines the purpose, topics, and objectives of a meeting. It also includes information such as date, time, duration, location, attendees, and roles. Distributing an agenda can help to prepare the participants for the meeting, set clear expectations, and facilitate a productive and focused discussion12