This is a general template for TAC and UAC workplans. Use this as a starting point for your sub-team, but feel free to depart from the format as your work needs. More general guidance on considerations regarding workplans can be found at https://archivesspace.atlassian.net/wiki/spaces/AC/pages/3137994933/Guidelines+for+ArchivesSpace+Council+Sub-Teams#Sub-team-Workplans
...
Table of Contents |
---|
...
Goals
Use this section to identify your sub-team’s overarching goals for the term. These may be restatements of your sub-team’s charge.
...
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
- Ongoing task 1
- Ongoing task 2
- Example: Monitor documentation GitHub repository and promptly address issues and pull requests. Point person is [name, using @ functionality]
- Example: Perform regression testing for upcoming releases.
In-Progress Projects Carried Over from Last Term
- Example: Revisit [document link] an update with current processes. Delegated to [name, using @ functionality], slated to be completed by .
New Projects for This Term
- New task/project idea, including basic descriptionExample: Revise documentation about [x] functionality based on conversation on User listserv.
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.
...