Part 3: Testing, POCs, Pilots & Rollouts

Last update: Mon May 13 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

Topics:
Overview

CREATED FOR:

Beginner
User
Developer

This page highlights part 3 of a 5-part series designed to help team members better understand the key terms critical in ensuring a successful solution can be developed before a rollout.

Overview

This tutorial covers the following points relevant to a successful deployment of a project plan:

Identify areas often underestimated as part of the overall project plan, including:
Actions surrounding Hardware Lab Testing & Performance Validation
Systems & Software Integration Testing
Proofs of Concept (also called POCs) and Pilot programs
End-to-End Testing

NOTE

Typical Sales cycles for Digital Signage deployment at scale can range from 9 through 18 months. There are many factors involved that affect the final time line. Some of these factors include how the end-client measures success and how risk averse their business partners are when a new solution is introduced.

For example, stakeholders for a digital signage program in a retail environment could include the following:

In-Store Marketing
Store Environment or Visual Merchandising
Store Operations
IT Security
IT Support
The product category Merchant and their supplier, who may be co-funding the solution.

Summary of Key Terms involved in an Overall Project Plan

The following section provides an overview on the key terms involved in an overall project plan, Key terms include project cycle, actions surrounding hardware testing, Proof Of Concept, pilots, and roll outs.

Proof of Concept (POC)

The purpose of a POC is to gain initial feedback on a solution’s key functionalities. It also lets both the end-client and Audio-Video Integrator an opportunity to identify areas for improvement and prepare assumptions surrounding labor requirements and resource demands. A POC also lets both parties assess the solution’s performance, which is typically measured through:

Quality Control

Systems and Software Integration testing begins with the Audio-Video Integrators IT Engineering team. Referencing the approved system design, the IT Engineering team configures, implements, and supervises the installation of hardware components in a “Lab environment” in the Audio-Video Integrator’s facility. This arrangement allows for close review and testing of the entire solution for quality control.

After QC testing is complete, the IT Engineering team creates documentation, workflows, and training for reference during Day-2 support. Systems aspects to test include the following:

AEM implementor integrations.
Third-party systems integrations.
Software.
Hardware.
Connectivity.
Content Deployment workflows including manual, automated and conditional deployments.

Part 3: Video Tutorial on Testing, POCs, Pilots & Rollouts

Follow the tutorial below to understand testing, proofs of concept, pilot programs, and rollouts.

Considering all these stages as part of the overall project plan helps manage expectations and identifies natural points in which the investment in an AEM Screens deployment can be evaluated.

Testing, POCs, Pilots & Rollouts

https://video.tv.adobe.com/v/28405

Learn the key terms involved in an overall project plan such as project cycle, actions surrounding hardware testing, Proof Of Concept, pilots and rollouts.

The Next Step

When you are through with testing, Proofs of Concept, pilot programs, and roll outs, follow the next tutorial that dives deep into Project Management and the processes involved.

Navigate to Part 4: Project Management and Deployment for more details.

recommendation-more-help