Glossary

If you’re new to the agile world, I hope you’ll find the following helpful:

  • Backlog – Usually refers to the Product Backlog, but might refer to the Sprint Backlog
  • Big Visible Chart / BVC – a certain kind of Information Radiator
  • Daily Scrum / Daily StandUp – Daily Meeting for a (scrum) team to synchronize their work; limited to 15 minutes
  • Information Radiator – Highly visible, public display of information
  • INVEST  – A mnemonic to remember the qualities of a good user story
  • Iteration – Fixed period of time for development; in my workplace 2 weeks; anything from 1 to 4 weeks is common
  • Kanban – Process to visualize (and hopefully improve) workflow
  • Lean – Remove waste to concentrate on value-adding activities – A way of thinking
  • Minimal Marketable Feature / MMF – The smallest possible set of functionality that a customer is willing to pay for
  • Prime Directive – Sets the context for retrospectives to keep them constructive
  • Product Backlog – List of desired functionality for a product; in descending order of ROI; Scrum artifact
  • Product Owner – provides the product vision; 1 of 3 scrum roles
  • Retrospective / Retro – Looking back to find things to improve
  • Scrum– A framework for process improvement
  • ScrumBut – When people do Scrum but altering certain aspects that “break” Scrum
  • Scrum Master / SM – protects the process (i.e. scrum); coaches the dev team; 1 of 3 scrum roles
  • Scrum of Scrums / SoS – Representatives of collaborating scrum teams meet to coordinate
  • Sprint – Scrum term for Iteration; no additions to the Sprint Backlog are allowed during the Sprint – the developers can work in peace
  • Sprint Backlog – Items taken from the Product Backlog that the developer team think they can finish during the sprint; usually Sprint Backlog = Task Board; Scrum artifact
  • User Experience / UX – Every interaction a customer has with a certain program / service / company
  • Work In Progress / WIP – The number of jobs that were started, but not yet finished. A central concept in Lean and Kanban. In the latter you set specific WIP limits in order to avoid context-switches (and thereby increasing productivity).

See also this very exhaustive glossary of Scrum terms.

Advertisements

What do you think?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s