1. Project
A temporary endeavor is designed to produce a unique product, service, or result.
E.g.: Designing a mobile application for a client.
2. Stakeholders
Any individual or group who has a stake in the project, whether directly or by way of influence.
E.g.: Client person, team members, company management, or end-users.
3. Scope
The project scope describes its boundaries, objectives, and deliverables.
E.g.: Developing a website with specific features and functions.
4. Project Charter
This is an official initiation document for a project, defining objectives, scope, stakeholders, and constraints.
5. Work Breakdown Structure (WBS)
Hierarchical framework for summary breakdown of deliverables into small manageable parts.
E.g.: You can divide a whole construction project into works like excavations, foundation work, framing, plumbing, and electrical setup.
6. Milestone
It is an event or moment that is convincing in the scheduling of the project.
E.g.: Completed a prototype phase of product development as the milestone achieved. Gantt Chart
7. Gantt Chart
A graphic representation is the time-based schedule of activities that are the responsibilities and dependencies of the project.
E.g.: Evaluation of how the tasks that make up a marketing campaign are executed using a Gantt chart.
8. Critical Path
The longest chain of dependent activities for a project determines the minimum time for completion of the project.
E.g.: Mapping critical activities to estimate the time needed to complete a software project with minimum duration.
9. Risk Management
A structured form of identifying, understanding, and analyzing all possible risks on the project.
E.g.: Creating mitigation procedures to handle risks resulting from unexpected shortages of resources or technical breakdowns during project execution stages in an IT infrastructure development project. Change Control: Change Control,
10. Change Control
An organized methodological approach to identification, approval, and implementation in scope, timeline, or budget on any project.
E.g.: Studying a proposed change’s impact on manufacturing to change a design in a product.
11. Project Manager
The individual who executes project planning, control, and implementation is known as a project manager.
E.g.: She coordinates activities among various teams, mitigates risks, and delivers every project milestone on time.
12. Project Sponsor
That senior stakeholder provides the necessary support, resources, and decision-making authority to the project.
E.g.: She is a senior management sponsor who has approved funding for the project and is responsible for resolving escalated issues.
13. Quality Management
Quality Management Activities and processes intended to guarantee that the project complies with established quality standards.
E.g.: Quality audits and inspections are done to verify that the construction project meets requirements.
14. Procurement
Buying goods or services required outside the organization.
E.g.: Building materials are procured from outside contractors.
15. Communication Management
Such processes in project management that communications continue with all stakeholders throughout the project initiate, plan, execute, and close. Such as:
E.g.: Project Management tools will fill this requirement with status meetings held weekly.
16. Cost Management
Processes for project cost estimation, budgeting, and control.
E.g.: Create a cost baseline and use actual costs in situ against it.
17. Time management
The planning, scheduling, and controlling of project tasks to meet deadlines.
E.g.: Developed using techniques like Critical Path Method (CPM) or Program Evaluation and Review Technique (PERT).
18. Resource Allocation
The process of understanding, finding, and optimally distributing various resources including people, machines, and materials.
Example: Assigning tasks to team members based on skills and task availability.
19. Stakeholder Management
That is understanding and managing expectations as well as the need for project stakeholders.
E.g.: Stakeholder analysis strategies of management.
20. Essential Project Management Maximum Integration
All aspects of a project are coardinately unified so that output at the end is well-fashioned.
E.g.: Creating a project management plan whereby all project sections are synchronized in developing integrated outputs throughout the managing processes.
21. Lessons Learned
It is the record of what projects have taught one in future improvement.
E.g.: Documenting lessons learned and effective practices in the case of a finished project to apply in future similar projects.
22. Project Closure
Closure of the project in an official way to complete documentation, evaluation of the results, and delivery of the entire product.
23. Agile Project Management
It is flexible and iterative taking dimensions toward summary and adaptability, teamwork, and incrementalism.
E.g.: Develop software in short iterative sprints with regular feedback in the Scrum framework.
24. Lean Project Management
Lean project management emphasizes reducing waste processes from the point of maximizing actual value.
E.g.: Streamlining the production process is an example of waste removal from operations.
25. Earned Value Management (EVM)
Earned Value Management EVM Cost-based productivity measurement system planning against actual costs versus schedules- Planned and actual cost; schedules.
E.g.: compute such matrics used
26. Project Risk
Referring to uncertain events or circumstances that will or may positively or negatively affect an objective of the project.
E.g.: Market fluctuations or environmental factors in launching a product.
27. Risk Assessment
The process by which risks are assessed concerning their identification, analysis, and prioritization by likelihood and impact.
E.g.: Evaluation of supply chain impacts in a manufacturing project.
28. Risk Mitigation
Activities taken to reduce the likelihood and/or impact of the previously defined risk.
E.g.: Make a contingency plan for the possible loss of crucial personnel.
29. Issue Management
Processes involved in the identification, tracking, and management of project issues during implementation.
E.g.: Management and resolution of software bugs during the development phase.
30. Project Baseline
The first baselined version approves the scope, schedule, and budget of a project which will serve as the basis for performance evaluation.
E.g.: An example of a project baseline includes a baseline original schedule, budget, and deliverables set at kickoff.
31. Change Request
A formal request for project scope, schedule, or budget changes.
E.g.: Demanding an extension in the project timeline due to unforeseen delays.
32. Project Closure Report
It details the achievements concerning what was done throughout the project, challenges faced, and lessons learned, and recommends future projects.
E.g.: Write a closure report that tells how deliverables were completed and areas for improvement.
33. Resource-Leveling
Scheduling or Assignment-Modifications that have been made so that there is neither overloading nor complete underuse of project resources.
E.g.: Reschedule task to redistribute workload to team members.
34. Kick-off Meeting
The first time that the project is briefed among the parties concerned expectations are set. Example
E.g.: Hosting a kickoff meeting to discuss goals, roles, and deliverables with the team and stakeholders.
35. Project Dashboard
It is a visual tool that quickly depicts important metrics and is representative of the current state and pace of the project.
E.g.: Displaying timely information for budgets, schedules, and milestones.
38. Lessons Learned Meeting
It is a closure meeting at the end ofthe project, wherein successes, challenges encountered, and recommendations have been discussed.
E.g.: Getting the necessary feedback from all the team members in a project retrospective.
37. Work Package
It is the smallest piece of project work assigned to an individual to carry it out and track it on the project.
E.g.: Assigning a work package for developing a specific module in the software project.
38. Assumption
Factors assumed to be true for planning.
E.g.: Material availability is assumed in a construction project.
39. Dependency
Relation between jobs in which one job has to wait until the other job is completed.
E.g.: Task B can not be commenced until Task A is finished.
40. Float (Slack)
The time during which an activity is delayed without affecting the project.
E.g.: Minor delays can take place; because Task C has two days of float.
41. Project Portfolio Management
Centralized control of diverse projects designed to meet the strategic goals and maximize value organization-wide.
E.g.: Resource allocation among projects to achieve strategic objectives.
42. Change Management
Change techniques and processes within organizations that help in transition and less resistance from the concerned people during changes.
E.g.: A takeover plan always works to ensure acceptance of the new software by staff.
43. Quality Assurance
Processes leading to meeting defined quality standards for deliverables.
E.g.: Carrying out quality checks during the manufacturing process to ensure compliance with specifications for product quality.
44. Lessons Learned Database
A central repository where the lessons recorded from projects can be consulted in the future for learning purposes.
E.g.: documenting the lessons learned from these projects will help design similar projects.
45. Project Closure Checklist
A comprehensive checklist of tasks needed to close out a project properly.
E.g.: The finalization of documentation standards, transfers of deliverables, and release of resources.
46. Procurement Management Plan
A documented plan as to how procurement activities will be conducted, including whether a vendor will be selected or contracts managed,
E.g.: preparing a plan for procurement of suppliers for a construction project.
47. Resource Histogram
Resource usage over time is graphed.
E.g.: Analyzing a resource histogram to identify workload bottlenecks.
48. Lessons Identified
Possible learning from the experience of a project and information for future work.
E.g.: The documentation of engagement strategies for stakeholders during the execution of the project.
49. Variance Analysis
The comparison of anticipated results with actual performance to identify and create action plans for hitches.
E.g.: An example of this would be the analysis of cost variances to identify the reasons for differences in project spending.
50. Earned Value (EV)
A measure of the amount of work that has been completed expressed as a percentage of work planned along with an associated cost example: measuring earned value to assess the progress of a building.
