Agile practices
| Practice | Description | Reference |
|---|---|---|
| Daily standup | Is a short timeboxed (15-minute) every-day meeting for the development team | Schwaber and Sutherland (2017) |
| Sprint/iteration planning | Sprint is a short time-boxed (interval of time) and the work to be performed in the sprint is planned at the sprint planning. This plan is created by the collaborative work of the entire Scrum Team | Beedle et al. (1999), Schwaber and Sutherland (2017) |
| Sprint retrospective | The sprint retrospective happens after the sprint review and before the next sprint planning. The sprint retrospective is an opportunity for the Scrum Team to review itself and create a plan for corrections to be enacted during the next sprint | Schwaber and Sutherland (2017) |
| Sprint/iteration review | This is an informal meeting at the end of the sprint to inspect the increment and adapt the product backlog if needed. During the sprint review, the scrum team and stakeholders collaborate about what was done in the sprint | Schwaber and Sutherland (2017) |
| Short iterations | Short iterations are needed for an effective product delivery to be able to handle the rapid change in, among other things, requirements management | Ahmed et al. (2010) |
| Continuous testing | Continuous testing is used to reduce the time and energy required to keep the code well tested and to prevent regression errors from remaining undetected long periods | Saff and Ernst (2004) |
| Self-organizing teams | Teams that have a common focus, mutual trust, and respect. Team members are collaborating, in a speedy, decision-making process and have the ability to deal with ambiguity | Cockburn and Highsmith (2001) |
| Pair programming | Two developers working together on the development and refinement of a piece of code at one computer | Abrahamsson et al. (2017) |
| Practice | Description | Reference |
|---|---|---|
| Daily standup | Is a short timeboxed (15-minute) every-day meeting for the development team | |
| Sprint/iteration planning | Sprint is a short time-boxed (interval of time) and the work to be performed in the sprint is planned at the sprint planning. This plan is created by the collaborative work of the entire Scrum Team | |
| Sprint retrospective | The sprint retrospective happens after the sprint review and before the next sprint planning. The sprint retrospective is an opportunity for the Scrum Team to review itself and create a plan for corrections to be enacted during the next sprint | |
| Sprint/iteration review | This is an informal meeting at the end of the sprint to inspect the increment and adapt the product backlog if needed. During the sprint review, the scrum team and stakeholders collaborate about what was done in the sprint | |
| Short iterations | Short iterations are needed for an effective product delivery to be able to handle the rapid change in, among other things, requirements management | |
| Continuous testing | Continuous testing is used to reduce the time and energy required to keep the code well tested and to prevent regression errors from remaining undetected | Saff and Ernst (2004) |
| Self-organizing teams | Teams that have a common focus, mutual trust, and respect. Team members are collaborating, in a speedy, decision-making process and have the ability to deal with ambiguity | |
| Pair programming | Two developers working together on the development and refinement of a piece of code at one computer |
Note(s): The table is inspired by Highsmith (2002), VersionOne (2019)