View source for Deliverable of the project

A '''deliverable''' is a tangible or intangible [[product]], result or [[capability]] that must be produced to complete a [[project]]. It is a measurable, verifiable outcome that can be used to demonstrate the completion of a project and its success. Deliverables are typically defined in the project’s scope of [[work]] and can include items such as an activity, document, report, software application, [[system]], [[process]], or procedure. Deliverables should be measurable, precise, and should meet the [[objectives of the project]].

==Example of deliverable of the project==
* A project deliverable could be a report on the findings of [[customer]] research.
* A project deliverable could be a website design that meets user experience and accessibility standards.
* A project deliverable could be an app that has been tested for bugs and meets the requirements of the customer.
* A project deliverable could be a [[marketing]] campaign that includes a [[strategy]] and budget for advertising, content creation, and public relations activities.
* A project deliverable could be an interactive [[training]] program that meets the objectives of the training program.

==Best practices of deliverable of the project==
# ''' Clearly Define the Deliverables''': The project manager should clearly define the deliverables in the [[project scope]] and ensure that all [[stakeholders]] agree upon them. This will help ensure that the deliverable is produced accurately and on time.
# ''' Scheduling''': When creating the [[project schedule]], the project manager should include a timeline for each deliverable and set clear expectations for when each deliverable should be completed.
# ''' Monitor Progress''': The project manager should monitor the progress of each deliverable and ensure that it is produced on time and according to the project scope.
# ''' Establish [[Quality]] Standards''': The project manager should establish quality standards for each deliverable and ensure that they are met. This will help ensure that the deliverable meets the expectations of the stakeholders.
# ''' Document and Archive''': The project manager should document and archive the deliverables, so that they can be easily accessed and analyzed in the future. This will help to ensure that the results of the project are available for future reference.

==When to use deliverable of the project==
Deliverables are used throughout the [[project life cycle]] to ensure that the project [[goals and objectives]] are met. Deliverables can be used to monitor progress, ensure [[quality of work]], communicate project status and milestones, and to determine the success or failure of the project. The following are some common uses of deliverables in a project: 
* '''To define project scope''': Deliverables are used to define the boundaries of the project, and to provide a basis for measuring progress and performance.
* '''To provide project [[documentation]]''': Deliverables are used to provide documentation of the project at the end of each phase. This documentation can include reports, presentations, requirements documents, and other materials.
* '''To measure project performance''': Deliverables can be used to measure the [[performance of the project]] and the team members involved.
* '''To communicate project status''': Deliverables can be used to communicate the project status to stakeholders, including current progress and any changes to the project [[plan]]. 
* '''To identify and resolve issues''': Deliverables can be used to identify and resolve issues that arise during the project.
* '''To ensure quality of work''': Deliverables can be used to ensure that the quality of work meets the expectations of the project stakeholders.

==Types of deliverable of the project==
The following are types of deliverables of a project:
* '''Documentation''': Documentation is a written or printed report that provides [[information]] about the project, such as the project plan, requirements, and design.
* '''Requirements''': Requirements are the expectations for the project, such as the customer’s [[needs]], goals, and objectives.
* '''Design''': Design is the process of creating the project’s architecture, components, and interfaces.
* '''Code''': Code is the programming language used to create the software applications or systems used in the project.
* '''Test Results''': Test Results are the outcomes of tests performed on the project. These results are used to ensure the project meets its quality standards.
* '''System''': System is the hardware and software components used to develop, deploy, and maintain the project.
* '''Processes''': Processes are the procedures used to manage the project, such as the project [[management]] process, [[software development]] process, and [[quality management]] process.
* '''Procedures''': Procedures are the steps used to complete tasks in the project, such as user [[acceptance testing]], installation, and maintenance.
* '''Reports''': Reports are the documents used to track and monitor the project, such as status reports and progress reports.

==Advantages of deliverable of the project==
Deliverables are an important part of a project, as they provide tangible evidence that the project has been completed. Some of the advantages of deliverables include:
* '''Improved Visibility''': Deliverables provide a consistent, defined result that can be viewed and assessed by stakeholders, providing improved visibility into the progress of a project.
* '''Enhanced [[Communication]]''': Deliverables help to ensure that all stakeholders are in agreement about the project’s objectives, timeline, and outcomes.
* '''Improved [[Efficiency]]''': Defining deliverables reduces [[risk]] and improves the efficiency of a project, as everyone involved is aware of what is expected.
* '''Increased Accountability''': Defining deliverables also helps to ensure that all stakeholders are held accountable for the successful [[completion of the project]].
* '''Improved Quality''': Having an agreed-upon set of deliverables helps to ensure that the project’s quality is consistent and meets the expectations of stakeholders.

==Other approaches related to deliverable of the project==
The following are other approaches related to delivering a project:
* '''Project [[Planning]]''': This is creating a plan that identifies the tasks, resources, and timeline needed to complete a project. It should also include [[risk management]], budgeting, and [[quality control]] measures. 
* '''Project Scheduling''': This is the process of determining the order in which tasks [[need]] to be completed in order to meet the project's timeline. It involves creating a timeline, assigning tasks and resources, and managing dependencies.
* '''[[Resource]] Allocation''': This is the process of assigning the right resources to the right tasks at the right times. This includes managing personnel and materials, as well as ensuring that resources are used efficiently.
* '''Project Monitoring''': This is the process of tracking project progress, identifying and addressing any risks or issues, and making sure that the project is on track to meet its objectives.
* '''Project Closure''': This is the process of formally ending a project and making sure that all deliverables have been met. It involves reviewing the project, assessing its success, and providing any necessary documentation.
In summary, other approaches related to delivering a project include project planning, scheduling, resource allocation, monitoring, and closure. All of these approaches help to ensure that the project is completed on time, within budget, and with the desired results.

{{infobox5|list1={{i5link|a=[[Traditional project management]]}} &mdash; {{i5link|a=[[Organizational project management]]}} &mdash; {{i5link|a=[[Quality of project]]}} &mdash; {{i5link|a=[[Applications of project management]]}} &mdash; {{i5link|a=[[Project scope]]}} &mdash; {{i5link|a=[[Project boundary]]}} &mdash; {{i5link|a=[[Delivery of the project]]}} &mdash; {{i5link|a=[[Plan and schedule]]}} &mdash; {{i5link|a=[[Life cycle approach]]}} }}

==References==
* Rad, P. F. (2003). ''[https://www.angelfire.com/ex/sixx/ProjectSuccess.pdf Project success attributes]''. [[Cost]] Engineering-Morgantown, 45(4), 23-29.
* Jaber, H., Marle, F., Vidal, L. A., & Didiez, L. (2018). ''[https://idp.springer.com/authorize/casa?redirect_uri=https://link.springer.com/article/10.1007/s00163-017-0254-7&casa_token=BoBG9fMDmskAAAAA:lCsMF8bvg1m3reEZ9C_4cfmYMF23pu6yY7dMTeO6HXvFemURCnNKFXApqNQkVxWrQj3x_-O0LXSvPzcc Criticality and propagation analysis of impacts between project deliverables]''. Research in Engineering Design, 29, 87-106.
[[Category:Project management]]