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

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.


standup, communication, meetings, development, effective development

Trust is a good thing. But communication wins.

no specific software, just the time of all parties involved

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:

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

Data Analyst, Project Manager, Researcher

3–5 years of experiences
Masaryk University

1. How do ​you rate the potential benefit for your projects? 5
2. How often are you using that practice? 3
3. What is the effort to introduce the practice in your project upfront? 3
4. What is the effort to apply the best practice in your project daily basis? 2

Questions 1, 3 and 4 (1 = Low, 5 = High)
Question 2 (1 = Never, 5 = Always)

You are running an old browser version. We recommend updating your browser to its latest version.

More info