Risetime defines, builds, and delivers BPM and DM solutions iteratively over several phases. In a typical waterfall methodology detailed requirements would be created and signed off before starting any work. However, Risetime uses a slightly different approach for delivering Business Process and/or Document Management solutions. Specifically, Risetime uses a rapid application development methodology that takes the best-of-breed concepts from the Rational Unified Process and Agile Development Process.

The Vision and Solution Definition Phase 

• Define the plan for what the system does at a high-level.
• A combination of high-level requirements with some design elements. 
• Capture the business processes and mockup screens for the new system. 
• Risetime performs extensive current-state and future-state process analysis.

Building Your Solution

In the next phase, Risetime completes two (2) solution build cycles.
In each of these cycles, in working with you, we will:

• Finish design and build a working application (although untested) based on the solution definition.
• After each cycle, the business users are brought in to provide feedback on the application.
• If required, we can provide detailed design documents

System Integration Phase

 includes extensive unit testing of the final application and building the components that will talk to any backend systems or other applications. Typically, in the previous phase these components are not built as they may not impact the user experience for the application being built. After completing these integrations, the system is tested end to end. The User Acceptance Testing Phase is formally testing the application with the end users and receiving signoff on the finished product. As mentioned previously, we believe this is best accomplished via a parallel pilot program. The Risetime approach significantly reduces the risk of scope creep and missed requirements at this point as the users have actually seen the application at least twice. 

Deployment phase

These are the final steps taken to ensure proper delivery of the system. Tasks such as training and knowledge transfer are also typically included in this phase. We create prototype screens and models that allow the user to visualize the solution. We do not create a formal requirements document that contains every detail of the system. Our experience shows us that requirements will change throughout the project. This is a good thing and must be embraced by the stakeholders and the business users – it is natural to continuously improve the processes and screens over the phases of this project. Trying to think of every detail up front is a waste of time and dollars and in our opinion is an unattainable goal. The business users and Risetime should not be expected to think of every detail up front. This is not the way businesses processes work in the real world (they evolve over time), so why should projects that automate business processes be expected to be any different. For this specific project, once product selections are made, Risetime is ready to build a prototype application for the users to demo and provide feedback. No further formal requirements will be gathered. We expect and have planned for requirements to change and be refined as part of the prototyping process during the phases of this project.

Before an organization embarks on any solution, the organization must embrace the concept on continuous process improvement.
Risetime educates our clients on the overwhelming benefits of this approach.
As an organization, it is much better to be agile than to be perfect with your processes and applications. The most successful organizations are the ones that have the ability to change their processes in response to the ever changing market place.