Question 1mediummultiple choice
Read the full NAT/PAT explanation →PK0-005 Tools and Documentation • Complete Question Bank
Complete PK0-005 Tools and Documentation question bank — all 0 questions with answers and detailed explanations.
Refer to the exhibit. ``` TASK DURATION PREDECESSORS A 3 days none B 2 days A C 4 days A D 1 day B, C E 2 days D ```
Refer to the exhibit. ``` Project: MobileApp v2.0 Task Name Duration Predecessors 1. Requirements 10d - 2. Design 15d 1 3. Coding 20d 2 4. Testing 10d 3 5. Deployment 5d 4 ```
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag a concept onto its matching description — or click a concept then click the description.
Sequential phases with heavy documentation
Iterative development with adaptive planning and early delivery
Time-boxed sprints with daily stand-ups and product backlog
Visual workflow management with continuous delivery
Focus on minimizing waste and maximizing value
Drag a concept onto its matching description — or click a concept then click the description.
Information sent to recipients without expecting immediate feedback
Recipients access information at their own discretion
Real-time exchange of information between parties
Official documents like contracts and project reports
Casual conversations and ad-hoc discussions
Project Status Report - Monthly Budget: Planned Value (PV): $120,000 Actual Cost (AC): $130,000 Earned Value (EV): $115,000
Predecessors: A -> B, C; B -> D; C -> D; D -> E Activity durations: A (5 days), B (3 days), C (4 days), D (2 days), E (1 day)
Stakeholder: Sponsor Interest: High Influence: High Category: Executive
Task A: Start 1/1, Duration 5d, No Predecessor Task B: Start 1/6, Duration 3d, Predecessor: A Task C: Start 1/6, Duration 4d, Predecessor: A Task D: Start 1/10, Duration 2d, Predecessor: B, C Task E: Start 1/12, Duration 1d, Predecessor: D Milestone M1: End of Task E
Risk Register: ID | Description | Prob | Impact | Response R1 | Server failure | High | High | Mitigate: backup server R2 | Staff illness | Medium | High | Accept: no action R3 | Regulatory change | Low | High | Transfer: consultant R4 | Budget cut | High | Medium | Avoid: reduce scope
Change Log: ID | Request | Status | Priority | Owner CR1 | Add login page | Approved | High | Alice CR2 | Change color scheme | Approved | Low | Bob CR3 | Implement search | Pending | High | Alice CR4 | Update user manual | Rejected | Medium | Carol
Risk Register: ID: R001 Description: Potential vendor delay Probability: High Impact: High Risk Score: 9 Response: Mitigate Owner: PM
Change Log Entry: Change ID: C001 Description: Add new feature X Status: Approved Date: 2025-01-15 Impact: Schedule increase of 2 days, Cost increase $5,000
Project Charter: Project Name: Cloud Migration Project Manager: Sarah Lee Business Need: Reduce on-premise costs High-Level Scope: Migrate servers to AWS Budget: $200,000 Milestones: Design - Feb 1, Implementation - Mar 1, Go-Live - Apr 1
Activity | Duration | Predecessor A | 2 days | - B | 3 days | A C | 4 days | A D | 2 days | B, C
Planned Value (PV): $45,000 Earned Value (EV): $40,000 Actual Cost (AC): $50,000 Budget at Completion (BAC): $100,000
WBS:
1.0 Software Project
1.1 Planning
1.1.1 Requirements Gathering
1.1.2 Design
1.2 Development
1.2.1 Coding
1.2.2 Testing
1.3 DeploymentChange Request ID: CR-001 Date: 2024-09-15 Description: Add a new feature to the mobile app. Priority: High Status: Submitted Impact: Scope increase of 2 weeks and $5,000. Submitted by: Stakeholder A
Risk ID | Risk Description | Probability | Impact | Risk Score | Response Strategy R-001 | Server outage | High | High | 0.75 | Mitigate R-002 | Vendor delay | Medium | High | 0.50 | Transfer R-003 | Budget cut | Low | High | 0.30 | Accept
Task | Duration | Predecessors A | 3 days | None B | 4 days | A C | 3 days | B D | 3 days | C