Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Goals

The testing team will perform regression testing for any releases as they become available and will test specific JIRA issues as assigned.

Specific Tasks or Projects

Use this section to identify the specific tasks or projects your sub-team intends to work on this year. Consider organizing them into ongoing and discrete tasks, if appropriate.

The sub-sections below provide a suggested structure: Ongoing/Recurring Tasks, In Progress Projects Carried Over from Last Term, New Projects for This Term, and Out-of-Scope. Feel free to depart from this as appropriate for your sub-team’s work.

A few considerations:

  • Consider adding details like timelines, names of sub-team members who the task is delegated to, and links to helpful documentation.

  • Be realistic about your sub-team’s capacity – small, achievable goals are important!

  • Identify if any of these projects are “stretch” goals that may not be feasible or will remain in-progress at the end of term.

  • Using the checkbox functionality allows you to easily indicate when work is completed.

Ongoing/Recurring Tasks

  • Assign Testing tasks across the team (regression and JIRA) as they are. Point person is Austin Munsell
  • Perform regression testing for upcoming releases.
  • Test specific JIRA issues as assigned
  • New members will be onboarded with guided testing for the first JIRA assignments and first full regression tests

In-Progress Projects Carried Over from Last Term

New Projects for This Term

Out-of-Scope (Optional)

Identify any work areas of projects that you have determined to be out-of-scope of this year’s workplan. This could be because it falls beyond your sub-team’s charge, has a dependency that requires you to wait, or is beyond your sub-team’s capacity.

Maintenance Activities (Optional)

Use this space to identify any actions or considerations necessary to support the maintenance of your sub-team’s tasks or projects once they have been completed. Is there documentation that needs to be created? Do future sub-team members need particular permissions to complete certain work?

  • Update access to Testing Google Drive

Themes (Optional)

This section is optional, but a space to identify any underlying themes that run throughout multiple tasks or projects. This can also be a space to identify how you intend to approach your work this term. This can also be helpful when revisiting the workplan at the end of term with an eye towards the sub-team’s retrospective, or at the beginning of next term.

  • No labels