Architect & Prototype

This package creates the solution's architecture and uses prototyping to validate that the design meets the technical requirements while delivering the desired business outcomes.

System Architecture Business Process Map Design Validation Test Strategy

System Architecture

Establish agreement among all parties involved in the design and architecture of the system(s) to support the requirements.

Deliverable

Solution Design Document

Ideal Format & Timing

Design and architecture sessions
2-3 weeks total

Key Activities

Define the objects—including custom objects—within the systems and their use based on the requirements
Create an end-to-end architecture diagram of the solution with integration points and data flows

Benefits

A Solution Design Document serves as a base moving forward
Clear understanding of system architecture and integration points
Alignment among all parties on technical design

Business Process Map

Create an overview map of the key processes needed to support the Solution Design, including the identification of those processes that will be updated and changed.

Deliverable

Process Design Document

Ideal Format & Timing

Process mapping and analysis sessions
2-3 weeks total

Key Activities

Understand the key processes required to support the solution design
Identify changes in existing processes, new processes, and processes that remain unchanged

Benefits

Ensures that process changes are facilitated during the implementation to be ready for a successful go-live
Ensures the solution design is supportable by the business in the long term

Design Validation

Complete prototyping within the systems of the Solution Design to ensure accuracy and test validity.

Deliverable

Validated Solution Design Document

Ideal Format & Timing

Prototyping and validation sessions
2-3 weeks total

Key Activities

Take the Solution Design and build out prototypes in the system to validate it
Adjust and iterate on the Solution Design as needed

Benefits

Up-front validation minimizes significant delays or re-work later in the process
Provides the customer with early visibility and exposure to the system
Diagnoses needs or requirements that may have been overlooked earlier in the process

Test Strategy

Develop a testing strategy for User Acceptance Testing at the end of the implementation to ensure satisfaction of business requirements and identify test scenarios and data that will need to be created.

Deliverable

User Acceptance Testing (UAT) Plan

Ideal Format & Timing

Testing strategy development
2-3 weeks total

Key Activities

Understand what testing scenarios are needed to validate that the system is configured correctly
Identify billing models, tasks, and other use cases that should be tested in the solution
Define the data and information needed to compile use cases for testing

Benefits

Ensures thorough testing of the system's ability to satisfy requirements
Helps the customer meet the challenge of creating quality use cases
Reduces risk of post-implementation issues

Uncover & Align

Build & Test

Value Management

The solution to tech-project regret

Companies across all industries struggle to successfully implement the software they've purchased, resulting in unrealized value, frustration, and regret. Regret often occurs when problems are misdiagnosed as a symptom or not fully known or understood. Focusing on business-value outcomes helps ensure the real problems are solved.

Get Started with Value Management