PSST! Need some help?

You can search for terms in the Search bar above! ;)

The Agile Dictionary


CRC Cards

CRC stands for Class, Responsibilities and Collaborators. The CRC model is a collection of index cards divided into three sections ; class that represents a collection of similar objects, responsibility that represents something a class knows or does and collaborator that represents another class with whom the class interacts to fulfill the responsibility.


In Scrum, meetings were called „ceremonies“ (now called „events“) to define four important ones within the Scrum framework :

  1. Sprint Planning

  2. Daily Scrum

  3. Sprint Review

  4. Sprint Retrospective

Connextra Format

Connextra Format is another term for the role-feature-reason template which is meant to help defining user story in a clear, concise and consistent manner. It is the most common user story format and is presented as follow:

“As a [type of user] I want [some feature] so that [some reason]

Continuous Delivery

Continuous Delivery is a very similar process to continuous development although in the former process, every piece of code is automatically tested, integrated and goes through automated acceptance tests but is not automatically deployed to production, meaning that the actual release of the functionality is made manually. This allows the company to wait before releasing a new version.

Continuous Deployment

Continuous Deployment is a process where any code commit will pass automatically tests only before releasing it into the production environment. Code will be automatically tested, then automatically integrated, acceptance tests will be run automatically and finally automatically deployed to production. It is aimed to reduce the lead time.

Continuous Integration

Continuous Integration is the pratice of integrating code changes into the main branch of a repository on a daily basis. Before being integrated to the larger code base, code changes will go through automated tests. One of the popular rules of continuous integration is that developers should never leave anything unintegrated at the end of the day. The purpose is to decrease the duration and work required for each integration episode as well as always having a releasable version at any moment.

Customer Development

Customer Development is a 4-step framework developed by the reknown entrepreneur Steve Blank to discover and validate the real customer’s needs, build the right product to satisfy these needs, test the correct methods and models to acquire and convert customers to finally deploy the right resources to scale the business. The four steps are :

  • Customer Discovery : Identify target group and understand their needs or issues

  • Customer Validation: The market is large enough to build a viable product that satisfy the customer’s needs

  • Company Creation : Your business is scalable with the user of Marketing to drive up Sales

  • Company Building : Business can grow with new hires to support demand

Customer Journey

The Customer Journey refers to the entire path of interactions that a customer goes through with a company, a service or a product. Customer Journeys can vary in terms of length and scope depending on the nature of the activities. The common Customer Journey represents all the interactions (touch points) happening from the customer being unaware of your existence through becoming aware of the product or company, investigating it, eventually buying it, using it, assimilating it to becoming an advocate for your product or company.

This is summarized into the 5 A’s:

1.     Awareness – 2. Acquisition – 3. Adoption – 4. Assimilation – 5. Advocacy

© 2019 by 🐿️

Website developed through ongoing iterative and agile development.