Adaption

Adaption is one of the Scrum pillars that enable empirical process control. The other ones are Inspection and Transparency. Furthermore, regular Inspection and Adaption are demanded by the last principle of the Agile Manifesto. Therefore, many agile teams do regular retrospectives to improve themselves.

Agile Manifesto

In February 2001, 17 people met in Snowbird, Utah, for an exchange and discussion about their ways of software development. They followed different methods and agreed on a list on their shared ideas and the basic thoughts they had in common. This Agile Manifesto states 4 so-called values: Individuals and Interactions > Processes and Tools

Commitment

Commitment is one of the Scrum values.

Courage

Courage ist one of the Scrum values, as well as of the XP values. It’s my favourite!

Customer Satisfaction

Customer Satisfaction is the first and highest of the principles of agile software development. See the Agile Manifesto.

Development Team

The Development Team is a role in Scrum. While the Product Owner focusses on WHAT? to do and the Scrum Master on HOW to improve?, the Development Team is responsible on HOW to realize the features. The development team is between 3 to 9 team members, it is cross-functional having all the skills it needs

eXtreme Programming

eXtreme Programming is a toolset for high quality agile software development. It is often abbreviated by XP. eXtreme Programming comes with a set of values, principles, and practices. Accordingly to XP, it’s not possible to successfully develop software without constant acknowledgement of these values: Courage Respect Simplicity Feedback Communication

Feedback

Feedback loops are the basis of learning and continuous improvement in agile development. They can be found at several levels throughout different frameworks: Compiler feedback Pairing feedback from the pairing partner Feedback from the automated test system Daily feedback in the daily standup meetings Customer or stakeholder feedback on the product in the review meetings

Focus

Focus is one of the Scrum values.

Inspection

Inspection is one of the Scrum pillars that enable empirical process control. The other ones are Transparency and Adaption. Furthermore, regular Inspection and Adaption are demanded by the last principle of the Agile Manifesto. Therefore, many agile teams do regular retrospectives to improve themselves.

Motivation

The Agile Manifesto demands: Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. But what motivates people? In his book “Drive” Daniel Pink describes the main factors for motivating people in knowledge work are: Autonomy Mastery Purpose But how do we foster these

Openness

Openness is one of the Scrum values.

PO

PO is a typical shortcut for Product Owner.

Product Backlog

The Product Backlog is the one only space, where requirements for a product are listed. It usually is a lost of items, which are formulated as User Stories. The items should be estimated and ordered. The Product Owner is responsible for the Product Backlog.

Product Owner

The Product Owner is a specific role defined in the Scrum framework. While the Development Team members focus on the HOW? of a feature and the Scrum Master focusses on the improvement of the team. the Product Owner focusses of the WHAT? of the development. It is usually abbreviated by PO.

Respect

Respect is one of the Scrum values, as well one of the XP values.

Retrospective

The Retrospecitive is a meeting for the team to gather information about their work and improve. Retrospectives are mandatory elements in Scrum and XP. For making an open and honest talk possible, the facilitator of the retrospective has to lay ground for a safe space and respectful conversation. I recommend to settle on working agreements.

Review

The Review Meeting is for getting customer or stakeholder feedback. The entire team demonstrates what they achieved in the last iteration. They listen to the stakeholders to learn about their opinions.

Scrum

Scrum is a framework for complex product development. It originates, but is not restricted to IT. It was first presented to the public at the OOPSLA Business Object Design and Implementation Workshop in 1995 by Jeff Sutherland and Ken Schwaber, and ever since optimized and updated. Key features of this framework are the 3 roles

Scrum Master

The Scrum Master (also spelled ScrumMaster) is a specific role in the Scrum framework. While the Product Owner focusses on the WHAT? of the development and members of the Development Team focus on the HOW? of the work, the Scrum Master focusses on the question How can we improve?. It is usually abbreviated by SM.

Selforganization

Agile methodologies build on selforganized teams: they organize and manage themselves in a high performing way. Successful teams need to be diverse be stable be cross-functional trust each other have a good conflict and failure culture commit to their common goal take accountability focus on team results To become a real high performing team, teams

Simplicity

Simplicity is one of the principles of the Agile Manifesto. Simplicity is also one of the XP values. Simplicity means that we maximize the work that we do not do… and still deliver value to the customer, and still deliver a high quality product.

SM

SM is a typical shortcut for Scrum Master oder ScrumMaster.

Story Points

User Stories typically are estimated in so-called Story Points. This is a new, fictitious unit for estimation. For estimating the size of a User Story these dimensions are taken into account: Effort Complexity Risk   Story Points usually are limited to the simplified Fibonacci numbers: 1 – 2 – 3 – 5 – 8 –

Tester

Testers are team members in a crossfunctional agile team. Product Owner and Scrum Master

Transparency

Transparency is one of the Scrum pillars that enable empirical process control. The other ones are Inspection and Adaption. Furthermore Transparency is the basis of visual management and enhances the visibility of project status, which is one of the main goals to introduce agility for most organizations.

User Story

A User Story is a very short description of the need a user wants to solve with the product and his reasons. My favourite pattern is: As a    …   <WHO> I want  …   <WHAT> so that …   <WHY> A User Story is to be enriched by acceptance criteria: criteria that tell how to demo that this

Vision

In agile methods we often work with Visions to set clear goals and align all people included in product development. A vision is often formulated as an product vision statement: For … «target customer» Who … «needs» The … «product name» Is a … «product category» That … «product benefit. Reason to buy» Unlike …

VUCA

Many articles I read in the last time are referring to a “VUCA” world that we life in. This means V – volatile -> with unstable challenges U – uncertain -> with unknown outcomes C – complex -> with many interconnected parts A – ambiguous -> with lack of clarity See also my blog-post on

XP

XP is a shortcut for eXtreme Programming.