Project settings overview

Powerful signals for automating your Delta test come from Project and Product Details

This article applies to Pro, Team, and Legacy editions.

Upon creation, projects in Centercode capture a range of testing, product, and participant details. These details:

Influence the Tester Engagement Director’s (Ted) messaging behavior
Inform the recommended number of testers to fit your testing needs
Are available in the Centercode Data Engine for high-level reporting across projects

These settings and details can be updated anytime after the project is created within the Basic Project Settings.

Project details impact high-level settings within a project, including Ted's settings, as outlined below.

Program: The program in which your project will be created
Project codename: What you want your project to be known as
Project type: The category of test you’re running
- Continuous Perpetual ongoing iterative
- Time-boxed A fixed duration with a beginning and an end
Exposure: Influences Ted's messaging and project messaging depending on your selection.
- Open Information is not intended to be kept confidential and allows Ted to mention to testers that your test is open and can be shared and discussed with others
- Private All information is intended to be kept confidential
Project style: Allows you to pick a color and icon to associate with your project (The icon that will be seen next to the project in the community home)
Visual theme: The Visual theme of your project controlling logos and colors (only visible if you have more than one visual theme available)
String set: The text throughout your project is determined by the selected string set which allows for localization or colloquialization (only visible if you have more than one project string set available)
Dashboard time zone: The time zone for the project which influences when automated communications are sent and when your scheduled test planning features and phases are launched
Project reply-to address: The email used when sending emails to participants
Project key: The globally unique identifier used in API endpoints to identify this project

Product details provide the project with key information about your product, allowing Ted to adjust its behavior for optimal participant engagement.

Product name: The product you’re testing
Product type: The categorization of your product
Product market: The target market for your product, signaling to Ted and other automation when to send tester communications (before 9am, after 5pm, weekdays only, etc.)
Product price: An estimation of your product's cost to your target market
Brand impact: How the value of the results of the test is relative to your brand
Product files : Allows you to upload relevent product files (such as manuals, specs, PRDs, etc), that can be used when generating resources via Ted AI (test plans, surveys, etc)

Participant details provide the project with key information about your testers.

Audience profile: The general persona of your target market (and therefore participants)
Identify by: How testers will be identified within your project to other users
Target number of testers: Your goal number of engaged testers based on required results or test planning (consider recruiting more participants than your goal number since 100% participation is unlikely)

Selecting a Visual theme other than the default community theme will use the logo associated with that theme in place of your project codename in the upper left menu.
Ted uses the Project codename in his automated emails to testers and admins.