You can search for terms in the Search bar above! ;)
The Agile Dictionary
Using the Scrum framework, there is a daily meeting with the whole Team including the Product Owner, the Development Team, the Scrummaster as well as customer and external stakholders.
It is essential that all the involved members of the Scrum Team are present for this meeting. It should last no longer than 15 minutes and it is strongly recommended to do a stand-up meeting, making people uncomfortable on purpose so it does not last too long.
Each Team member should answer 3 questions:
What have I done since the last Daily Scrum?
What will I do until the next Daily Scrum?
Which impediments are in my way?
Decomposition is the process of breaking a Feature down into user stories and then translate them into tasks. It is used to facilitate the understanding of complex processes from the whole team. It is usually performed during the Backlog refinement or the iteration planning and will help to estimate tasks for a new feature release.
Definition of Done
The Definition of Done is a set of criteria defined by the Scrum team that determines whether a User Story is considered processed and finished. It is up to the Team to determine what their Definition of Done is but it has to be clear for any member of the Team. The Definition of Done can include these:
Code Review was done
Acceptance criteria Tests were ALL successful
The Product Owner has tested the Demo and validated it works accordingly to the requirements
Stress Tests were conducted
Some Teams also have a „Done Done“ state that means that 1) it reached the definition of done and that 2) it was successfully deployed and is now live.
Definition of Ready
The Definition of Ready is a set of criteria defined by the Scrum team that determines whether a User Story from the Backlog is Ready to be included in a sprint. It is up to the Team to determine what their Definition of Ready is but it has to be clear for any member of the Team, especially the Product Owner. The Definition of Ready is basically which information does the Team need to start working on a new User Story without asking hundreds of questions to the Product Owner. This should be the result of Decomposition, to break down the big user story into easily understandable, estimable working units (tasks).
The Sprint Demo (or Demonstration) is not to be confused with the Sprint Review. The Sprint Demo is part of the Sprint Review, but that’s not all. The main goal of the demo ist o shpowcase the result of the sprint, meaning showing the new feature that was implemented within the product. The whole Agile Team will attend the meeting as well as users, customers and other stakeholders. A common measure is to allocate 1 hour of meeting per week of sprint but it really depends on the complexity of the new feature.