Table of Contents

6. Alpha - Wrike Task Definitions

Jason Carroll Updated by Jason Carroll

This article contains definitions and essential info pertaining to all of the tasks in the "Alpha" milestone/bucket in the Wrike course development blueprint. If you notice anything out of date or missing here, please use the "Send Feedback" button in the lower right of this page to report it.

1. Prepare/Conduct Alpha

Basic Task Description

This task covers the full run of the Alpha test, from the kickoff meeting (for Course 1) through the end. The ID should confirm that all the testers and the facilitator are set up and ready.

Workflow Guidelines

  1. Schedule kickoff on the Monday before the Alpha begins (usually on a Wed.)
  2. Make sure all testers have access
  3. Set to In Progress
  4. Set to Done when the Alpha is complete

Who to Tag if You Need More Info

Jason Carroll

Who Defines Dates?

IDD

Common Mistakes/Confusion

  • Make sure the Tech QA is complete
  • The kickoff meeting usually needs to happen only before the Alpha for Course 1 of a cert

See this doc for more information on the process

2. Schedule & Conduct Alpha Triage Meeting

This is an optional task and depends on consultation between tech lead, alpha coordinator, and ID.

Basic Task Description

Scheduled by the ID & Tech Lead; invite:

  • IDA
  • Alpha Facilitator
  • Product Owner
  • Faculty Author (if involved at that level)

Workflow Guidelines

Single meeting: set to To Do when scheduled; set to Done when complete

Who to Tag if You Need More Info

Ted Blanchard

Who Defines Dates?

ID

Common Mistakes/Confusion

This task is optional, and can sometimes be replaced by an asynchronous BugHerd review by the ID/IDA in consultation with the Tech Lead

3. Implement/Verify Alpha Changes to Master

Basic Task Description

This is task shared by the Tech Developer (and/or Tech Lead) and the Tech Reviewer QA: the former Implements the changes, and the latter Verifies them

Workflow Guidelines

  1. Task set to To Do when/while  the BH bugs are being reviewed and categorized
  2. Set to In Progress while the TD/TR and Implementing
  3. Set to Ready for Review (and assigned to the Tech QA) when Implementation is finished
  4. Set to Done (by Tech QA) when the Verification is finished

Who to Tag if You Need More Info

Ted Blanchard

Who Defines Dates?

ID

Common Mistakes/Confusion

The Implementation phase of this task often involves consultation/collaboration with the ID and the Faculty Author, to confirm (or reject) changes.

3. Update/Revise Facilitator Notes

Basic Task Description

This task is managed by the ID, but performed largely by the Alpha Facilitator, based on his/her experience facilitating the course Alpha test.

Workflow Guidelines

  1. Set task to To Do when the Alpha is finished
  2. Set to In Progress while working
  3. Set to Done when complete

Who to Tag if You Need More Info

Dylan McNally

Who Defines Dates?

ID

Common Mistakes/Confusion

The Facilitator Notes/Facilitation Guide process can vary by project, and this will result in a change in what actually needs to be updated. See this doc for more info.

How did we do?

Alpha Review Process

Contact