What Is a Deliverable?

The word deliverable (root: to deliver) is used in software development to describe almost anything that is given to someone. A deliverable is given or presented to a stakeholder because it has some value to the stakeholder or the stakeholder is expected to act upon it. Examples of deliverables include a workflow diagram “delivered” to a stakeholder for review and approval, a database design “delivered” to a database administrator with the expectation that he or she will create a new database, and a new data entry screen “delivered” to software users to improve their process efficiency. To be accurate when talking about business analysis deliverables, the word requirement should be used as a prefix to deliverable. A requirements deliverable is then easily distinguished from a software deliverable, a training deliverable, etc.

Business analysis professionals create requirements deliverables for their stakeholders to confirm understanding of requirements, get approvals, communicate work to developers, communicate needs to vendors, communicate software testing requirements to quality assurance, etc.

Software development methodologies and processes often recommend specific requirements deliverables for their process (i.e., use cases are used with RUP). Many organizations also have company-wide standards that dictate required deliverables (i.e., business case, Requests for Proposal). BAs must be aware of the required/recommended requirements deliverables for their organizations and each particular project. In addition, the BA may decide to create other deliverables to present requirements that are not completely represented by the recommended techniques. It is important that the BA not simply follow the prescribed deliverables blindly. It is the BA’s responsibility to communicate requirements accurately and completely; to fulfill this responsibility, creativity is often required.

System vs. Software

Terms are important in all BA communications. The terms system and software are often used interchangeably, sometimes causing confusion in communications. The word system is defined as a set of connected things or parts forming a complex whole. This word can be used to describe a computer system, an electrical system, a biological system, or a business system. Notice how the addition of a modifier makes the term much clearer. System can also mean a systematic approach to a problem or situation. Software is the programs and other operating information used by a computer.

Be aware that when you use the word system alone, your audience will envision something based on their background and experience. If you are talking with an IT person, he or she will think software. An electrical engineer will think electrical system. A business person will think business system. Use the word system carefully and with a specific purpose.

It Depends

One of the most common phrases that business analysis professionals use is it depends. Much of business analysis work is complex, abstract, and dependent on current circumstances. When a BA is asked about a recommendation for a particular approach or analysis technique, often he or she will start the answer with it depends. Every situation is unique, and BAs bring their problem-solving, communication, interpersonal, and teamwork skills and knowledge to tailor an approach to each new problem.