User:Fæ/GLAM job ticket

Description

This template creates a structured layout for a job ticket supporting GLAM initiatives. Such tickets are for crowd-sourcing activities such as:

non-content technical effort such as special bot-script creation or collaboration tools
research or data gathering (such as coordinating a survey)
logistical, communication and managerial support for events
supporting significant external requests for help or partnership

GLAM initiatives are intended to apply at an international level. National activities will require liaison with the local chapter.

Usage

{{User:Fæ/GLAM job ticket
 | parent =
 | title =
 | id =
 | deliverables =
 | resources =
 | constraints =
 | people =
 | acceptance =
 | estimate =
 | result =
}}

Example default layout

Parent project GLAM general

Title ? ID ?

Plan

Deliverables

< Please specify the expected outcomes of the job >

Resources

< List the resources needed to deliver this job, for example software licenses, equipment on loan, room hire >

Budget

< If any costs are expected to be incurred please provide a breakdown of budget required. The budget should be signed off here by a chapter board director before the start of any activity and linked to any micro-grant discussion >

Volunteer effort

< Specify the total effort that might be needed from volunteers. If this is more than 80 hours, consider breaking the ticket into smaller tickets >

Constraints

< Identify the minimum possible constraints for this job. This may include location, skills and experience needed and delivery dates >

Acceptance criteria

< For each of the deliverables listed above, specify the acceptance criteria. These might be documented activities such as functional tests, peer review, user feedback >

Do

People delivering

Please volunteer and sign up here! If a collaboration page is not already identified please link to where your progress can be viewed.

Progress and coordination

Check

Acceptance results

< Results, interwiki links, comments and feedback from acceptance stage >

Act

Deployment and lessons learned