Agile is a methodology that emphasizes iterative and incremental development, customer collaboration, and responsiveness to change. Agile is suitable for developing a minimum viable product (MVP), which is a version of a product with just enough features to be usable by early customers who can then provide feedback for future product development. Agile allows the project sponsor to deliver an MVP quickly and test it with real users, and then adapt the product based on the feedback and changing requirements. Agile also reduces the risk of wasting time and resources on a product that does not meet the customer's needs or expectations123.
References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 2: Project Methodologies, p. 55; What is a Minimum Viable Product (MVP)? | Agile Alliance; Minimum Viable Product (MVP): What is it & Why it Matters - Atlassian

Incorrect configuration was the initial cause of the issue that caused the unexpected crash of the website that the team was developing. The diagram given is an example of a fishbone diagram or a cause-and-effect diagram that shows the possible causes of a problem or effect. The diagram has four main categories: people, process, technology, and environment. Each category has subcategories that list specific factors that may contribute to the problem or effect. The diagram shows that incorrect configuration under technology was marked as an initial cause of website crash.

When analyzing the backlog to decide what to include in the next sprint, the most important aspect to consider
is the impact to the project. This involves assessing which items will provide the most value and contribute
significantly towards achieving the project goals. It's crucial to prioritize work that has the highest impact on
the project's success.
References = The answer is based on standard agile project management practices, particularly in the context
of sprint planning where prioritization is key. For detailed information, please refer to the CompTIA Project+
Study Guide and other official CompTIA resources

A defect log tracks and details all bugs and issues identified in a project. This log is essential for quality control and continuous improvement, as recommended by CompTIA Project+ guidelines on project monitoring and control.

The project manager should review the requested change first to assess its impact, feasibility, and alignment
with the project objectives and scope. Reviewing the change will help the project manager to determine if the
change is necessary, beneficial, and acceptable to the stakeholders. The project manager should also consider
the risks, costs, and quality implications of the change before proceeding to the next steps of the change
management process123. References = CompTIA Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter
9: Project Change Management, p. 323; 5 Steps in the Change Management Process | HBS Online; 8 Steps for
an Effective Change Management Process - Smartsheet