Built around advanced BPM concepts
To address the issues that experience with BPM/BPMS projects has proven will be encountered; the ADDI development team created several new approaches and techniques, and modified others. These approaches and techniques are unique to ADDI and help it reduce risk, reduce cost, and improve the quality and consistency of BPM/BPMS projects. These are:
Built around the recognition that a Hybrid approach formed from both Waterfall and Agile methodology approaches is needed to provide consistency, control, and flexibility
Focused on the delivery of defined outcome state – with alignment of vision, strategy, outcome, goals, capabilities, processes, workflow, rules, problems, data, and applications
Applying Strategic Lean with incremental deployment design to ensure design optimization and control development and deployment
Breakpoint analysis with fault detection to identify the way problems build in the work and mitigate them
Evolutive Requirements Definition – a new approach to defining business and IT solution requirements, designed to support a phased approach to change and to eliminate the problems with fitting together the parts of a solution created by multiple teams
Solution Simulation with iterative design and application generation to ensure that all KPIs and targets are met
Solution Lab – Model Office to ensure that the solution is optimal in actual use
Evolutive Management approach to continuous improvement to deliver innovation
Collaborative/holistic engagement of participants to manage the discipline mix and ensure that the change is done with those affected, not to them
Leveraging these approaches and techniques, ADDI is designed to be business, not technology, driven. While we recognize that technology is critically important, the applications that are built or generated, the technology that is used, and the way the customer will interact with the technology is strictly a business function. This focus is unique to ADDI. We prefer to tie into your BPMS vendor’s tool focused method and your in-house Agile methods and link to the parts of them we need rather than try to replace them.