A vocabulary exercise covering IT project management terminology. These terms are used by project managers and technical leads managing software and technology projects in English.
📚 Key vocabulary stakeholder — any individual, group, or organization that has an interest in or is affected by a project's outcome deliverable — a tangible or intangible output produced as part of a project that can be measured and verified scope creep — the uncontrolled expansion of a project's requirements beyond what was originally agreed upon critical path — the longest sequence of dependent tasks in a project that determines the minimum completion time milestone — a significant event or achievement in a project timeline that marks progress toward completion risk register — a document used to identify, assess, and monitor potential risks throughout a project Gantt chart — a bar chart showing a project schedule with tasks, durations, and dependencies plotted over time sprint — a short, time-boxed period in Agile projects during which a specific set of tasks is completed baseline — the approved version of a project plan used as a reference point to measure actual performance resource allocation — the process of identifying and assigning available resources to project tasks efficiently
READY TO PRACTICE? LET’S GO!
Choose the correct response to complete each sentence.
1. Everyone knows that _____________________ ( = the time when a server/site are down) is costly.
That's right! Well done!Sorry, that is incorrect. Please try again.
2. As a project manager, I have to _____________________ all technology related expenses.
That's right! Well done!Sorry, that is incorrect. Please try again.
3. That appears to be a _____________________ solution, but there's always a risk that it might not come together in production.
That's right! Well done!Sorry, that is incorrect. Please try again.
4. The last project I was working on had a tight deadline, so once decisions were made, we couldn't _____________________. ( = go back and change them)
That's right! Well done!Sorry, that is incorrect. Please try again.
5. Well, it's explicitly ____________________ in the guidelines that we are to avoid this.
That's right! Well done!Sorry, that is incorrect. Please try again.
6. Everyone on my team knows what they're supposed to do. There is no _____________________.
That's right! Well done!Sorry, that is incorrect. Please try again.
7. I use critical path analysis to _____________________ and manage complex projects.
That's right! Well done!Sorry, that is incorrect. Please try again.
8. We're going to have to _____________________ ( = change) our plans a little bit.
That's right! Well done!Sorry, that is incorrect. Please try again.
9. Before we assign tasks, we have to _____________________ them.
That's right! Well done!Sorry, that is incorrect. Please try again.
10. It's my job to ensure that all the work is done to _____________________.
That's right! Well done!Sorry, that is incorrect. Please try again.