<div class="figure"> <a class="reference external image-reference" href="https://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.svg"> </a> </div> <a name="business-requirement-deliverable"></a> <h2>Business Requirement Deliverable</h2> <a name="introduction"></a> <h3>Introduction</h3> <p>This module is part of a set (&quot;Business Requirement&quot;). The Business Requirements features start as independent entities, and can be used as standalone.</p> <p>Additional modules integrate them with other business areas, such as Sales, Procurement, Project or Analytic Accounting. For example:</p> <ul class="simple"> <li>Sales Quotation can have an estimation supported by a BR analysis</li> <li>Project Tasks can be related to the BRs they implement or support</li> <li>Procurement and purchase can be generated out of the BR</li> </ul> <div class="figure"> <img alt="Business Requirement List view" src="static/img/bus_req_tree.png" style="width: 600px;" /> </div> <p>The following diagram gives a simplified view of the universe:</p> <div class="figure"> <img alt="Business Requirement modules diagram" src="static/img/bus_req_module_diag.png" style="width: 600px;" /> </div> <a name="what-is-a-business-requirement"></a> <h3>What is a Business Requirement?</h3> <p>A Business requirement (BR) is the expression of a business need by a customer or internal project user. A BR can contain multiple different parts depending on the company needs:</p> <ul class="simple"> <li>Customer Story: this is the requirement as expressed by the customer</li> <li>Scenario: How/where the current solution can provide a suitable scenario to answer the customer story</li> <li>Gap: For the uncovered part of the scenario, elaborate the gap/need for specific developments/setup</li> <li>Deliverables to be provided to the customer/user</li> <li>Resources necessary to achieve the deliverables</li> <li>Additional information (approval, cost control etc.)</li> </ul> <p>These modules were originally designed for the service/IT industry but the requirement management is generic and can apply to many cases/industries (customer or internal projects):</p> <ul class="simple"> <li>Construction</li> <li>Trading (New product development)</li> <li>Business Consultancy</li> <li>IT development</li> </ul> <p>What is the difference between a BR and CRM lead?</p> <ul class="simple"> <li>CRM leads are sales oriented</li> <li>BR are project and workload estimation oriented</li> </ul> <a name="how-to-use-this-module"></a> <h3>How to use this module?</h3> <p>This module introduces 2 main concepts in the business requirements model:</p> <ul class="simple"> <li>Deliverable lines</li> <li>Resource lines</li> </ul> <p>What is a Deliverable Line?</p> <p>Deliverable Lines (DL) contains products and services that we will deliver to the customer. They are <strong>customer oriented</strong> and can be either physical or service products</p> <ul class="simple"> <li>Servers and procured goods</li> <li>Gap analysis services</li> <li>Module development services</li> <li>Training etc.</li> </ul> <p>DL directly depends on the BR.</p> <div class="figure"> <img alt="Business Requirement Deliverable lines" src="static/img/bus_req_deliverable.png" style="width: 600px;" /> </div> <p>What are Resources Lines?</p> <p>Resources Lines (RL) are the different tasks or procurements needed to achieve one deliverable:</p> <ul class="simple"> <li>Service tasks (Development, consultant etc.)</li> <li>Procurement of other physical goods (server, etc.)</li> <li>Procurement of other virtual goods (templates, sub-contracting, etc.)</li> </ul> <p>RL directly depends on the DL.</p> <div class="figure"> <img alt="Business Requirement Resources lines" src="static/img/bus_req_resource.png" style="width: 600px;" /> </div> <p>What is the difference between Deliverable and Resources?</p> <p>Deliverables are:</p> <ul class="simple"> <li>provided to the customer (“Functioning Website”)</li> <li>Valued at Customer Sales Price</li> <li>Used in Sales Quotations</li> </ul> <p>Resources are:</p> <ul class="simple"> <li>executed internally (“Server+CSS modifications”)</li> <li>Valued at Cost Price</li> <li>Used in Project management or procurement management</li> </ul> <a name="example"></a> <h3>Example</h3> <ul class="simple"> <li>BR1<ul> <li>DL1<ul> <li>RL1</li> <li>RL2</li> <li>RL3</li> </ul> </li> <li>DL2<ul> <li>RL4</li> <li>RL5</li> <li>RL6</li> </ul> </li> </ul> </li> <li>BR2<ul> <li>DL3<ul> <li>RL7</li> <li>RL8</li> </ul> </li> <li>DL4<ul> <li>RL9</li> </ul> </li> </ul> </li> </ul> <a name="installation"></a> <h4>Installation</h4> <p>No specific steps required</p> <a name="configuration"></a> <h4>Configuration</h4> <a name="users"></a> <h3>Users</h3> <p>No specific ACL are required for the module.</p> <a name="master-project"></a> <h3>Master project</h3> <p>You can define a master project linked to the business requirement.</p> <p>You have to specify a estimation price list in the master project, used for deliverable price management. If no pricelist is specified in the project, the one from the customer associated will be used.</p> <a name="usage"></a> <h4>Usage</h4> <ol class="arabic simple"> <li>In the BR, you can add as many deliverable lines as necessary. Price of the deliverable lines will depend on the pricelist in master project or customer.</li> <li>Once the deliverable lines are created you can create as many resources lines as necessary in each DL. Cost price of the product will apply</li> <li>in RL you can already assign the responsible of the task if necessary</li> </ol> <div class="figure"> <img alt="Inputing the deliverables and resources lines" src="static/img/bus_req_deliverable2.png" style="width: 600px;" /> </div> <div class="figure"> <a class="reference external image-reference" href="https://runbot.odoo-community.org/runbot/222/8.0"><img alt="Try me on Runbot" src="https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas" /></a> </div> <a name="bug-tracker"></a> <h4>Bug Tracker</h4> <p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/business-requirement/issues">GitHub Issues</a>. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.</p> <a name="credits"></a> <h4>Credits</h4> <a name="contributors"></a> <h5>Contributors</h5> <ul class="simple"> <li>Eric Caudal &lt;<a class="reference external" href="mailto:eric.caudal&#64;elico-corp.com">eric.caudal&#64;elico-corp.com</a>&gt;</li> <li>Alex Duan &lt;<a class="reference external" href="mailto:alex.duan&#64;elico-corp.com">alex.duan&#64;elico-corp.com</a>&gt;</li> <li>Xie XiaoPeng &lt;<a class="reference external" href="mailto:xie.xiaopeng&#64;elico-corp.com">xie.xiaopeng&#64;elico-corp.com</a>&gt;</li> <li>Victor M. Martin &lt;<a class="reference external" href="mailto:victor.martin&#64;elico-corp.com">victor.martin&#64;elico-corp.com</a>&gt;</li> </ul> <a name="maintainer"></a> <h5>Maintainer</h5> <div class="figure"> <a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a> </div> <p>This module is maintained by the OCA.</p> <p>OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.</p> <p>To contribute to this module, please visit <a class="reference external" href="https://odoo-community.org">https://odoo-community.org</a>.</p>