What this book covers

Chapter 1, Introduction to the CompTIA Project+ Exam (PK0-004), is an overview of what to expect from the CompTIA Project+ certification process and the steps to help you with certification. It also provides a practice exam to test your knowledge.

Chapter 2, Project Initiation, will help readers learn about how projects are defined based on different organizational structures and introduce the different project selection techniques that are used to charter a project.

Chapter 3, Project Roles and Responsibilities, will describe the variety of stakeholders who could be involved in any type of project and will define the responsibilities they may undertake.

Chapter 4, Developing a Project Charter, will describe the different process groups found on projects or phases and provide information on how key deliverables and high-level requirements are determined based on a business case and stakeholder engagement.

Chapter 5, Creating a Work Breakdown Structure (WBS), will provide the ability to accurately plan other areas such as the schedule, budget, and procurement.

Chapter 6, Developing a Project Schedule, will review defining and sequencing tasks to best determine durations. Once the schedule is put together, the critical path can be determined and a schedule baseline can be set.

Chapter 7, Resource Management Planning and Communication Considerations, will cover the best practices for selecting team members and advice on how to create a cohesive team.

Chapter 8, Budget and Contingency Plans for Risk, will review how project budgets are created and why setting a baseline is so important. It is also necessary for most projects to understand how risk events can help or hurt your project financially.

Chapter 9, Monitoring and Controlling Project Work, will cover how to monitor your project work and make changes to bring performance back in line with the plan and provide best practices to help you keep an eye on your projects and close them out successfully.

Chapter 10, Formal Project or Phase Closure and Agile Project Management, talks about how closing out a project or phase in a formal manner is important for the tracking of lessons learned and for finalizing anything left of project work or deliverable transition. It is also important to know that project management isn't a one-size-fits-all situation, therefore there may be a need to tailor best practices using a more agile approach.