PK0-005: CompTIA Project+

Smoothing is a conflict resolution technique that involves minimizing or ignoring the differences between the parties and focusing on the common interests or goals1.It is often used when the conflict is not very important or when there is a need to maintain harmony and relationships2. By using smoothing, the project manager can reduce the tension and stress caused by the disagreement and encourage the team members to cooperate and work together.Smoothing is different from compromising, which involves finding a middle ground or a trade-off that partially satisfies both parties; forcing, which involves imposing one's own solution or decision on the other party; and collaborating, which involves finding a win-win solution that fully satisfies both parties3.Reference=CompTIA Project+ PK0-005 Certification Study Guide, Chapter 10: Executing Projects Part 1, page 297;A Quick Guide to Resource Smoothing: Definition, Benefits, and Process, Conflict Resolution Techniques section;Resource Smoothing: How To Use In Project Management | Hive, Smoothing section.

The next step after defining tasks, durations, resources, and costs is to establish baselines. A baseline is an approved version of a project plan that serves as a reference point for measuring progress and performance throughout the project lifecycle. A baseline typically includes scope, schedule, cost, quality, and risk parameters. Establishing baselines involves presenting the project plan to key stakeholders and obtaining their formal agreement on the project objectives and deliverables. Baseline approval can help to establish clear expectations, avoid scope creep, and facilitate change control during project execution34

During the stabilization phase of recently deployed software, the project manager will most likely use a defect log to track and manage reported bugs. A defect log is a document that contains information about the defects or issues identified during testing or after the deployment of software. It includes the severity of the defect, the steps to reproduce the problem, and the actions taken to resolve the defect. Reference: CompTIA Project+ Study Guide Section 4.1.

The project manager will most likely use a defect log during the stabilization phase for recently deployed software to record a bug that is compromising data integrity. A defect log is a tool that tracks and documents any errors or flaws found in a software product or system during testing or operation. It usually includes information such as defect ID, description, severity, priority, status, resolution, and responsible person. A defect log can help to monitor and manage the quality of the software product or system and ensure that all defects are identified and resolved before delivery or release.

A project evaluation review is a tool that helps a project manager assess the activities performed, work effort applied, and the productivity of a project. It involves collecting and analyzing data on the project's performance, outcomes, and impacts. It also provides feedback and recommendations for improvement and learning. A project evaluation review can be done at different stages of the project life cycle, such as during or after completion. Reference = CompTIA Project+ PK0-005 Certification Study Guide, Chapter 14: Project Evaluation and Assessment; CompTIA Project+ Certification Exam Objectives, Domain 4: Project Closure, Objective 4.1: Conduct project closure activities.

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.Reference= 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

Documenting artifacts is the main reason for creating and maintaining project documents that relate to the management of the project, not the project deliverables. Artifacts are used to define, support, and align the project work to the project requirements and business goals.They also serve as a source of information and evidence for future projects, audits, reviews, and lessons learned1.Documenting artifacts helps to capture the project's history, performance, outcomes, and best practices, which can be useful for organizational learning and improvement2.Reference=CompTIA Project+ PK0-005 Certification Study Guide, Chapter 14: Closing the Project, page 403;Project Artifacts and How to Use Them - Rebel's Guide to Project Management, Introduction and What are project artifacts in project management? sections;Project Management Artifacts: Definition, Types, and Phases, Introduction and What are project artifacts in project management? sections.