Glossary

Onderstaand vindt u verschillende definities en aanvullingen op de meest gehanteerde termen van deze site.


A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z

A

Acceptance Test Driven Development (ATDD)

Scrum.org: “Test-first software development practice in which acceptance criteria for new functionality are created as automated tests. The failing tests are constructed to pass as development proceeds and acceptance criteria are met.”

Agile Projectleider

Agitma: “Projectleider verantwoordelijk voor de start, uitvoering en afronding van een project uitgevoerd in een Agile context. Hierbij worden best practices van projectmanagement methonden zoals Prince2 gecombineerde met die uit de Agile beweging.”

Agile Testing

Agitma: “Agile Testen is een werkwijze waarin de principes van Agile software ontwikkeling worden gevolgd bij de voorbereidingen en uitvoer van testen.
(vgl. Growing Agile, Ambler Scot, Wikipedia Agile Testing)

B

Backlog

See Product Backlog

C

Component Team

Innolution: “A team that focuses on the creation of one or more components of a larger product that a customer would purchase. Component teams create assets or components that are then reused by other teams to assemble customer-valuable solutions.”
(vgl. Feature Team)

Continuous Integration

Gartner: “Continuous integration (CI) systems provide automation of the software build and validation process driven in a continuous way by running a configured sequence of operations every time a software change is checked into the source code management repository.”

Continuous Delivery

Martin Fowler: “Continuous Delivery is a software development discipline where you build software in such a way that the software can be released to production at any time.”
(vgl. Jez Humble & David Farley, Martin Fowler)

Continuous Delivery Maturity Model (CDMM)

Agitma: “Modellen om op basis van vragenlijsten en observaties te categoriseren op welk niveau een organisatie zich bevindt met betrekking tot Continuous Delivery. Hierbij is de doelstelling voor om de eerst volgende verbeteringen inzichtelijk te maken.”
(vgl. Info Support CDMM, InfoQ CDMM)

D

DevOps

Agitma: “Organisatiemodel waarbij (Scrum) teams verantwoordelijk zijn voor de gehele life cycle van software. Vanaf de ontwikkeling, het live brengen en beheren, tot en met het decommisionen van deze software.”
Scrum.org: “An organizational concept serving to bridge the gap between development and operations, in terms of skills, mind-set, practices and silo-mentality. The underlying idea is that developers are aware of, and in daily work consider implications on operations, and vice versa.”
(vgl. The Agile Admin, DevOps.com)

Disciplined Agile Delivery (DAD)

DisciplinedAgileDelivery.com: “is a process decision framework for Enterprise I.T. The main characteristics of this framework are that it: is a people-first, learning-oriented hybrid agile approach; has a risk-value delivery lifecycle; is goal-driven; is enterprise aware; is tactically scalable at the team level; and scalable strategically across all of IT.”
(vlg. Scaling Agile)

E

F

Feature Teams

Bas Vodde & Craig Larmang: “is a long-lived, cross-functional, cross-component team that completes many end-to-end customer features—one by one.”

Innolution: “A cross-functional and cross-component team that can pull end-customer features from the product backlog and complete them.”
(vgl. Component Team, Mike Cohn: The benefits of Feature Teams)

G

Gemba Walk

Lean.org: “A management practice for grasping the current situation through direct observation and inquiry before taking action. Gemba means ‘actual place’ in Japanese. Lean Thinkers use it to mean the place where value is created. Japanese companies often supplement gemba with the related term ‘genchi gembutsu’ — essentially ‘go and see’ — to stress the importance of empiricism.”
(vgl. GoLeanSixSigma.org: GembaWalk, Wikipedia: Genba, Lean)

H

Hackathon

Wikipedia: “A hackathon (also known as a hack day, hackfest or codefest) is an event in which computer programmers and others involved in software development and hardware development, including graphic designers, interface designers and project managers, collaborate intensively on software projects. Occasionally, there is a hardware component as well. Hackathons typically last between a day and a week.”
(vgl. 8 Kinds of Projects You Meet at a Hackathon, Hackathon Guide)

High Performance Team (HPT)

Wikipedia: “High-performance teams (HPT) is a concept within organization development referring to teams, organizations, or virtual groups that are highly focused on their goals and that achieve superior business results. High-performance teams outperform all other similar teams and they outperform expectations given their composition.”
(vgl. Chris Warner: High Performance Teams)

I

J

K

Kanban

LeanIt.com: “Kanban is Japanese for ‘visual signal’ or ‘card.’ Toyota line-workers used a kanban (i.e., an actual card) to signal steps in their manufacturing process. The system’s highly visual nature allowed teams to communicate more easily on what work needed to be done and when. It also standardized cues and refined processes, which helped to reduce waste and maximize value. A new application of Kanban emerged for knowledge work as early as 2005, and an inquisitive community formed in 2007 around the leadership of David J. Anderson.”
(vgl. Scrum vs Kanban, Kanban Scrum Minibook)

L

Large Scale Scrum (LeSS)

