Glossary

Term / Context / Description /
agile / agile / Agile is a flexible iterative approach often used when developing IT products.
Alpha / Accelerate / The phase of Accelerate when the product is developed.
architecture owner / Accelerate / The role responsible for facilitating the development of the architecture (structure) of the solution. In agile, this is done collaboratively with the development team. This role is discussed in detail in the Accelerate framework, under Key terms used in Accelerate.
Beta / Accelerate / The phase of Accelerate when the product is released.
burn down chart / agile
scrum / A chart showing the remaining sprint tasks, updated daily during a sprint.
business architect / See enterprise architect
customer / A person who uses the product or service. This can be a member of the public, or a staff member (including staff members using processes to assist members of the public). This term is interchangeable with ‘user’.
definition of done / agile / The criteria that define when a user story (task), sprint, or release has been completed.
definition of ready / agile / The criteria that define when a user story (task) is ready to be included in a sprint, or when a sprint, or release is ready to start.
Discover / Accelerate / The phase of Accelerate when information is gathered so that the business case for proceeding to the rest of the project can be presented.
enterprise architect / The role responsible for developing and maintaining the IT capabilities of an organisation to support its strategic objectives.
Grow / Accelerate / The phase of Accelerate after the product has been released, when the product’s capability is reviewed and may be extended.
Live / Accelerate / The phase of Accelerate after the product has been released, when the product’s capacity may be extended.
minimum viable product (MVP) / agile / A portion of the product’s desired features that is able to be deployed and has value to the customer.
In Accelerate the MVP is likely to be refined and extended in further development iterations (that is, in Live and Grow).
MVP / agile / See minimum viable product.
Prepare / Accelerate / The phase of Accelerate when information is gathered so that the business case for proceeding to Discover can be presented.
product backlog / agile / The list of user stories (discrete tasks) that will be carried out to complete the product release.
product owner / agile / The role responsible for maintaining the product backlog, representing the interests of the stakeholders and customers, and ensuring the value of the work the of the development team.
Project Board / PRINCE2 / The group that provides governance through direction and management.
The Project Board is responsible for the overall direction and management of the project and should have the authority to direct the project within the remit set by the Department or programme.
project manager / PRINCE2 / The role responsible for day-to-day management of the project.
The project manager reports directly to the sponsor, and is not part of the Project Board.
The project manager’s responsibilities include:
·  directing the project team
·  managing the project plan
·  maintain the risk register, issue, and change control logs
·  reporting on progress to the sponsor and other stakeholders.
scrum / agile
scrum / An agile development model that uses a series of iterations (sprints) to develop a product.
scrum master / agile
scrum / The role responsible for ensuring the scrum process is followed effectively.
scrum team / agile
scrum / The product owner, the scrum master and the development team.
sponsor / PRINCE2 / Also known as the senior responsible officer, or executive.
The person ultimately responsible for the success or failure of the project. They:
·  are a member of the Project Board, and appoint the other members
·  secure budgets and ensure appropriate financial controls are in place
·  advocate for, and support the project
·  sign off on project deliverables.
sprint / agile
scrum / A block of work done by a team over a set time period (usually 1-4 weeks), on tasks moved from the product backlog into the sprint backlog.
sprint backlog / agile
scrum / The list of user stories that will be worked on by the team in a particular sprint.
stakeholders / Individuals or groups that are likely to affect, or be affected by, the project.
user / See ‘customer’.
user story / A clear expression of a product requirement that:
·  is written from the perspective of the customer
·  can be coded and delivered within a sprint.
velocity / agile
scrum / The total effort a specific team is capable of in a sprint, based on the work completed during previous sprints.

Page 2 of 2