This workflow goal is to perform the first investigations about the customizations to be implemented. The customer is involved in the early definitions of the requirements needed. The initial requirements analysis is performed during this workflow. If necessary, it should be tested the feasibility of using the technology and infra structure that is intended be used in the project. Initial requirements should be written and it is important to collect information necessary to analize the gap between client expectations and product standard features. This GAP Analysis intends to map the differences between customer requirements and the current product being offered. A high level definition document should be produced to be reviewed and approved by the customer.

This workflow goal is to define and prioritize the set of features that will be the input for the iteration planning. The list of features produced in the initial requirements analysis is reviewed and prioritized. It allows stakeholders to identify the most important requirements that will be analized and developed in the following iteration cycle. The analysis of the set of features previously defined should be used to write the stories with enough detail to perform the iteration planning. In this case, the stories are written by the Deployment Manager or Engineering Leader that will always be in contact with the customer. The output of this workflow is the Change Definition Document (CDD) containing the stories that describers the changes to be performed.

In this workflow, the environment is setup for the product deployment based on previous planning. The approach defined should be reviewed so the infra structure of servers, network, and other components required is arranged. In addition to this, it should be set up the infra structure needed by the engineering team in order to implement customizations and integrations.