Individual Assignment
Project Documents
In partial fulfillment of the requirements in MAEC 1 - Project
Management 2nd Semester S.Y. 2024 - 2025
Presented to:
Atty. Bona Soriano
Presented by:
Lauron, Krystele Mae B.
March 7, 2025
Project Documents
1. Activity Attributes - are details of project activities which are used to help project planning and
scheduling. These details are necessary because they allow the project team not only to understand the
work requirements associated with each project activity, but also to consider how activities may
impact one another and affect the overall project.
2. Activity List – The activity list is essentially an itemized documentation of all of the schedule
activities that are part of a particular project. These lists are typically (and ideally should be) very
detailed and comprehensive, providing as many details as possible to make it as easy and quick as
possible for a user to attain general, broad sheet information.
3. Assumption Log – An Assumption Log is a document where all the important assumptions
made during a project are recorded. It helps project teams understand what they are assuming and
keeps them aware of any potential risks or uncertainties.
4. Basis of Estimates – The Basis of Estimate is part of estimate documentation to record
assumptions and back-up calculations and can be tailored to the project.
5. Change Log – a documented record of all the changes that a software undergoes. Changes made
are then chronologically recorded for users to easily spot the evolution of the product. Following a
defined changelog format can help in tracking the changes made in a systematic way, and help
contributors to identify notable changes easily.
6. Cost Estimates – an approximation of the total cost of a project, program, or operation, which
breaks down the expected expenses into different categories to provide a projected overall price, often
used to help decision-making before committing to a full project;
7. Cost Forecasts - a financial planning technique that organizations use to predict the different costs
they are likely to incur in forthcoming accounting periods or for specific projects. By estimating
future expenses based on the most current information available, they can plan more accurate budgets,
secure the necessary labor and materials and be better prepared to pivot should circumstances change.
8. Duration Estimates – allow project managers to guess how long tasks will take and create a
project schedule. It helps in a better organize system project and to understand the progress. These are
approximations of how much time a project task will take.
9. Issue log –an outline that you can use to track problems or issues as they occur during a project.
This tool helps you establish a process for how to document and keep track of problems during your
project’s timeline.
10. Lessons learned register – is a structured document that teams may use to record their comments
on various project life cycle events. It's a straightforward description of all possible and present issues
within a project. Teams may better monitor projects, reflect and evaluate, collect quantifiable data,
and enhance productivity with the use of templates.
11. Milestone list – a comprehensive document that outlines all the critical events or checkpoints
within a project, signifying significant progress and serving as markers to track the project's timeline
and overall completion.
12. Physical resource –refer to the tangible, material assets that a business or organization utilizes to
carry out its operations and achieve its objectives. These resources include equipment, machinery,
buildings, land, and other physical infrastructure that enable the production and delivery of goods
and services.
13. Project Calendars – a visual representation of the project's timeline, outlining the start and end
dates, milestones, tasks, and resources involved. It provides a comprehensive view of the project's
schedule, enabling project managers to plan, coordinate, and track its progress effectively.
14. Project Communications –an agreement between collaborators and stakeholders that outlines
what, when, and how information will be shared at key intervals. Information like status updates, task
related questions, and meeting details should all be included in this written guide.
15. Project Schedule – a timetable that organizes tasks, resources and due dates in an ideal sequence
so that a project can be completed on time. A project schedule is created during the planning phase
and includes the following: A project timeline with start dates, end dates and milestones.
16. Project Schedule Network Diagram - show the order in which activities should be scheduled to
address logical relationships between these activities. It typically comprises of nodes that represent
activities and arrows that show the sequence and dependencies.
17. Project Scope Statement – is a clear definition of the boundaries of a project. It includes all the
assumptions, responsibilities, requirements, constraints, milestones, and deliverables needed to ensure
the project is a success.
18. Project Team Assignments –refers to the process of distributing specific tasks and
responsibilities within a project to individual team members, ensuring everyone understands their role
and contributes effectively towards the project's successful completion.
19. Quality Control Measurements – A Quality Control (QC) template is a structured document
designed to document, monitor, and evaluate the quality of products, processes, or services. It can be
used to make sure that the products, processes, and services fulfill the established standards.
20. Quality Metrics –are measurable values used in quality management to systematically assess and
control processes within companies. They serve as an objective foundation for performance
measurement and continuous improvement within a quality management system (QMS).
21. Quality Report –a structured document that presents analysis and details to ensure each quality of
products, processes, or services meets certain requirement standards. It serves as a tool to monitor and
track quality at each stage of production, providing valuable insights into how well the company is
meeting its quality objectives.
22. Requirements Documentation – A business requirements document is a report detailing
everything a new project requires for success. This document outlines project objectives, what’s
expected throughout the project lifecycle, and what’s required to accomplish the project.
23. Requirements Traceability Matrix –a tool or a document that ensures all project requirements
are linked to their origin and tracked throughout the project lifecycle. It provides a detailed mapping
of requirements to deliverables, design elements, test cases, and other related artifacts. This
guarantees that each requirement is implemented, tested, and verified.
24. Resource Breakdown Structure – A resource breakdown structure helps project managers
identify, allocate, and monitor resources effectively throughout the project lifecycle. A resource
breakdown structure template is a visual tool used in project management to organize and categorize
all the resources required for a project. It provides a hierarchical breakdown, listing resources such as
personnel, equipment, materials, and facilities in a structured format.
25. Resource Calendars – A resource calendar is a schedule that shows different resource
responsibilities at different times. Often, this refers to staff resources, with the calendar showing staff
member or department assignments and the time currently allocated to each.
26. Resource Requirements – a structured document used to capture and organize this information,
typically including categories for each resource type, their quantities, and estimated costs.
27. Risk Register – A risk register is a document that is used as a risk management tool to identify
potential setbacks within a project. This process aims to collectively identify, analyze, and solve risks
before they become problems.
28. Risk Report – A risk report doesn’t just identify risk; it also describes its potential consequences,
how it’s currently managed, and whether these efforts are sufficient. This is important information that
could affect a company’s health, its profits, or its ability to reach its goals. That’s why these reports
matter, and why they need to be clear, concise, and accessible.
29. Schedule Data – Schedules serve to prepare a job to run at a later time or recurrently following a
time pattern. This refers to the information used to outline and manage a project timeline, including
details like task start and end dates, dependencies between tasks, milestones, assigned resources, and
any constraints that may impact the schedule.
30. Schedule Forecasts – A forecast schedule definition lets you define how revenue should be
apportioned when you run generate Forecasts. You define the proportion of revenue to be forecast and
at what intervals.
31. Stakeholder Register - a tool project managers use to capture and organize information about the
stakeholders who impact the project they’re managing. This document helps project managers analyze
the influence and interest of each stakeholder as they relate to the project throughout its life cycle.
32. Team Charter – a document that outlines a team’s purpose, goals, and approach. It helps get
everyone on the same page about the scope of the team's work and how they will collaborate. A team
charter defines how a team will work together and make decisions. It explains communication
methods, meeting schedules, project collaboration tools, and conflict resolution processes so everyone
can collaborate seamlessly.
33. Test and Evaluation Documents - one such report which determines whether an organization,
software, or program is effectively carrying out the planned activities and is successfully achieving its
stated objectives and anticipated results.
References:
[Link]
/ [Link]
[Link]
r [Link]
[Link]
[Link]
i ng/[Link]
[Link]
[Link]
r [Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
- qo7fc
[Link]
[Link]
[Link]
[Link]
s [Link]