Project Management Quiz
Across
- 2. The official written record of what was discussed, what was decided, and who was assigned "Action Items" during a meeting.
- 8. Anyone who is involved in, contributes to, or is affected by the outcome of a project.
- 11. The visible result of a problem, but not the cause itself.
- 12. A written list of topics to be discussed during a meeting. It is created and distributed before the meeting starts.
- 14. Statement A specific, action-oriented sentence explaining a committee's role and purpose.
- 16. Whys A problem-solving technique used to dig past symptoms and find the root cause by repeatedly asking this question.
- 17. The process of identifying and documenting the logical order in which project activities must occur.
- 19. A single point of congestion or delay in a project that slows down all subsequent dependent tasks from moving forward.
- 21. Plan A backup plan created in advance to handle identified risks or bottlenecks.
- 23. The task that logically happens next, following a predecessor.
- 24. Goal A framework for setting goals that are Specific, Measurable, Actionable, Relevant, and Time-bound.
Down
- 1. Reaching an agreement that the entire group can support and commit to, even if it wasn't everyone's first choice.
- 3. Assessment The process of observing and surveying a community to identify "gaps" or problems that need to be solved.
- 4. A risk management exercise where a team imagines a project completely failed, and works backward to brainstorm everything that could have gone wrong.
- 5. A mandatory delay or waiting time between a preceding task and a succeeding task.
- 6. Cause The hidden, underlying origin of a problem.
- 7. A final, tangible product or result produced by a project (e.g., a printed program, a built stage, a launched app).
- 9. How realistic or possible a project is given the available time, budget, and resources.
- 10. Tasks Two or more completely separate activities that are worked on simultaneously by different team members.
- 13. A relationship where one task relies on the completion (or start) of another task.
- 15. A broad picture of what ultimate success looks like for a project.
- 18. Overlapping dependent tasks to get a head start and finish a project earlier.
- 20. The task that absolutely must happen first before the next logical step can begin.
- 22. Breakdown Structure The process of taking a massive, overwhelming project and breaking it down into small, assignable tasks.