Execution phase

Kinetic Data follows a version of the Incremental Process Model (also known as a Successive Version Model) during the Execution Phase. This model involves creating a functional system by focusing on only a few essential features in a two-week period — known as a "sprint." The resulting work from the sprint is then demoed or delivered to the customer. Subsequently, multiple iterations or versions of the system are developed and delivered to the customer until the final product meets their requirements and is ready for release.

The first sprint (marked as "A" in the above image) should focus on establishing a repeatable approach that both the project team and client can follow. Once the initial sprint has been completed, iterations should be identified and broken down into manageable tasks to produce tangible outcomes (“B,” “C,” and beyond).

This approach offers several benefits, including:

• Faster development: By breaking the project into smaller, achievable tasks, the team can deliver quicker.

• Clear project vision: By involving the client in the initial sprint, they gain a clear idea of the project and can provide feedback on the team's approach.

• Easy implementation of changes: The successive version model allows changes to be easily incorporated into the project during subsequent sprints.

• Risk management support: The iterative approach of the successive version model provides risk handling support by allowing for continuous evaluation and adjustment throughout the project.