Regular and ongoing communication with the customer and developer during the application development itself

Description:
Communication is the foundation of all relationships. If we want to ensure maximum awareness among developers, communication is essential. Regular stand-ups, where completed and ongoing tasks are briefly discussed, should be held several times during the work week. Communication with our user should not be forgotten either. The user can change his mind or just make some changes in the functionality. Communication saves time for all parties involved.

Links:
https://www.atlassian.com/agile/scrum/standups
https://www.hatica.io/blog/daily-standup-meetings/

Keywords:
standup, communication, meetings, development, effective development

Motivation:
Trust is a good thing. But communication wins.

Requirements/Prerequisities:
no specific software, just the time of all parties involved

Level:
generic: high level abstract best practice, metalevel category (e.g. manage architectures)

Application domain:
Data science (analysis & visualisation), Software engineering

Main phase:
Generic: Requirements/Exploration, Generic: Design/Plan, Data Science: Preparation/Integration, Data Science: Modeling/Training/Evaluation, Development: Implementation/Code/Build, Development: Testing, Operations: Deployment/Release

Related literature:
https://www.sciencedirect.com/science/article/pii/S0164121216000066
https://www.researchgate.net/profile/Viktoria-Stray/publication/266850154_An_Empirical_Investigation_of_the_Daily_Stand-Up_Meeting_in_Agile_Software_Development_Projects/links/543cfb9e0cf2c432f7423232/An-Empirical-Investigation-of-the-Daily-Stand-Up-Meeting-in-Agile-Software-Development-Projects.pdf

In which projects do/did you use this practice?
SIMUportfolio, webstudio