The Deliverable Prototype is the first development step in implementing Iterative Development on your project. The Deliverable Prototype is a complete skeletal model of the deliverable application. As such, it contains source files for data entities, domain modules, user screens and supporting code modules called out in the technical design.
The Deliverable Prototype contains all new or novel combinations of technologies contemplated in the project technical design. This includes any new database access technologies, user interface component sets, user interface themes, reporting tools and deployment platforms needed to demonstrate feasibility.
The solution domain naming convention, called out in the project technical design, is codified and vetted in this skeletal application.
The Deliverable Prototype is the primary responsibility of the project technical lead until the first Project Build and Demonstration is completed.
Creating a Deliverable Prototype provides the following advantages:
In addition, a Deliverable Prototype that is available for demonstration and feedback will generate specific requests for functionality and user interface features that are overlooked when application design is performed starting with a blank screen. This allocation of resources, beginning with a tangible but empty demonstration, energizes the prospective user community with the prospect that their concerns are being heard and shaping the application they will soon use. This exercise also empowers the user community representative and helps start the process of prioritizing feature requests into individual milestone requirements lists.
The Deliverable Prototype and Deployment scheme are critical inputs for the specification of the Project Delivery System. By completing this step, your project and management are assured that you can deliver and deploy your latest version of a working prototype, at the very least to a location on your development network.
The sole difference between any of your prototypes and a deployable product is now a successful acceptance test. Once you complete automating your build and deployment scripts, each successive project build will be more predictable, reliable and testable because the error-prone complexity and custom nature of your unique project build will be encapsulated. When deadlines loom, this effort pays for itself many times over and can be the margin of success by freeing resources for testing and handling exceptional conditions, only found in the production environment.
The sections of this presentation are structured to be read once, sequentially, and then as needed in any order. The navigation links to the left and section descriptions below appear on every page.
To continue now with the iterDev.com Iterative Development Process, click each of the links to on the left in order. A brief description of each document's contents is below. The 'Home' link returns you to the home page.
Foreword - iterDev.com Home page and Author's Foreword to the Iterative Software Development web site.
Introduction - iterDev.com Introduction, Background and The Iterative Development Force Multiplier.
Iterative Process Model - The Iterative Development Process Model, its place in the Software Development Lifecycle and expected benefits.
Deliverable Prototype - The Deliverable Prototype, its down stream Advantages for projects and the Work Product that delivers them.
Development Process - The Iterative Development Process, Activities and their mapping to SDLC and a closer look at the core Iterative Development Cycle.
Project Delivery System - The Project Delivery System: Activities, Activity Specifications and how they combine to produce Managed Project Releases.
Epilog - A few final thoughts. A request for comments. What I hope to achieve with this site.