Wikipedia: “Large-Scale Scrum (LeSS) is a product development framework that extends Scrum with scaling rules and guidelines without losing the original purposes of Scrum. LeSS stands for the general techniques for scaling Scrum and Agile Development to more than one team and it is the name for the basic LeSS Framework which works up-to around 8 teams. The second LeSS Framework is named “LeSS Huge” and introduces additional scaling elements for development up to hundreds of developers.”
(vgl. InfoQ: LeSS at JP Morgan, Less.works, Scaling Agile)

Lead by Example

Agitma: “Het gewenste (voorbeeld) gedrag en houding laten zien en uitdragen zodat andere individuen, teams of afdelingen deze gedragingen ook laten zien. In de Agile context komt dit neer op het laten zien en bewijzen dat de werkwijzes daadwerkelijk meerwaarde hebben en bijdragen aan de kwaliteit en snelheid waarmee software kan worden ontwikkeld.”
(vgl. Scoop.it: Management, AgileAlliance: Leading by Example)

Lean (IT)

Lean.org: “The core idea is to maximize customer value while minimizing waste. Simply, lean means creating more value for customers with fewer resources.”
(vgl. Poppendieck: The Lean Mindset, Martin Fowler: Lean vs Agile)

M

Minimal Viable Product (MVP)

Eric Ries: “The minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.”
(vgl. Henrik Kniberg: MVP, Wikipedia: Lean Startup, Eric Ries: Startup Lessons Learned)

N

Nexus

Scrum.org: “Nexus is a framework that drives to the heart of scaling: cross-team dependencies and integration issues.
It is an exoskeleton that rests on top of multiple Scrum Teams who work together to create an Integrated Increment. It builds on the Scrum framework and values.”

(vgl. Nexus Guides, Gunther Verheyen: Scaled Professional Scrum)

O

P

Prince2

Prince2.org: “PRINCE2 (an acronym for PRojects IN Controlled Environments) is a de facto process-based method for effective project management. Used extensively by the UK Government, PRINCE2 is also widely recognised and used in the private sector, both in the UK and internationally. The PRINCE2 method is in the public domain, and offers non-proprietorial best practice guidance on project management.”
(vgl. APMG: combine Prince2 & Agile, Prince of Scrum)

Product Backlog

Scrum.org: The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.”

Product Owner

Scrum.org: “The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.”

Q

R

Retrospective

Scrum.org: “The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.”

S

Scaled Agile Framework (SAFe)

ScaledAgileFramework.org: “is an interactive knowledge base system for implementing agile practices at enterprise scale.”
(vgl. Scaling Agile, Schwaber: UnSAFe)

Scaling Agile

Agitma: “Een werkwijze om de voordelen van Agile werken (met name Scrum) binnen teamverband door te trekken naar meerdere teams, afdelingen of hele organisaties. De laatste jaren zijn er meerdere varianten gepubliceerd.”
(vgl. Disciplined Agile Delivery, Scaled Agile Framework, Large Enterprise Scrum, Nexus)

Scrum Master

Scrum.org: “The Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules.”

Spotify Engineering Culture

Agitma: Beschrijvingen van Henrik Kniberg e.a. aan de hand van filmpjes over de geëvolueerde cultuur binnen Spotify
(vgl. Spotify Engineering Culture – Part I, Spotify Engineering Culture – Part II)

Sprint Backlog

Scrum.org: “The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment.”

T

Test Driven Development (TDD)

AgileAlliance: “Test-driven development refers to a style of programming in which three activities are tightly interwoven: coding, testing (in the form of writing unit tests) and design (in the form of refactoring).”
(vgl. Acceptance Test Driven Development, Martin Fowler: TDD, James Shore: TDD)

Team Lead

Agitma: “Persoon die (vaak ook hiërarchisch) leiding geeft aan een team en hier tevens in meewerkt (meewerkend voorman). In de Agile/Scrum context heeft deze rol een grote overlap met die van de Scrum Master.”

T-shaped

TSummit.org: “T-shaped professionals are characterized by their deep disciplinary knowledge in at least one area, an understanding of systems, and their ability to function as “adaptive innovators” and cross the boundaries between disciplines.”
(vgl. HBR: T-Shaped Managers, TSummit.org)

U

V

Velocity

Scrum.org: ” an optional but often used indication of the average amount of Product Backlog turned into an Increment of product during a Sprint. It is tracked by the Development Team for use within the Scrum Team.”

Visualisaties

Agitma: “Visualisaties zijn grafische uitingen over de toestand van een project, sprint of product. Het doel is om in een oogopslag belangrijke informatie helder te maken voor belanghebbenden. Scrum teams gebruiken vaak de team area om de deze op te hangen of op dashboards te laten zien.”
(vgl. Innolution: Visual Lexicon, InfoQ: Visualize Agile, Crisp: AgileToolbox – Visualizations)

W

Waste

Poppendieck: “Anything that does not add value.”
(vgl. ScrumAlliance: Waste, Poppendieck: Discovering Waste, Wikipedia: Lean Software Development)

X

Y

Z

Glossary

Mission statement

Setup, guide and coach high performing teams capable in delivering truly great software.

Be Awesome

How? Try to improve something small everyday..... In management, in coding or life.

Learn from anybody

Be aware that every colleague, teammember or friend is capable of something that you are not.

Fail and letting fail

Failure is the only way to success, so fail fast and fail often, especially in software development.