This is where we get into the "nitty-gritty" and cover the detailed steps of scoping, building, testing and deploying a K2 solution. Information includes planning and resourcing documentation, required skillsets, existing line-of-business application integration and other critical business considerations that are required to deliver a completed solution.

Initial Discovery

This phase focuses on understanding the high level goals, needs and timelines for the potential project. This is typically a one-to-four hour meeting in which the key stakeholders of the solution, such as business subject matter experts (SMEs), technical leads and/or project manager(s) have a discovery conversation with the leads from the potential implementation team (referred to as business architect and technical architect).

Solution Analysis and Planning

The solution analysis and planning phase is the entry point into solution functional scoping and project planning. The goals of this phase are to identify project critical success factors, as well as discover initial functional scope/business requirements and technical drivers and integrations. This phase is typically lead by the business architect and the technical architects leveraged during the initial discovery phase.

Elaboration and Design

The elaboration and design phase expands upon the previous phases by delving deeper into identifying and documenting the business and technical requirements. The goal of the phase is to derive a target solution architecture, technical design and implementation plan. This phase has a typical duration of two-to-six weeks depending on the size of the project.


Milestones are best implemented by following a build, test and review cycle. This section goes into detail on who should be involved and best practices to follow.

Roll Out

The roll out phase occurs when a version is deployed to the production environment and becomes operational within the business unit. Learn how to coordinate a roll out across multiple stakeholder groups.