A mouthful of agile management terms and jargonApril 28, 2021
Sign up and try it out for free!Sign Up For Free
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 charts and burnup charts track the amount of output / productivity completed across an sprint or a project.
Collective code ownership means every developer on the project has equal access to update product code.
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.
When each successive version of a product is usable, building on to the previous product version releases.
“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.
A Kanban Board is a paper-based visual workflow consisting of tasks organized by To Do’s, In Progress, Done.
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.
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 consists of two programmers sharing a single workstation, switching off in turns, to improve the quality of the product and reduce bugs.
Personas are bios, character sketches, and stories of fictitious users of a product.
A product backlog is a prioritized list of the new features, feature updates, bug fixes, and other support activities that a team may execute.
The product owner exists within the Scrum Framework – responsible for the team delivering their intended outcome.
Refactoring consists of improving the internal structure of an existing program’s source code, while preserving its external behaviour.
Regular meetings to reflect on project events that occurred since the last meeting.
Scrum is an agile framework used to manage product development.
The scrum master ensures the team applies agile values, principles, and follows the practices that the team agreed to operate under.
Planned features and tasks that are prioritized for completion within a sprint.
Sprint planning happens at the beginning of a sprint where the team determines the product backlog for that particular sprint.
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.
Often used by Scrum Masters, a timebox is an agreed duration that a team works to complete a set goal.
Testing a particular area of the product’s source code.
The sum of productivity required for the completion of tasks in the Spring backlog.
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.