Deliverables

Deliverables — Meaning, Definition & Full Explanation

Deliverables are the tangible or intangible products, services, or results that must be produced and submitted to a client, stakeholder, or project sponsor as part of a project or contractual agreement. These outputs represent the concrete outcomes of work performed, fulfilling specific requirements or objectives outlined in the project scope.

What is Deliverables?

A deliverable is any specific output that is created during a project and intended to be provided to an internal or external client or stakeholder. These can range from physical items like a new software application, a detailed report, or a constructed building, to less tangible outcomes such as a strategic plan, a training program, or an improved business process. Deliverables are crucial as they represent the value being created by a project and are often tied to specific contractual obligations or project objectives. They serve as evidence that work has been completed and progress has been made, allowing stakeholders to review and approve the project's outputs. The concept of deliverables ensures accountability and provides a clear understanding of what a project aims to achieve and provide.

How Deliverables Works

The process of managing deliverables typically begins during the project planning phase.

1. Identification: Specific deliverables are identified and documented in the project scope statement, work breakdown structure, or contractual agreements, detailing their specifications, quality standards, and due dates.
2. Creation: The project team then performs the necessary tasks to create each deliverable according to the defined requirements. This involves allocating resources, executing tasks, and managing workflows.
3. Quality Assurance: Before submission, deliverables undergo internal quality checks and reviews to ensure they meet the agreed-upon standards and specifications. This step helps in identifying and rectifying any defects or inconsistencies.
4. Submission: Once approved internally, the deliverable is formally submitted to the client, sponsor, or relevant stakeholders. This submission often includes supporting documentation or presentations.
5. Acceptance: The client or stakeholder reviews the submitted deliverable against the agreed-upon criteria. Upon successful verification that it meets all requirements, the deliverable is formally accepted. Acceptance often signifies the completion of a project phase or triggers subsequent actions, such as payment or the start of the next project stage. Deliverables can be incremental, meaning smaller, successive outputs contribute to a larger final deliverable, facilitating continuous progress and feedback.

Deliverables in Indian Banking

In the Indian banking sector, deliverables are integral to various operational, technological, and compliance projects undertaken by financial institutions. When an Indian bank, such as SBI, HDFC Bank, or ICICI Bank, embarks on an IT modernization project, say, developing a new digital lending platform, the project will have numerous deliverables. These might include detailed system requirement specifications (SRS), user interface/user experience (UI/UX) design mockups, software modules, user acceptance testing (UAT) reports, and finally, the fully deployed platform.

Furthermore, deliverables are critical in a regulatory context. The Reserve Bank of India (RBI) frequently mandates banks to submit various reports and compliance documents as deliverables. For instance, following a new RBI circular on cyber security frameworks or data localisation, banks must deliver implementation status reports, audit findings, and evidence of compliance to the RBI within specified timelines. Similarly, for projects funded or overseen by institutions like NABARD (for rural development) or NHB (for housing finance), specific project progress reports, financial statements, and impact assessments serve as crucial deliverables. Candidates preparing for JAIIB/CAIIB exams encounter concepts related to project management, IT systems, and regulatory compliance, where understanding the role and importance of project outputs and reporting as deliverables is fundamental to banking operations.

Practical Example

Consider ABC Bank, a mid-sized private sector bank in India, which has initiated a project to upgrade its core banking system (CBS) to improve customer service and operational efficiency. Mr. Rohan Sharma, the project manager based in Mumbai, is responsible for overseeing this complex undertaking. The project's Statement of Work (SOW) outlines several key deliverables.

One critical deliverable is the "System Integration Test (SIT) Report." This document, once completed, will detail the results of testing how the new CBS modules interact with existing bank systems like the ATM network, mobile banking app, and payment gateways. Rohan's team spends three months conducting rigorous SIT, identifying bugs, and ensuring seamless data flow. Upon completion, the 150-page SIT Report, along with supporting test logs and defect resolution summaries, is formally presented to the Head of IT and the Chief Operating Officer (COO) for review and approval. Their acceptance of this deliverable signifies that the integrated system is stable enough to proceed to User Acceptance Testing (UAT), marking a significant milestone in the ₹50 crore project.

Deliverables vs Project Milestone

While both deliverables and project milestones are crucial for project management, they represent different aspects of project progress.

Feature	Deliverable	Project Milestone
Nature	Tangible or intangible output/result	Significant point or event in a project schedule
Purpose	To provide a specific outcome to a client/stakeholder	To mark progress and track project schedule
Example	A completed software module, a detailed report	Completion of design phase, successful UAT start
Outcome	A product, service, or documented achievement	A point in time, often with no direct output

Deliverables are the actual outputs or products of work performed, whereas milestones are significant points in a project timeline that indicate progress towards completion. A milestone often marks the successful completion or acceptance of one or more key deliverables.

Key Takeaways

• Deliverables are the specific products, services, or results produced during a project.
• They can be tangible (e.g., a report, software) or intangible (e.g., a training program, a strategy).
• Deliverables are crucial for demonstrating progress, fulfilling contractual obligations, and achieving project objectives.
• They undergo creation, quality assurance, submission, and formal acceptance by stakeholders.
• In Indian banking, deliverables are vital for IT projects, new product development, and regulatory compliance reporting to the RBI.
• Successful acceptance of a deliverable often triggers the next phase of a project or a payment.
• Deliverables are distinct from project milestones, which are simply points in time marking significant progress.
• Proper management of deliverables ensures accountability and client satisfaction.

Frequently Asked Questions

Q: Are deliverables always tangible? A: No, deliverables can be either tangible or intangible. Tangible deliverables include physical products, software, or reports, while intangible ones could be services like training programs, strategic plans, or process improvements.

Q: How do deliverables impact project timelines? A: Deliverables are intrinsically linked to project timelines as they often have specific due dates. Delays in producing or getting a deliverable accepted can push back subsequent project phases, impacting the overall project schedule and potentially increasing costs.

Q: Who is responsible for accepting deliverables? A: The responsibility for accepting deliverables typically lies with the client, project sponsor, or relevant stakeholders who defined the requirements. Their formal acceptance confirms that the deliverable meets the agreed-upon specifications and quality standards.