A mouthful of agile management terms and jargon

April 28, 2021

Sign up and try it out for free!

Sign Up For Free
Agile Management terms

Getting into project management can be a mouthful of new terms and phrases. Are you relatively new to working under an Agile Framework for project management? We’ve put together a short list of some of the agile management terms used in agile to help you “fake it ’til you make it“….enjoy.

Backlog Grooming / Backlog Refinement
When the product owner and team regularly review the backlog for tasks that are dated or unnecessary.

Burndown Chart
Burndown charts and burnup charts track the amount of output / productivity completed across an sprint or a project.

Collective Ownership
Collective code ownership means every developer on the project has equal access to update product code.

Epic
A large, long-winded user story.

Given When Then
Given-When-Then is a formula or preferable question format for user stories that include (Given) scenario context, (When) some an action or event occurred, (Then) observable consequences / outcomes in result of the action.

Incremental Development
When each successive version of a product is usable, building on to the previous product version releases.

Information Radiators
“Information radiator” can be in the form of physical items, signs, tickers, or a dashboard displaying current project data somewhere that all team members can view it regularly.

Kanban Board
A Kanban Board is a paper-based visual workflow consisting of tasks organized by To Do’s, In Progress, Done.

Milestone Retrospective
A team’s detailed analysis of the project’s significant events after a set period of time or at the project’s end.

Minimum Viable Product (MVP)
The initial version of the product which allows Product Owners to test its use and validity.

Mob Programming
A software development approach where an entire team works on the same thing, at the same time, in the same space, and at the same computer.

Pair Programming
Pair programming consists of two programmers sharing a single workstation, switching off in turns, to improve the quality of the product and reduce bugs.

Personas
Personas are bios, character sketches, and stories of fictitious users of a product.

Product Backlog
A product backlog is a prioritized list of the new features, feature updates, bug fixes, and other support activities that a team may execute.

Product Owner
The product owner exists within the Scrum Framework – responsible for the team delivering their intended outcome.

Refactoring
Refactoring consists of improving the internal structure of an existing program’s source code, while preserving its external behaviour.

Retrospective
Regular meetings to reflect on project events that occurred since the last meeting.

Scrum
Scrum is an agile framework used to manage product development.

Scrum Master
The scrum master ensures the team applies agile values, principles, and follows the practices that the team agreed to operate under.

Sprint Backlog
Planned features and tasks that are prioritized for completion within a sprint.

Sprint Planning
Sprint planning happens at the beginning of a sprint where the team determines the product backlog for that particular sprint.

Story Mapping
Ordering user stories along two independent dimensions.

Test Driven Development (TDD)
A programming style in which three activities are tightly interwoven: coding, testing, and refactoring.

Timebox
Often used by Scrum Masters, a timebox is an agreed duration that a team works to complete a set goal.

Unit Testing
Testing a particular area of the product’s source code.

Velocity
The sum of productivity required for the completion of tasks in the Spring backlog.

Version Control
Version control is a widespread industry practice used by development teams to keep track of updates and changes made to a product’s code base.