Notes
Project vs. Operations
- Project
- Definite beginning and ending
- Process and results are unique
- May involve multiple people, internal groups, or organizations
- Require a purpose- market demand, business need, technical breakthrough, customer order, legal requirement
- Results- new product, new service, product enhancement, improved service, new business asset
- Make a business case by proving the results will fulfill a need
- Value- How well a project meets needs relative to its cost
- financial, strategic, social good, improve quality or resilience, organizational empowerment, customer satisfaction, technological innovation, IP
- Operation
- Needs to be done continually
- May follow same tasks and steps to achieve similar result
Project management
Actvities
- Manage project requirements
- Address stakeholder needs
- speak directly or through focus groups
- Maintain communication
- Balance resource constraints
- scope, schedule, risk, budget, quality, resources
- keep in mind the objectives while balancing
Roles
Core team members- full-time on project Extended- participate part-time in project Functional- contribute directly to fulfilling project requirements Operational- Facilitate the work of functional members via administrative support
- leader- responsible for ensuring the objectives are met
- could be PM, coordinator, scrum master, or others
- facilitator- helps team achieve their goals by clearing barriers
- sponsor- responsible for committing resources, providing funding, and certifying objectives
- product owner- may be sponsor; prioritizes requirements for ongoing work
- business analyst- performs gap analysis, gets info from stakeholders, and defines requirements
- domain SME- Not core team; provide insight toward specifying requirements and may help with implementation
- devs and engineers- complete requirements and generate new value; help to gauge resources requirements and identify activity precedence
- testers & QA specialists- ensures that requirements are met
- customers- may be project owner; define value
- end user- may or may not be customer; will be most impacted by project work
- PMO (project management office)- support, resources, and best practices to project teams
- governance body- insure project work is in compliance; may do formal review
The 2-Day Cram Plan
Day 1: Core Concepts & Weak Area Review (Approx. 6-8 hours)
- Morning (3-4 hours): Review Part 1 of this guide (Core Concepts, Life Cycle, Tools, and Data). Focus on understanding the purpose behind each item, not just the name.
- Afternoon (3-4 hours): Carefully read through Part 2: Personalized Practice Test Analysis. For each question you missed, don’t just read the explanation. Actively think about why you chose the wrong answer and what mental connection you need to fix. This is the most important step.
- Evening: Create digital or physical flashcards for everything in Section 5: Rote Memorization Cheat Sheet. Do a quick review before finishing for the day. Day 2: Memorization & Final Practice (Approx. 6-8 hours)
- Morning (3-4 hours): Drill the flashcards you made. Write out the formulas, acronyms, and key lists (like conflict resolution techniques) from memory. Do this repeatedly until it’s second nature.
- Afternoon (2-3 hours): Take a different, full-length practice exam. Immediately after, review every single question—both right and wrong—to understand the logic.
- Evening: Do one last, quick review of your flashcards and the Rote Memorization Cheat Sheet. Get a good night’s sleep.
Part 1: CompTIA Project+ (PK0-005) Core Concepts Guide
Section 1: Project Management Fundamentals
- Project vs. Operations:
- Project: Temporary and creates a unique product, service, or result. Has a definite start and end. (e.g., Deploying a new ERP system).
- Operations: Ongoing and repetitive work that sustains the business. (e.g., Daily accounting entries).
- The Triple Constraint (Iron Triangle): The three primary competing demands. Changing one impacts the others.
- Scope: The work to be done.
- Schedule (Time): The project timeline.
- Cost (Budget): The financial resources.
- Quality is often considered the central point, affected by all three.
- Key Roles:
- Project Sponsor: Champions the project, provides funding, and has the authority to start/stop the project.
- Project Manager (PM): Responsible for planning, executing, and closing the project successfully.
- Project Team: The individuals performing the project work.
- Stakeholder: Anyone affected by the project or its outcome.
- PMO (Project Management Office): A department that standardizes project management processes, tools, and templates for an organization.
- Project Methodologies:
- Waterfall (Predictive): Traditional, sequential phases. Scope is fixed upfront. Best for well-understood projects.
- Agile (Adaptive): Iterative and incremental. Work is done in short cycles (sprints). Embraces change and customer feedback. Best for projects with evolving requirements.
- Hybrid: Combines elements of both Waterfall and Agile.
Section 2: The Project Life Cycle (Process Groups)
Memorize the flow and the main output of each phase. Mnemonic: I Prefer Eating Mangoes Cold (Initiating, Planning, Executing, Monitoring & Controlling, Closing)
- Initiating:
- Purpose: Formally authorize the project.
- Key Output: Project Charter. This document officially starts the project and grants the PM authority.
- Planning:
- Purpose: Create the roadmap for the entire project.
- Key Output: Project Management Plan. This is the master document containing all subsidiary plans (scope, schedule, cost, risk, etc.).
- Executing:
- Purpose: Perform the work defined in the plan.
- Key Output: Deliverables (the product) and Work Performance Data.
- Monitoring & Controlling:
- Purpose: Track progress against the plan and manage changes.
- Key Output: Change Requests and Work Performance Reports.
- Closing:
- Purpose: Formally finalize and close the project.
- Key Output: Final Product/Service, Lessons Learned Register, and Archived Documents.
Section 3: Key Tools & Documents
| Category | Tool / Document | Purpose |
|---|---|---|
| Initiating | Project Charter | Authorizes the project, names the PM, and lists high-level goals, risks, and stakeholders. |
| Stakeholder Register | Lists all stakeholders and their influence, interests, and communication needs. | |
| Planning | WBS (Work Breakdown Structure) | Decomposes all project work into smaller pieces (work packages). Defines 100% of the project scope. |
| Gantt Chart | A bar chart that visualizes the project schedule and task dependencies over time. | |
| Network Diagram | A flowchart showing the sequence and dependencies of tasks. Used to find the Critical Path. | |
| RACI Chart | (Responsible, Accountable, Consulted, Informed) - Defines roles and responsibilities for tasks. | |
| Risk Register | A log of all identified risks, their characteristics, and response plans. | |
| M & C | Change Control Board (CCB) | A formal group that reviews and approves/rejects change requests. |
| Lessons Learned Register | A living document to capture knowledge gained throughout the project. |
Section 4: Data Analytics & Reporting
Earned Value Management (EVM)
You MUST know these formulas and how to interpret the results.
- PV (Planned Value): The budgeted cost of work scheduled.
- EV (Earned Value): The budgeted cost of work performed.
- AC (Actual Cost): The actual cost of work performed.
| Formula | Name | Question it Answers | Interpretation |
|---|---|---|---|
| CV = EV - AC | Cost Variance | Are we over/under budget? | Positive = Good (Under Budget) |
| SV = EV - PV | Schedule Variance | Are we ahead/behind schedule? | Positive = Good (Ahead of Schedule) |
| CPI = EV / AC | Cost Performance Index | How efficient is our spending? | > 1.0 = Good (Efficient) |
| SPI = EV / PV | Schedule Performance Index | How efficient is our time? | > 1.0 = Good (Efficient) |
Section 5: Rote Memorization Cheat Sheet
Key Acronyms
- CCB: Change Control Board
- EVM: Earned Value Management
- PMO: Project Management Office
- RACI: Responsible, Accountable, Consulted, Informed
- SOW: Statement of Work
- WBS: Work Breakdown Structure
- ESG: Environmental, Social, and Governance
- ERP: Enterprise Resource Planning
Essential Lists to Memorize
- Project Process Groups (IAPEMC): Initiating, Planning, Executing, Monitoring & Controlling, Closing.
- Conflict Resolution Techniques:
- Withdraw/Avoid: Postponing the issue. (Lose-Lose)
- Smooth/Accommodate: Emphasizing agreement, ignoring the problem. (Lose-Win)
- Compromise/Reconcile: Both sides give something up. (Lose-Lose or No-Win/No-Win)
- Force/Direct: Pushing one viewpoint at others’ expense. (Win-Lose) - AVOID THIS
- Collaborate/Problem Solve: Finding a solution that satisfies all parties. (BEST OPTION, Win-Win)
- Tuckman’s Ladder (Team Development): Forming, Storming, Norming, Performing, Adjourning.
- Risk Responses (Threats): Avoid, Transfer, Mitigate, Accept.
- Risk Responses (Opportunities): Exploit, Enhance, Share, Accept.
Part 2: Personalized Practice Test Analysis
Here is a breakdown of the questions you missed. Focus on understanding the logic and memorizing the key terms defined.
Question 3
- Question: Which of the following are examples of industry- or organization-specific compliance concerns that may impact a project?
- Correct Answer: B, C, D (PCI DSS, FINRA, Company code of ethics)
- Explanation:
- Why B, C, D are Correct:
- (B) PCI DSS (Payment Card Industry Data Security Standard): This is a specific set of security standards for any organization that handles credit cards. It is a classic example of an industry-specific compliance requirement.
- (C) FINRA (Financial Industry Regulatory Authority): This body regulates brokerage firms and exchange markets. Compliance is mandatory for projects in the financial services industry.
- (D) Company or employee code of ethics: This is an organization-specific compliance document that all projects within that company must adhere to.
- Why A is Incorrect:
- (A) Virginia Consumer Data Protection Act (VCDPA): This is a governmental law or regulation based on geography (the state of Virginia). While it is a compliance concern, it’s not specifically tied to an industry or a single organization but rather to anyone doing business in or with residents of that location. The question’s focus is on industry/organization standards.
- Why B, C, D are Correct:
Question 7
- Question: Who would be the best party to conduct briefings on project status, including cost, schedule, quality, and technical aspects?
- Correct Answer: D (team members knowledgeable in the areas)
- Explanation:
- Why D is Correct: While the Project Manager (A) facilitates and owns the overall meeting, the most effective and credible briefings come directly from the subject matter experts—the team members who are doing the actual work. A developer is best equipped to discuss technical aspects, and a cost analyst is best for the budget. This demonstrates effective delegation and leverages the team’s expertise.
- Why A, B, C are Incorrect: The PM (A) orchestrates the meeting but shouldn’t be the sole speaker on all detailed topics. Functional heads (B) are too far removed from the daily project work. The customer (C) is the audience, not the presenter.
Question 15
- Question: The team is assigning a privacy impact rating to data for a new software module. Which step in the software change control process are they performing?
- Correct Answer: A (Requirements definition)
- Explanation:
- Why A is Correct: A “privacy impact rating” is a non-functional requirement. It defines how the system must handle data, which is a core part of defining the requirements for the change. Before you can assess risk or get approval, you must first define what the change needs to do.
- Why E is Incorrect: While the privacy rating is an input to the Risk Assessment (E), the act of assigning the rating itself is part of defining the change’s requirements. Risk assessment would come next, analyzing the potential negative impacts if this requirement is not met.
- Augmented Info - Typical Change Control Steps: 1. Identify Change → 2. Document Change Request → 3. Define Requirements of Change → 4. Assess Impact/Risk → 5. Get Approval (CCB) → 6. Implement Change → 7. Validate/Test → 8. Release & Communicate.
Question 16
- Question: You want to categorize errors and find their frequency to identify the main causes. What tool helps?
- Correct Answer: B (Pareto diagram)
- Explanation:
- Key Term - Pareto Diagram: This is a quality management tool based on the 80/20 rule (the Pareto Principle). It’s a combination bar and line chart. The bars show the frequency of different categories of problems (in descending order), and the line shows the cumulative percentage. Its purpose is to help a team focus on the “vital few” causes that are responsible for the majority of the problems.
- Why B is Correct: The question’s goal—find the frequency of errors to identify the most significant causes—is the exact definition of a Pareto diagram’s function.
- Why A, C, D are Incorrect: PERT (A) is a scheduling estimation technique. A Gantt chart (C) visualizes a project schedule. A fishbone diagram (D) helps brainstorm all possible causes for a single problem, but it doesn’t use frequency data to prioritize them.
Question 18
- Question: Alexey needs to immediately review changes with his collocated team. Which communication tools should he choose?
- Correct Answer: B, D, E (Telephone, Video call/videoconference, Face-to-face meeting)
- Explanation:
- Why B, D, E are Correct: The keywords are “immediately” and “collocated.” These point to synchronous (real-time) communication methods. A face-to-face meeting (E) is the most obvious choice for a collocated team. Telephone (B) and Video calls (D) are also synchronous and allow for immediate back-and-forth discussion.
- Why A, C are Incorrect: Email (A) and Enterprise social media (C) are asynchronous. They do not guarantee an immediate review or discussion, as there can be a delay in response. They are not suitable for an urgent, real-time review.
Question 19
- Question: A globally distributed team needs access, but only one person has physical site access. What type of access should be established for the rest of the team?
- Correct Answer: A, C, D (Remote access, VPN access, Access control)
- Explanation:
- Why A, C, D are Correct:
- (A) Remote access: This is the general term for allowing users to access network resources from a different location. It’s the overarching requirement.
- (C) VPN (Virtual Private Network) access: This is a specific technology used to provide secure remote access over the internet. It’s a common way to implement (A).
- (D) Access control: This is a security principle and process. It’s not a tool itself, but a necessary system to manage who has what access (e.g., ensuring only the PM can approve certain files, while developers can access code repositories). It governs both remote and facility access.
- Why B is Incorrect: The question explicitly states that only one person has facility access (B), so this is not what needs to be established for the rest of the team.
- Why A, C, D are Correct:
Question 22
- Question: Which three activities would you perform during the discovery/concept phase?
- Correct Answer: C, D, E (Create a business case, Check pre-existing contracts, Review vendor options)
- Explanation:
- Key Term - Discovery/Concept Phase: This is the very beginning of a project idea, even before the Initiating phase. It’s about determining if a project is feasible and worth pursuing.
- Why C, D, E are Correct: Creating a business case (C) justifies the project’s existence. Checking contracts (D) and reviewing vendors (E) are part of the initial due diligence to understand potential constraints, partners, and costs. These all happen before a project is formally chartered.
- Why A, B, F are Incorrect: Building a project schedule (A) and training team members (F) are Planning/Executing activities. Developing the project charter (B) happens in the Initiating phase, which comes after the initial discovery/concept is deemed viable.
Question 33
- Question: An SME suggests one module should be developed before another based on past experience. What type of dependency is this?
- Correct Answer: B (discretionary)
- Explanation:
- Augmented Info - Task Dependency Types:
- Mandatory (Hard Logic): An inherent dependency that cannot be changed. (e.g., You must build the foundation before the walls).
- Discretionary (Soft Logic / Preferred Logic): A dependency based on best practice, a preference, or a non-essential sequence. The project could technically be done in a different order, but this way is preferred.
- External: A dependency based on an input from outside the project. (e.g., Waiting for a government permit).
- Internal: A dependency between two project tasks, managed by the project team.
- Why B is Correct: The SME’s suggestion is a “best practice” or a preference. The second module could technically be started, but it’s not advisable. This is the definition of a discretionary dependency.
- Augmented Info - Task Dependency Types:
Questions 34, 44, 46 (Network Diagram Questions)
- Explanation: These questions require a visual network diagram exhibit that was not included in the JSON data. However, I can explain the concepts you need to solve them.
- Key Concepts for Network Diagrams:
- Critical Path: The sequence of tasks that determines the shortest possible duration for the project. It is the longest path through the network diagram. Any delay on the critical path will delay the entire project. The float/slack on the critical path is zero.
- Float (or Slack): The amount of time a task can be delayed without delaying the project’s end date. Float = Late Start (LS) - Early Start (ES).
- Forward Pass: Calculating the Early Start (ES) and Early Finish (EF) for each task by moving from the beginning of the project to the end. (EF = ES + Duration).
- Backward Pass: Calculating the Late Start (LS) and Late Finish (LF) for each task by moving from the end of the project to the beginning. (LS = LF - Duration). This is what you need to find the Late Start of Task E (Q34).
- To answer these questions, you must:
- Identify all possible paths through the diagram.
- Calculate the total duration of each path.
- The path with the longest duration is the Critical Path (Q46).
- Calculate the LS for Task E by performing a backward pass from the project end date.
- Analyze how increasing a task’s duration affects the path lengths to see if the critical path changes (Q44).
Question 37
- Question: A geographically dispersed team needs a central repository for documentation. Which should you NOT use?
- Correct Answer: A (Vendor knowledge base)
- Explanation:
- Why A is Correct: A vendor knowledge base is typically a resource provided by a software or hardware vendor for their products. It is not a tool for your team to create and store your own project-specific documentation. It’s an external resource, not an internal repository.
- Why B, C, D are Incorrect: An Internet site (B), Wiki page (C), and Intranet site (D) are all valid platforms that can be configured and used as a central repository for a project team to share its own documents.
Question 43
- Question: Nancy has accepted all vendor deliverables and needs to indicate the procurements are complete. In which phase is she working?
- Correct Answer: D (Closing)
- Explanation:
- Why D is Correct: While the work and deliverables from vendors occur during the Executing phase, the formal process of closing procurements (finalizing payments, closing contracts, and formally accepting all work is done) is a key activity of the Closing phase. This is a common point of confusion.
- Why B is Incorrect: Executing is where the vendor does the work. Closing is where you formally close out the contract after the work is done and accepted.
Question 47
-
- Question: How do you communicate project status to stakeholders to show variations between actual and planned schedule and budget?
-
- Correct Answer: A (tracking Gantt chart)
-
- Explanation:
- Why A is Correct: A Tracking Gantt Chart is specifically designed for this. It visually compares the original baseline schedule (planned bars) with the actual progress (filled-in or separate bars). This provides an immediate, intuitive visual representation of schedule variance, making it an excellent communication tool for stakeholders.
- Why C is Incorrect: Earned Value Analysis (EVA) provides the numerical data (SV, SPI, CV, CPI) for schedule and budget variance. While this data is crucial, it’s not a communication tool in itself. A tracking Gantt chart visualizes this information for easier consumption by stakeholders. The question asks how you communicate it, and visual charts are key.
- Why B and D are Incorrect: Review meetings (B) and progress reports (D) are methods or containers for communication, but the tracking Gantt chart is the specific tool within them that shows the schedule variance.
Question 49
- Question: What communication methods allow Ellen to ask non-urgent questions without interrupting David?
- Correct Answer: B, D (Text messaging, Email)
- Explanation:
- Key Concept - Asynchronous Communication: This is communication where the participants do not need to be engaged at the same time (e.g., email, text, forum posts). It is perfect for non-urgent matters where an immediate response is not required.
- Why B and D are Correct: Email (D) is the classic asynchronous tool. The recipient can read and reply when they have a moment. Text messaging (B), while often used for quick replies, is also fundamentally asynchronous and less disruptive than a phone call or walking over.
- Why A and C are Incorrect: Enterprise social media (A) could work but is often more for broader team announcements. Faxing (C) is an outdated and inefficient method for this kind of simple query.
Question 51
- Question: A project has many stakeholders with differing needs. What is the best first step to facilitate discussion?
- Correct Answer: B (Have a formal kick-off meeting at which all stakeholders participate.)
- Explanation:
- Why B is Correct: A kick-off meeting is the formal event designed to bring all key stakeholders together at the start of a project. Its purpose is to align everyone on the project’s goals, scope, and plans, and to establish communication lines. It is the single best first step to get everyone on the same page.
- Why A, C, D are Incorrect: Interviewing stakeholders individually (D) is a good activity, but it should happen before or as an input to the kick-off meeting, not as the primary facilitation step. Reviewing plans with individuals (C) can lead to siloed conversations and misunderstandings. Submitting all wants to the sponsor (A) bypasses the crucial step of discussion and prioritization among the stakeholders.
Question 58
- Question: Match project management scheduling tool installation types with their features.
- Correct Answer: As listed in the JSON.
- Explanation: This is pure memorization. Here is a simplified table to help you remember.
| Installation Type | How it Works | Cost Model | Maintenance |
|---|---|---|---|
| Cloud-based | Access via web browser. Works across devices. | Recurring subscription fee (SaaS). | Low (Vendor handles it). |
| On-premises | Installed on your company’s servers. | Large initial investment (licensing). | High (Your IT team manages it). |
| Local | Installed on a single computer/device. | One-time software purchase. | Highest (User is responsible for everything). |
Question 60
- Question: What are three statements that define the Scrum master’s role in gathering requirements?
- Correct Answer: A, B, C (Handle external impediments, Bridge communication gaps, Translate needs)
- Explanation:
- Key Concept - Scrum Roles:
- Product Owner: Owns the product vision. Manages and prioritizes the Product Backlog. Represents the customer/stakeholders.
- Scrum Master: A “servant-leader” and coach. Facilitates Scrum events. Removes impediments (blockers) for the team. Protects the team from outside distractions.
- Development Team: Self-organizing group that does the work to create the product increment.
- Why A, B, C are Correct: The Scrum Master acts as a facilitator. They handle external impediments (A) that might block the team, ensure effective communication (B) between the Product Owner and the team, and help translate (C) needs to ensure clarity. These are all facilitation and support roles.
- Why D and E are Incorrect: The Scrum Master is NOT a resource manager (D). The team is self-managing. The Scrum Master does NOT prioritize the backlog (E); that is the sole responsibility of the Product Owner.
- Key Concept - Scrum Roles:
Question 70
- Question: While managing projects within a program, what actions may a PM need to perform due to interdependencies?
- Correct Answer: A, B, C (Resolving issues/change, Aligning goals, Resolving resource conflicts)
- Explanation:
- Key Concept - Program Management: A program is a group of related projects managed in a coordinated way to obtain benefits not available from managing them individually. The key word is interdependencies.
- Why A, B, C are Correct: Because projects in a program are linked, the PM must constantly deal with the ripple effects. A change in one project (A) can impact another. Strategic goals (B) must be aligned across all projects. Resources (C) are often shared, leading to conflicts that must be resolved at the program level.
- Why D is Incorrect: While cost control is always important, “minimizing project costs” is a general PM duty, not a specific action performed due to interdependencies within a program. In fact, program-level decisions might sometimes increase one project’s cost to achieve a greater overall program benefit.
Question 72
- Question: Which of the following is NOT a valid way to avoid resource overallocation?
- Correct Answer: A (Limiting project acquisition)
- Explanation:
- Key Concept - Resource Overallocation: This occurs when a resource is assigned to more work than they can complete in a given time period.
- Why A is Correct: “Limiting project acquisition” is a Portfolio Management strategy. It is done at a high organizational level to decide which projects the company will even start. It is not a technique a Project Manager uses to manage resources within their already approved project(s).
- Why B, C, D are Incorrect: Leveling resources (C) is a primary technique to resolve overallocation by adjusting schedules. Prioritizing projects (D) helps determine which tasks get resources first. Allowing breathing space (B) is a planning tactic to build slack into the schedule, which helps prevent overallocation.
Question 75
- Question: You need to communicate an approved change. What makes the communication most effective?
- Correct Answer: B, D (Explain the intent clearly, Mention the benefits)
- Explanation:
- Why B and D are Correct: Effective change communication focuses on clarity and “what’s in it for me” (WIIFM). You must clearly explain the intent and purpose of the change (B) so people understand the “why.” You must also highlight the benefits (D) to gain buy-in and reduce resistance from stakeholders.
- Why A, C, E are Incorrect: While you need to be aware of the constraints (A) and drawbacks (C), leading with them makes for poor communication and invites resistance. You should focus on the positive intent and benefits first. Discussing best practices (E) is irrelevant to communicating a specific, approved change to stakeholders.
Question 80
- Question: The project doesn’t match the customer’s wants. What are three potential sources of the scope mismatch?
- Correct Answer: A, C, D (Requirements not correctly gathered, PM did not caution against gold plating, Plan lacked a detailed scope statement)
- Explanation:
- Why A, C, D are Correct:
- (A) Requirements were not correctly gathered: This is the most direct cause. If the initial requirements document was flawed, the project was built on a faulty foundation.
- (D) Lacked a detailed scope statement: A good scope statement would have clarified the project boundaries and deliverables, making it easier to spot discrepancies with the requirements document early on.
- (C) Gold plating: This is when the team adds extra features that were not requested. Even if the requirements were correct, gold plating could cause the final product to differ from what was formally agreed upon.
- Why B is Incorrect: Auditing every task is micromanagement and not a standard PM duty. The PM’s role is to manage the overall process, not inspect every single finished task.
- Why A, C, D are Correct:
Question 81
- Question: A US-based PM is working with a client in France, and discussions must be in French. What are the best communication options?
- Correct Answer: A, D (Do not communicate important matters via email, Conduct video conferencing with a translator)
- Explanation:
- Why A and D are Correct: When there is a significant language barrier, relying on written communication like email (A) for important, nuanced matters is very risky. Tone, context, and complex ideas can be lost in translation, leading to major misunderstandings. The best approach is synchronous communication (like a video conference, D) where a professional translator or interpreter can facilitate real-time understanding and clarification.
- Why B and C are Incorrect: Option B is the opposite of the correct approach. Voice conferencing (C) is good, but video conferencing (D) is better as it allows for non-verbal cues, which are a critical part of communication.
Question 83
- Question: Which of the following is performed during the development stage of software development?
- Correct Answer: D (Requirements definition)
- Explanation:
- Augmented Info - Simplified Software Development Life Cycle (SDLC):
- Planning & Requirements Definition (D): Figure out what to build.
- Design: Architect the system.
- Development (Coding): Write the software.
- Testing: Find bugs. Includes Smoke Testing (B) to see if a build is stable enough for further testing.
- Deployment: Release the software. Includes Pilot Deployment (A) to a small group of users.
- Maintenance: Support and update the software.
- Why D is Correct: Requirements definition is the foundational step that happens at the beginning of the development stage, guiding everything that follows.
- Why A and B are Incorrect: Pilot deployment (A) happens at the end, during release. Smoke testing (B) happens during the testing phase, after a build is created. Risk assessment (C) is an ongoing project management process, not a specific SDLC stage.
- Augmented Info - Simplified Software Development Life Cycle (SDLC):
Question 90
- Question: Which project document will you use to determine the target audience when planning project communications?
- Correct Answer: B (Stakeholder register)
- Explanation:
- Why B is Correct: The Stakeholder Register is the definitive document for this purpose. It is created specifically to list all stakeholders, their roles, interests, influence, and communication requirements. It directly answers the question, “Who is my audience?”
- Why A, C, D are Incorrect: The Charter (D) and SOW (A) may list key stakeholders but not the comprehensive list needed for detailed communication planning. The Risk Register (C) lists risks, not audiences.