Development
The Work Plan batches produced as part of the Architecture Modelling step form the basis for the agile development workflow.
Batches can be adjusted and rearranged as the Development continues in order to accommodate new ideas, changes in scope and discovery of new information.
However the full delivery plan “as it stands today” is visible for all to see, and for the rest of your business to make decisions around.
Engineering
Engineering provides the bridge between Architecture and Construction.
It enables business analysts and customers to understand the specifics of what will be built and exactly how the solution will operate.
For each part identified in modelling, engineers detail how the developer is expected to implement the Parts in order to meet your objectives.
Deliverables
Part Schema
For every part in the Work Plan batch engineers produce a Schema defining why the part exists and what it should do and how it should operate.
This is the critical link between your idea and what the programmers will construct.
This schema forms the basis for capturing your knowledge, providing guidance to the programmers, testers and serves as the key documentation for long term maintenance of the part.
Batch QA Plan
A QA plan defining how developers and testers should go about proving they have produced the expected outcome.
Construction
Writing code to meet the requirements set out in Engineering.
This is much easier and clearer than the traditional method of relying on programmers to work out what should happen as they code.
Deliverables
User Acceptance Environment.
The working component is delivered to an environment that you can use to test
That the developers have done what you agreed to in the engineering
more importantly, does that meet your needs now that you have seen it in action.
Construction Proof QA.
Based on the risk profile the expected happy path and planned boundary case tests are either automated or manually executed based on requirements and budget.
Quality Control
Extended scenario testing outside of constructions "proof".
Directed by Project Risk Profile, QA seeks to validate newly added code against all prior code, throughout as many permutations as is practical within budgetary constraints.
User acceptance testings ensures delivered code firstly meets the agreed Engineering specification AND that the solution is "fit for purpose".
Deliverables
Planned test output
Creating and executing a series of tests plans to validate the risks and assumptions of both the business and the developers. The output shows you what worked and what didn’t giving you confidence to proceed with the next steps.
Automated test results
Like the test plans, Automated test results provide faster and easily rerunnable tests that provide a higher return on investment over time as the solution grows, these tests ensure there have been no breakages.
Freeform test output
While formal tests and automated tests handle the “predicable” or “Known unknowns” freeform testing attempts to find the unpredictable once the solution is written. This is a critical quality aspect that ensures customers are given the best possible experience.
Redprint Adaptive Deliver Process.
Redgums adaptive framework applied to manage the varying risks of a broad range of projects.