Table 11.
Summary of key findings and implications for employment of agile development and ways of working
| Finding | Implication |
|---|---|
| Decreased appreciation | There has been a significant increase in number of meetings since work-related |
| for meetings in | and catching up with colleagues are scheduled as meetings, and an increase in |
| general | back-to-back meetings which may result in more stressed and less motivated |
| practitioners. The increase in meetings in combination with challenges with | |
| digital meeting structure, e.g., hybrid meetings, have led to a decreased | |
| appreciation for meetings. | |
| Hybrid meetings | Hybrid meetings are less effective and more challenging compared to meetings |
| where all participants are either remote or onsite. Hybrid meetings creates a | |
| gap between participants that are onsite and those who are remote. | |
| Stand up meetings, | These three agile practices have |
| retrospectives, and | been particularly important. They all have been used to compensate for lack |
| pair programming | of casual conversations. Syncing conversations that usually existed in person |
| in the office are now carried out during more and longer stand up meetings. | |
| etrospective aspects, such as reflections and continuous improvement have | |
| become more important than the retrospective meetings per se. Pair | |
| programming is not only particularly important for teams and teamwork in | |
| a remote setting, but also for integrating new team members and facilitate | |
| knowledge sharing. |