Basic Agile and Scrum

Product Owner

The person who represents the customer for the thing you're developing

Sprint

A time box of one month or less during while a finished, useable and potentially releasable product increment is created

User Stories

Short simple description of a feature told from the perspective of a person who desires the new capability

e.g. an epic: As a user I can backup my entire hard drive

or more detailed: As a power user I can specify files or folders to backup based on file size, date created and date modified

Each story can be split into multiple smaller stories

Acceptance Criteria

Defines the boundaries of a user story, used to confirm when a story is completed

Examples: A user cannot submit a form without completing all the mandatory fields Information from the form is stored in the registrations database Protection against spam is working. Users can pay by credit card.

Task ——- Single piece of work associated with s story, usually carried out by one person

Artifacts

Product backlog - All baseline requirements prioritized in order

Sprint backlog - Subset of the product backlog that the team pulls into the sprint to work on This is the list of To Dos a dev team has during the current sprint

Product Increment - Each sprint produces a potentially shippable product increment, must align to the dev teams "definition of done"

Definition of Done - A shared understanding document of the dev team regarding what 'done' means