Build

This document will outline the best practice methodology for delivering K2 solutions. This can be followed on its own, or adapted to fit within an existing development methodology that may already be present within an organization. This featured methodology encompasses the full life cycle of a project, from initial consideration through design, development, testing and ultimately deployment and operations as shown below:

Each stage of the K2 Build methodology has defined goals and outcomes. Below provides a summary of each phase. The following sections of this document will provide details for each phase.

INITIAL DISCOVERY ANALYSIS & DESIGN IMPLMENTATION ROLLOUT
Solution Analysis and Planning Elaboration and Design Build Test Review
Goals Discuss project at a high level. Assess initial fit and needs. Determine amount of time needed for the next phase. Perform business review and process discovery to understand functional requirements. Execute technical discovery and develop initial solution vision and project estimate. Work to solidify functional and technical requirements via discovery workshops and rapid prototyping of concepts. Once requirements are signed off, detailed estimate and project plan (where applicable) are created. Develop artifacts for given milestone scope and perform developer/unit testing and integration testing. Execute QA/UAT testing and prepare against given milestone. Analyse testing feedback and determine impacts and priority of bugs and enhancement requests. Release version to production and prepare for operational phase by communicating solution components with operations team.
Potential Duration Hours Hours / Days / Weeks Hours / Days / Weeks Days / Weeks (per milestone) Days / Weeks (per milestone) Hours (per milestone) Hours (per version)
Key Outcome(s) Assess project fit

Determine timing and duration of Solution Analysis and Planning phase
Initial scope and solution vision

Initial Project Estimate

Determine timing and duration of Elaboration and Design phase
Functional Design

Technical Design

Detailed Project Estimate

Project Plan for Build, Test and Deploy phases
Test Plan

Deployment Artifacts

Support Plan

User Training

Solution Knowledge Transfer
Test Results

Testing issues list that details and severity
Milestone Go/No Go

If required: impacts of requested changes
Deployed solution

Project Debrief

Asset Inventory
Supporting Content Initial Discovery Assessment

Process Viability Assessment
Process Discovery Questionnaire
Initial Project Estimate spreadsheet Functional Design

Technical Design

Detailed Project Estimate

Project Plan for Build, Test and Deploy phases
Source Control Guidance

K2 Solution Design and Implementation Best Practices

Test Cases

Demo notes

Sign-offs
Application Deployment Guide

Application Checklist
INITIAL DISCOVERY
Goals Discuss project at a high level. Assess initial fit and needs. Determine amount of time needed for the next phase.
Potential Duration Hours
Key Outcome(s) Assess project fit

Determine timing and duration of Solution Analysis and Planning phase
Supporting Content Initial Discovery Assessment

Process Viability Assessment
Process Discovery Questionnaire
ANALYSIS & DESIGN
Solution Analysis and Planning
Goals Perform business review and process discovery to understand functional requirements. Execute technical discovery and develop initial solution vision and project estimate.
Potential Duration Hours / Days / Weeks
Key Outcome(s) Initial scope and solution vision

Initial Project Estimate

Determine timing and duration of Elaboration and Design phase
Supporting Content Initial Project Estimate spreadsheet
ANALYSIS & DESIGN
Elaboration and Design
Goals Work to solidify functional and technical requirements via discovery workshops and rapid prototyping of concepts. Once requirements are signed off, detailed estimate and project plan (where applicable) are created.
Potential Duration Hours / Days / Weeks
Key Outcome(s) Functional Design

Technical Design

Detailed Project Estimate

Project Plan for Build, Test and Deploy phases
Supporting Content Functional Design

Technical Design

Detailed Project Estimate

Project Plan for Build, Test and Deploy phases
IMPLMENTATION
Build
Goals Develop artifacts for given milestone scope and perform developer/unit testing and integration testing.
Potential Duration Days / Weeks (per milestone)
Key Outcome(s) Test Plan

Deployment Artifacts

Support Plan

User Training

Solution Knowledge Transfer
Supporting Content Source Control Guidance

K2 Solution Design and Implementation Best Practices

Test Cases

Demo notes

Sign-offs
IMPLMENTATION
Test
Goals Execute QA/UAT testing and prepare against given milestone.
Potential Duration Days / Weeks (per milestone)
Key Outcome(s) Test Results

Testing issues list that details and severity
Supporting Content
IMPLMENTATION
Review
Goals Analyse testing feedback and determine impacts and priority of bugs and enhancement requests.
Potential Duration Hours (per milestone)
Key Outcome(s) Milestone Go/No Go

If required: impacts of requested changes
Supporting Content
ROLLOUT
Goals Release version to production and prepare for operational phase by communicating solution components with operations team.
Potential Duration Hours (per version)
Key Outcome(s) Deployed solution

Project Debrief

Asset Inventory
Supporting Content Application Deployment Guide

Application Checklist

Initial Discovery

This phase focuses on understanding the high-level goals, needs and timelines for the potential project. This is typically less than a couple of hours of conversation where the key stakeholders of the solution, such as business subject matter experts (SME), technical leads and project manager have a 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 to discover initial functional scope, business requirements, technical drivers and integrations. This phase is typically lead by the Business Architect and the Technical Architect leveraged during the Initial Discovery phase. Once the functional and technical factors are determined, a high-level solution vision and reference architecture can be formulated to articulate how the key components of the proposed solution can be aligned and leveraged to achieve the functional requirements. Additionally, initial infrastructure planning can be formulated to support the project needs. With this reference architecture in place, initial estimates can be formulated and work breakdown structures generated to allow for initial project costing; allowing for more detailed budgeting and planning discussions.

Elaboration and Design

Upon completion of the SA&P phase there should be a foundational understanding of the goals, scope and vision of the proposed solution. The Elaboration and Design phase expands the prior work by delving deeper into identifying and documenting the business and technical requirements in order to drive to derive at a target solution architecture, technical design and implementation plan. This phase can be of a short duration depending on the size of the project.

Implementation

The below Build, Test and Review cycles fall within a given milestone. This section goes into detail on who should be involved and best practices to follow.

Roll Out

The rollout phase is when a version is deployed to the Production environment and becomes operational within the business unit. This requires planning and coordination across multiple units.