A Balanced Approach
In today's competition-driven business environment, companies depend on eBusiness applications and solutions to achieve and maintain a competitive edge. Yet eBusiness deployments often turn into runaway projects with significant cost overruns. When these overruns occur, clients lose much of the strategic value they hoped to gain from the new application and solution.
dazzleM!'s Strategic VisioneeringSM, a suite of proven rapid deployment methodologies, gives you a safe and effective choice when it comes to implementing your eBusiness solutions and mapping your route to the future.
A comprehensive, five-phase methodology for delivering e-business solutions, Strategic Visioneering uses proven/tested software components that accelerate application development and mitigate risk. It addresses technical architecture, provides complete decision support, and successfully executes legacy, intra/internet and package integration. A carefully designed management process that includes end-to-end plans, charters, techniques, and estimating metrics ensures successful, on-time project completion.
Project Management and Control
dazzleM!'s philosophy is that a successful project requires a close partnership with our clients and a meticulous project governance methodology.
dazzleM! also provides each customer with a password protected Extranet site dedicated to their project that includes all project documentation, status reports and meeting minutes, and online access to system prototypes and works-in-progress.
Training and Documentation
Training and documentation go on throughout the entire project lifecycle. Mentoring and hands-on collaboration are a standard feature of our blended-team approach.
Strategic VisioneeringSM
dazzleM!'s Strategic VisioneeringSM project plans follow a common sense, industry-standard, phased methodology, which has been in use for decades in companies like IBM. Each phase allows for refinement of deliverables to ensure development can proceed on compressed time-lines.
Initiation
The initiation phase provides a strong common foundation from which to launch the project as well as consistent expectations among all the participants. Deliverables and activities include project staffing roster, roles and responsibilities guidelines, reporting procedures and formats, risk management procedures, escalation list and guidelines, analysis and recommendation of deployment platforms, online library of relevant project documents, plan and estimate for the analysis phase, plan and estimate for project to completion, and a communications plan for key parties and stakeholders.
Analysis
The analysis process delivers an in-depth understanding of the nature of the business problem to be solved and the shape of the technical solution. Extensive prototyping is typically used in this phase to help the various users (audiences) of the application refine their needs. Analysis ensures that application requirements are locked down, the parameters of the solution are defined and the framework for quality assurance is established.
Design
A detailed technical solution and the recipe to implement it are accomplished during the design phase. External, user-visible architectures are complemented with an internal technical architecture that guides the implementation. During this phase, the internal details of the application are locked down and plans for development are finalized. Based on these deliverables, the project plan is updated and refined to reflect the improved understanding of the application and the effort required to produce it.
Development
During development, frequent milestones and demonstrations of work-in-progress ensure that the implementation is in line with the expectations for the project and visible to all stakeholders. To the extent possible, organization of work activities is consistent with the organization of the application itself, so that the work product gradually becomes live and useable. Deliverables during the development phase include preparation of the development and QA environments, production and testing of application code, preparation of the user training program and materials as well as development and roll-out of application support and operations documentation.
Delivery
The delivery phase features formal acceptance testing, in both a QA and live environment, to ensure that the deliverable performs as expected, and is followed by launch of the application to the user community. Testing is done against criteria developed first in the analysis phase and maintained throughout the development lifecycle, providing a sure yardstick for success.