2080 Development Cycle
From 2080 Development community.
To make sure projects have a beginning and an end, while remaining adaptable, the 2080 methodology prefers a five step approach to a project. The three middle steps follow a classic 'PDCA' (plan-do-check-act) approach (also used in six sigma), while the first and last step are more proprietary especially in the importance of the business case in the first step.
For description of the 2080 Team roles and responsibilities, click here.
Contents |
[edit] First Prototype
During this phase, a first prototype of the application is built. This is used for both user validation and making the business case. It is not meant to be deployed but has about 80% of features and functionality.
Deliverable:
- Design approval
- Functionality Draft
Use:
- Proof of concept
- Business validation
[edit] Second Prototype
Once the business case is made, and the decision to complete the project has been taken, 2080 continues with four more steps. These are agile-like, in that changes and adaptations are welcomed if they benefit the business. The steps are, however, delineated to make sure a project remains a project, not a lifelong experience. The second prototype has a finalized and approved design, still 80% of final functionality (because required functionality is updated based on the user feedback from the first prototype) and delivers a fully working product for at least 40% of functionality
Deliverable:
- Final Design
[edit] Alpha Version
The last three iterations validate the development already done, while continuously aligning completion with business needs. The Alpha Version has 80% of functionality working, ready for testing.
[edit] Beta Version
The Beta version should be functionally correct, with 90% of functionality working and approved after testing.
[edit] Release Version (Project Closure)
The Release version has full functionality, working and tested. In this phase, user documentation is built, pilot groups are using the application and application support staff is trained. Full roll-out is then done by the pilot users and application support staff.
Deliverable:
- Working Application, aligned with business needs
- Documentation
- Core users able to support the application (transfer to 'operations')
