OxBridge-IT Solution Development Approach
OxBridge-IT Solution Development Approach
The Dynamic Development
Approach is used as a blueprint for the implementation of technologies to
support business processes.
It is scaleable and can be adapted
for use in a variety of projects from simple short adaptations of standard
packages through to bespoke, complex, integrated projects. Dynamic Development
Approach is based on the industry standard DSDM.
It is deployed when a significant portion (Business Impact) of a project or Project is suitable for RAD development (passes the DSDM suitability Filter test). In order to deliver a Project in a quality, timely and cost effective manner, Dynamic Development Approach is deployed into the following phases:
| Define
Phase – an exercise focussed on high level requirements, issues and plans | |
| Design Phase – production of project plans, business requirements, package selection (if applicable), technical architecture and interface design. |
| Develop
Phase – RAD and Traditional development workstreams of the required
functionality | |
| Demonstrate
Phase – RAD & Traditional based testing of the required functionality
(UAT in model office) | |
| Deployment
Phase – migration and rollout of the accepted solution. | |
| The
RAD features of the approach take the DSDM methodology as the starting
point. |
These features include
timeboxing, prototyping and developing functionality against prioritised
requirements, to ensure that the available time and budget concentrates on
delivering the greatest business benefit.
Moreover, OxBridge-IT recognises
that not all of the components of a project are suited to DSDM or RAD, and
require more traditional development approaches to be used i.e. a Traditional
(waterfall) approach.
Thus Dynamic Development Approach
is clearly a business focused approach to the development and delivery of
technology based solutions.
It is used to deliver
business benefit from technology, as quickly as possible, using the rule of 10
(significant project milestone every 10 days, significant benefit delivery every
100 days; this is halved for small project).
Because the approach refers
to business benefit throughout and relies on close involvement of the business
community the delivery of the solution into the business is smoothed, ensuring
that “business as usual” is not interrupted.
Business users must be an integral part of the development, full time or
at least in regular contact with all requirement, design and implementation
decisions.
A successful implementation
can not happen unless there is strong mechanism for managing complexity i.e.
project management approach.