There are three types of implementation sprints:
1. Functional sprints
2. Integration and infrastructure sprints
3. Feedback sprints
FUNCTIONAL SPRINTS //
Functional sprints implement one or more components of the Q system. They have a self-contained set of deliverables that include: discovery, definition of success criteria, recommended processes, implementation, testing, and documentation.
The Q functional sprints are typically comprised of 6-8 weeks of delivery effort that allow us to implement a component of our application for use and value achievement by our clients. Each functional sprint, by design is focused on delivering the client the most value that can be achieved in a 6-8 week timeframe.
INTEGRATION AND INFRASTRUCTURE SPRINTS //
Integration and Infrastructure Sprints are also of a limited duration. Each sprint addresses a subset of the integration requirements or infrastructure. As in the functional sprints, each sprint has a contained set of deliverables that include: discovery, definition of success criteria, recommended processes, implementation, testing, and documentation.
Integration sprints will align with the functional sprints to enable use of the Q functionality delivered in the sprints. Addressing integration aspects early-on speeds implementation time. However, wherever possible, integration sprints and functional sprints are kept as independent as possible. The goal is for integration never to impede the functional delivery (though of course the final production usage will depend upon integration). Early sprints may use integration that is manually triggered and/or loaded.
FEEDBACK SPRINTS //
Feedback sprints take the functional sprints and apply them to the customer’s business. Tasks in the feedback sprint include: training, tracking of ROI/success criteria, user assessment, finalizing the to-be-business process, and identification of any additional configurations or modifications necessary to support the business.
The Q Feedback Sprints are typically comprised of 4-6 weeks of effort and are run directly after the applicable solution sprint. Integration, functional, and feedback sprints run concurrently. Typically only one sprint of each type is run at any given time, but they can overlap somewhat if required.
