FREE Comptia Project+ PK0-005 Study Guide
Made for WGU Business of IT - Project Management
1.0 Project Management Concepts
1.1 Explain the basic characteristics of a project and various methodologies and
frameworks used in IT projects.
Characteristics of a project
- Start and finish
- Unique
- Reason/purpose
- Project as part of a program
- Project as part of a portfolio
Methodologies and frameworks
- DevSecOps: DevSecOps is an extension of the DevOps (Development and Operations)
methodology that emphasizes the integration of security practices into the DevOps process. It
focuses on incorporating security considerations and practices early and throughout the
software development lifecycle (SDLC), from planning and coding to testing and deployment.
The goal of DevSecOps is to improve the security of software applications by making security
an integral part of the development and operations processes, leading to faster, more secure
software delivery.
- DevOps: DevOps is a set of practices and principles that aim to improve collaboration and
communication between development (Dev) and IT operations (Ops) teams in order to
streamline software development and delivery processes. DevOps emphasizes automation,
continuous integration, continuous delivery (CI/CD), and a culture of collaboration, enabling
organizations to deliver software more quickly, efficiently, and reliably. It seeks to break down
silos between development and operations, leading to shorter development cycles and
improved software quality.
- Kanban: Kanban relies on visual boards, often called Kanban boards, which are
typically physical or digital boards divided into columns representing different stages of
a workflow or process. Each column may contain cards or visual elements representing
tasks, work items, or items to be produced. Pull system.
- PRojects IN Controlled Environments 2 (PRINCE2)
● Process-Oriented Approach: PRINCE2 is process-driven, meaning it defines a
series of well-defined processes and activities to be carried out during the
project's lifecycle. These processes provide a clear framework for project
management activities.
- Software Development Life Cycle (SDLC):
,Planning: In this initial phase, project stakeholders define objectives, requirements, and
constraints. A project plan is created, outlining goals, scope, timelines, budgets, and resources.
Analysis: Requirements gathering takes place during this phase, involving interviews, surveys,
and analysis of existing systems. The goal is to understand and document the specific needs
and functionalities required for the software.
Design: Based on the gathered requirements, the system's architecture, user interfaces, data
structures, and other design elements are created. This phase focuses on defining how the
software will meet the specified needs.
Implementation (Coding): Developers write the actual code for the software, following the design
specifications. This phase involves coding, testing, and debugging to create functional software
modules.
Testing: The software undergoes rigorous testing to identify and fix defects, ensuring that it
meets the specified requirements. Different testing types include unit testing, integration testing,
system testing, and user acceptance testing (UAT).
Deployment: Once the software is thoroughly tested and approved, it is deployed to a
production environment, making it accessible to end-users.
Maintenance and Support: After deployment, ongoing maintenance, updates, and support are
provided to address issues, implement enhancements, and ensure the software remains
functional and secure.
Documentation: Throughout the SDLC, comprehensive documentation is created to record
project requirements, design decisions, coding standards, testing procedures, and user
manuals. This documentation aids in future maintenance and understanding of the software.
Review and Evaluation: At various stages of the SDLC, project progress and outcomes are
reviewed and evaluated to ensure alignment with project goals, scope, and quality standards.
Feedback and Iteration: Based on reviews and feedback, necessary adjustments and
improvements are made to the software, design, or project plan. Iterative development may
involve revisiting earlier phases to refine and enhance the product.
Closure: In this final phase, the project is officially closed, and documentation is archived. A
post-implementation review is conducted to assess the project's success, lessons learned, and
areas for improvement.
- Scrum: Teams meet for 2-4 week ‘sprint’ cycles where they take from the project backlog and
decide what they want accomplish on a particular cycle.
, - Scaled Agile Framework (SAFe) - implementing agile frameworks at an enterprise level scale.
- Extreme programming (XP): Programming practice that motivates pair programming, and on
site customers.
- Waterfall: Each project follows a strict program where once one section of the project is
finished another begins. Does not relate to agile methodologies.
1.2 Compare and contrast Agile vs. Waterfall concepts.
Criteria for selecting a method
- Tolerance for change/flexibility
o Requirements
o Budget
o Schedule
- Environmental factors
o Cultural
o Developmental
o Industry standards
• Team composition
- Product ownership
- Roles and responsibilities
- Team size: Agile teams tend to have less members than waterfall.
- Resource allocation and commitment
• Differences in communication methods
1.3 Given a scenario, apply the change control process throughout the project life cycle.
• Project-specific change control
- Create/receive change requests
-Document requests in the change control log
- Conduct a preliminary review
- Conduct impact assessments
- Document change recommendations
- Determine decision makers
- Escalate to the change control board (CCB), if applicable
- Document the status of approval in the change control log
- Communicate the change status
- Update the project plan
- Implement changes
- Validate the change implementation
- Communicate change deployment
• Project change management
Made for WGU Business of IT - Project Management
1.0 Project Management Concepts
1.1 Explain the basic characteristics of a project and various methodologies and
frameworks used in IT projects.
Characteristics of a project
- Start and finish
- Unique
- Reason/purpose
- Project as part of a program
- Project as part of a portfolio
Methodologies and frameworks
- DevSecOps: DevSecOps is an extension of the DevOps (Development and Operations)
methodology that emphasizes the integration of security practices into the DevOps process. It
focuses on incorporating security considerations and practices early and throughout the
software development lifecycle (SDLC), from planning and coding to testing and deployment.
The goal of DevSecOps is to improve the security of software applications by making security
an integral part of the development and operations processes, leading to faster, more secure
software delivery.
- DevOps: DevOps is a set of practices and principles that aim to improve collaboration and
communication between development (Dev) and IT operations (Ops) teams in order to
streamline software development and delivery processes. DevOps emphasizes automation,
continuous integration, continuous delivery (CI/CD), and a culture of collaboration, enabling
organizations to deliver software more quickly, efficiently, and reliably. It seeks to break down
silos between development and operations, leading to shorter development cycles and
improved software quality.
- Kanban: Kanban relies on visual boards, often called Kanban boards, which are
typically physical or digital boards divided into columns representing different stages of
a workflow or process. Each column may contain cards or visual elements representing
tasks, work items, or items to be produced. Pull system.
- PRojects IN Controlled Environments 2 (PRINCE2)
● Process-Oriented Approach: PRINCE2 is process-driven, meaning it defines a
series of well-defined processes and activities to be carried out during the
project's lifecycle. These processes provide a clear framework for project
management activities.
- Software Development Life Cycle (SDLC):
,Planning: In this initial phase, project stakeholders define objectives, requirements, and
constraints. A project plan is created, outlining goals, scope, timelines, budgets, and resources.
Analysis: Requirements gathering takes place during this phase, involving interviews, surveys,
and analysis of existing systems. The goal is to understand and document the specific needs
and functionalities required for the software.
Design: Based on the gathered requirements, the system's architecture, user interfaces, data
structures, and other design elements are created. This phase focuses on defining how the
software will meet the specified needs.
Implementation (Coding): Developers write the actual code for the software, following the design
specifications. This phase involves coding, testing, and debugging to create functional software
modules.
Testing: The software undergoes rigorous testing to identify and fix defects, ensuring that it
meets the specified requirements. Different testing types include unit testing, integration testing,
system testing, and user acceptance testing (UAT).
Deployment: Once the software is thoroughly tested and approved, it is deployed to a
production environment, making it accessible to end-users.
Maintenance and Support: After deployment, ongoing maintenance, updates, and support are
provided to address issues, implement enhancements, and ensure the software remains
functional and secure.
Documentation: Throughout the SDLC, comprehensive documentation is created to record
project requirements, design decisions, coding standards, testing procedures, and user
manuals. This documentation aids in future maintenance and understanding of the software.
Review and Evaluation: At various stages of the SDLC, project progress and outcomes are
reviewed and evaluated to ensure alignment with project goals, scope, and quality standards.
Feedback and Iteration: Based on reviews and feedback, necessary adjustments and
improvements are made to the software, design, or project plan. Iterative development may
involve revisiting earlier phases to refine and enhance the product.
Closure: In this final phase, the project is officially closed, and documentation is archived. A
post-implementation review is conducted to assess the project's success, lessons learned, and
areas for improvement.
- Scrum: Teams meet for 2-4 week ‘sprint’ cycles where they take from the project backlog and
decide what they want accomplish on a particular cycle.
, - Scaled Agile Framework (SAFe) - implementing agile frameworks at an enterprise level scale.
- Extreme programming (XP): Programming practice that motivates pair programming, and on
site customers.
- Waterfall: Each project follows a strict program where once one section of the project is
finished another begins. Does not relate to agile methodologies.
1.2 Compare and contrast Agile vs. Waterfall concepts.
Criteria for selecting a method
- Tolerance for change/flexibility
o Requirements
o Budget
o Schedule
- Environmental factors
o Cultural
o Developmental
o Industry standards
• Team composition
- Product ownership
- Roles and responsibilities
- Team size: Agile teams tend to have less members than waterfall.
- Resource allocation and commitment
• Differences in communication methods
1.3 Given a scenario, apply the change control process throughout the project life cycle.
• Project-specific change control
- Create/receive change requests
-Document requests in the change control log
- Conduct a preliminary review
- Conduct impact assessments
- Document change recommendations
- Determine decision makers
- Escalate to the change control board (CCB), if applicable
- Document the status of approval in the change control log
- Communicate the change status
- Update the project plan
- Implement changes
- Validate the change implementation
- Communicate change deployment
• Project change management
