Wendan's Dan Morris is a columnis for PEX and a webinar host for ABPMP.
Dan's columns and papers can be found through the main PEX website and his webinars can be found through the ABPMP website.
Or use our contact form.
We are excited to announce the ADDI (Analyze, Design, Develop, Implement) BPM/BPMS Methodology.
ADDI is the first and only formal iBPM project execution and orchestration methodology.
With over 1,500 formal tasks, ADDI is ready to help with the tough business transformation projects. ADDI is also fleixible and adjustable - by removing tasks it can be customized to eliminate unneeded work and guide smaller business improvement projects. If you need consistency, governance and reduced risk, ADDI is for you.
ADDI was created to provides four things to companies who are doing either BPM or BPMS supported BPM projects. These are:
This combination represents the best of both Waterfall and Agile.
1. Consistent Outcomes:
Improve consistency by providing a common framework for all projects
Reuse of information by applying standards for data collection, modeling, and more
Consistent results through the unique ADDI approach to simulation, iteration and testing
Nothing is forgotten in the project plan and estimates – customize the project plan by selecting needed activities from a list of over 1,000 tasks (do only what you need, but leave nothing out)
2. Improved Control:
Move all BPM project teams to a common approach, using common techniques, and following common standards
Constantly increasing view of the business operation by controlling the way models are built
Improve the ability to manage and oversee projects through a common approach
Ability to innovate and experiment through controlled simulation
Customize project tasks and plan to adjust to the complexity of each BPM project
Identify how the new design will be built and align BPMS application generation with IT application support work
Change the design through controlled iteration and regenerate the BPMS applications
Iterative and improved IT support specs tied to the business design and aligning to its evolution
4. Reduce Risk:
Significantly reduce risk by applying a formal framework for the project
Reduce project risk by supporting controlled design, iteration, simulation, test cycles
Integrate company standards into the task groups to ensure compliance
Iterate, simulate, test, iterate, simulate test – repeat this process until all project goals are met