Project Documents Examples
|
|
|
1. Empty DeliverableEmpty structure of a Word document. Such a deliverable may be used as a template already set with logos and Company references, simple or with cover.
|
2. Software VendorsSoftware Vendors reports a complete list of all the vendors involved together with a brief description per each Vendor. Such a list may be used many times along different Projects as a Best Practice.
|
3. Hardware VendorsHardware Vendors contains a complete list of all the vendors involved together with a brief description per each Vendor. This list may be used over and over again as a Best Practice.
|
4. Software AttachmentThis document provides a detailed Software Architecture description of what is in scope together with the list of possible Operative Systems (Software Vendors are not included).
|
5. Hardware AttachmentHardware class definition (Hardware Vendors are not included). This document provides a list of technological environments typically used while delivering a Software solution (e.g. Development, Test, etc.)
|
6. Database AttachmentThis document contains a list of all the Databases potentially in scope, together with Database Data Types used to define table fields and a coincise/effective description of what a CRUD (Create, Read, Update, Delete) matrix stands for.
|
7. Network AttachmentThis deliverable contains the list of Network locations - e.g. where Users and Data Centers are distributed - together with data exchange frequencies, allowing to set up the basis for Integration Architecture and Database Growth Trend.
|
8. Prof. Services AttachmentProfessional Services Profiles shows the list of professionals who might/would be involved along a Project (e.g. Project Manager, Senior Consultant and so forth) without any reference to their daily cost.
|
9. Technical AttachmentThis document represents the sum of Software, Hardware and Database technical deliverables together with Professional Services Profiles, providing a detailed view of the technical side of a Project.
|
10. Application ArchitectureApplication landscape detailed architecture, showing the whole set of Enterprise Applications in scope of the Project, clearly described through market and technological details. Cost is not included.
|
11. Application Business CaseThis document describes the Application landscape (which Applications are in scope of the Project) together with the related Users per Application, offering a detailed view of the Total Application Cost together with a 5 years cost projection.
|
12. Hardware ArchitectureHardware detailed architecture, showing the list of Hardware Platforms described in terms of how many environments per Application would be necessary, together with Class of computation and Vendor. Cost is not included.
|
13. Hardware Business CaseThis document describes the overall Hardware landscape offering a detailed view of the single server cost (development, test, pre-production and production servers) together with the Total Hardware Cost in scope of the current Project.
|
14. Architecture AttachmentOmni comprehensive Application Architecture document which provides the accurate cost of the Software in scope within the Project, considering the number of Users and the class of the hardware used (e.g. how many cpus, how many cores per cpu, if Production only or Pre-Prod either and so forth).
|
15. Project Reqs AttachmentThis Document provides an estimation of the Project Effort based on how many Project Manager mandays would be required per week on a global elapsed together with a more detailed analysis based on Project Requirements and macro planning. Cost is not included.
|
16. Software RequirementsThis deliverable is able to list the Application Requirements expressed in terms of Functionalities, Priority and Availability together with the Data Entity the Functionality itself would operate upon, where the operation is one of the combinations allowed through the CRUD specification.
|
17. Entity Relationship ModelThe Entity Relationship Model shows at an high level design how the data Entities related to all the Applications in scope of the Project are in relationship with each other.
|
18. Integration ArchitectureAlong with a complex Application landscape, this deliverable reports the set of Integrations (e.g. Data Flows) between all the Enterprise Applications in scope, specifying the Frequency any single Integration is required to act.
|
19. InterfacesThis deliverable provides the list of Application Interfaces which are necessary to design System Integrations, showing the detailed set of data elements exchanged through any single software Integration.
|
20. Database Growth TrendRemember all the times a Customer asked how much a database was supposed to grow over time, in a way to plan in advance the required storage? This deliverable - Database Growth Trend - provides an accurate estimation out of Users daily operations and Integrations exchanges, expressed in Gigabytes.
|
21. Functional AttachmentThis document is the sum of Functional Requirements, Entity Relationship Model, Integrations and Interfaces up to Data Growth Trend all together, in order to offer one omni comprehensive Functional Attachment to the Customer.
|
22. Test StrategyTest Strategy is a deliverable dedicated to gather Test Groups, meaning the superset of Tests which are necessary to be addressed before User Acceptance, together with the list of Tests which belong to every Group of Tests. Test Groups and Test Lists are necessary to address Quality Assurance and precede the creation of User Acceptance Test Cards.
|
23. User Acceptance Test CardsThis deliverable provides the ability to set up a detailed Test Scope description and build Test Cards, which are necessary to allow User Acceptance and enable the Project Go Live.
Specifically, Test Cards are made of Test Case, Functionality, Input, Output, Sequence and Description. |
24. Sales Commercial ProposalHave you ever experienced the complexity of creating a Sales Commercial Proposal - Software Applications, license criteria, legal Terms & Conditions, discounts, maintenance and so forth? This deliverable allows to automatically create a Software Commercial Proposal - Professional Services excluded - to be delivered directly to the Customer.
|
25. Professional Services ProposalThe other side of a Commercial Proposal is based on Professional Services - how many mandays per professional profile on tasks/activities, filtered by specific Legal Terms and Conditions, already provided through the software but always customizable. This deliverable allows to automatically create a Professional Services Proposal - Software excluded - to be delivered directly to the Customer.
|
26. Project Status ReportOne of the most annoying - and yet important - project activities is that of preparing a weekly Status Report referred to the ongoing Project. Any macro actvity requires to be analyzed through an accurate snapshot and communicated to the Project Board accordingly.
|
 |
 |
