Agile

Rerquirements, Epics, stories, tasks and tests

Requirements

Everything we need to do

Written in general customer language 

Non-technical

Gathered from customers and can change

Stories

Generally translations of requirements

"As a [role] I want [feature] so that [benefit]"

Specific and actionable

Epics

A group of stories

Usually born out of more general requirements

Needs to be drilled down into stories

Not necessarily always part of a projects

Sometimes convenient to group stories this way

Tasks

Actual development work

Subordinate to Stories

Not the concern of the client or typically the PM

Backlog

A list stories yet to be done

Epics can be in here too

Stories are listed by importance and dependency

Backlog grooming is the process of reordering or inserting new requirements

Tests

Verification that a story is complete

Tests are a composite of the acceptance requirements for a story

The exact format of stories is used in testing

In the form of unit, manual and automated testing

Tools

Jira

Jira Agile

Testing Tool (yet to be named)

Overhead

Learning the lingo

Using the tools

Keeping the faith