Next Phase Prescriptive Customer Projects

Below is described what the methodology is for 'next phase customer projects'. With next phase we mean all phases after the initial implementation. As there can be a wide variety of types of next phase projects, the assumption here is that:

• The DEV/QA/Prod systems are in place

• The team on the customer side is the same team as the previous project phase

• All needed data is already there

• The project refines existing functionality and might add additional functionality on top of what is already implemented

Main differences in terms of implementation will be:

• No (or much shorter) project initiation sprint needed, as the systems are in place and the customer's team is intact

• No setup sprint needed as all data is already there

• Shorter foundation sprint

• Shorter go-live sprint

• More focus on regression testing during the sprints and UAT

There can be different project characteristics that you might end up with a mixed approach in terms of our methodology - mixed in the meaning of a blend between phases of the initial implementation methodology and the phases described below. This could be the case when:

• Rollout to different regions for which the data is not in the system yet

• Implementing different modules with different data needs that are not in the system yet

• A very different customer team, because of a different functionalities, geographical / business regions, or a large time gap with the previous implementation

Here are the phases:

• Optional: Project Initiation

• Foundation Sprint

• Preparation sprint

• Feature Sprints

• Hardening & SIT

• Optional: Performance sprint

• UAT sprint

• Deployment

• Stabilization sprint

Open