Glossary

Epic

An epic acts as a parent container for multiple child user stories that span multiple releases and sprints in a product. You can link epics to requirements to provide traceability and to help with the planning process.

Product

Something of value produced by your company for sale or internal company use. A product can be merchandise or wares, software, a building project, or any other consumable. Products also represent services, applications, or systems in an IT environment.

Product Backlog

The list of current and upcoming user stories and associated issues for a product. A scrum team uses the backlog to determine what items they work on for a release or sprint.

Product Owner

The scrum team member listed as the product owner in the properties of a product.

The product owner has privileges over all objects that are associated with the product, such a requirements, releases, sprints, and backlog items. The product owner does not need to be a scrum team member to work with user stories associated with the product.

Release

A release is similar to a project, an effort that ends with the delivery of value. The release usually entails a number of features and requirements.

Requirement

A requirement is a documented specification that describes what a particular product or service can be or do. A statement that defines a necessary attribute, capability, characteristic, or quality of a product or service so that it provides value to a user.

Scrum Master

The scrum team member responsible for the daily tracking, problem solving, and tasks associated with managing a release. The scrum master needs to be knowledgeable about scrum and agile methodologies and procedures.

The scrum master generally moderates all planning, daily-stand up, and retrospective meetings.

Scrum Team

The group of people assigned to work on a release and sprints for a product. The team has the following roles: product owner, scrum master, and team member.

Sprint Backlog

The list of user stories and issues to which the scrum team has committed for a sprint.

Task Worklog

A log that a scrum member creates for a task that records how much time the member worked on the task.

Team Member

A member of the scrum team that works on user stories. A scrum team consists of a cross-functional group of members, including the following skills:

• Software development
• Quality assurance
• User interface or product design
• Technical documentation development

Theme

A container for user stories that groups them under a common purpose, such as user interface changes. Themes are useful because they can span releases and a user story can belong to more than one theme.

User Story

A user story is a way to define requirements in CA Agile Vision. If these products are used together, a requirement in CA Product Vision can be linked to its associated user story in CA Agile Vision.