Daily Meetings - Coordinate and Communicate Every Day

Using daily meetings for frequent course corrections. However, you should keep the meeting short because time is burn rate.

Though good collaboration doesn't guarantee a project's success, poor collaboration almost always guarantees a project's failure

What benefits does the daily meeting bring to you?

- Keeps inexperienced developers and experienced ones on-track.
- Avoids reinventing the wheel.
- Limits tumbleweed developers' damage.
- Leverages the entire team’s experience to solve problems quickly.
- Improves team communication.
- Helps every people have a big-picture
point of view.

Who are tumbleweed developers?

We’ve all worked with a few tumbleweed developers. These developers lose direction and drift through their days. They wade through the random code and “improve” it, cleaning up method signatures, polishing algorithms, and reformatting brackets. Tumbleweed developers lack the discipline to finish any task you ask them to do and generally cause more harm than good.

Tumbleweed developers will retool your algorithms for speed, but their changes cause the code to generate wrong results. They’ll spend hours reformatting code to suit their preferences. Tumbleweeds have a collection of habits that they practice because it’s the “right thing” to do.

(I all cited the above fun description from the reference book below) 


Reference

[1]. Jared R. Richardson &  William A. Gwaltney Jr. | Ship It! A Practical Guide to Successful Software Projects.