How to Organize Deliverables

    It's a well known fact that, when working on large projects and/or in large companies, organizing deliverables may become a pain. The purpose of this article is to propose you a few best-practices for this.

    With not too much attention to the documents we need to prepare, we can discover that basically we deliver documents with just two purposes: business improvement and project definition:

Business Processes

• Business Rules
• Decision Tables

Business Requirements - User Stories

• Stakeholder Requirements - Use Cases
• Solution Requirements

            - Functional Requirements
            - Acceptance Criteria
            - Non Functional Requirements

• Transition Requirements

    If you ever worked on one purpose, or the other, or both of a Business Analyst' deliverables documents, my assumption is that you got these points above. For more details, please read this article.