Software Engineering, Project Management, and Effectiveness
On my teams we do a daily sync meeting. It's 10 minutes max. We go around the team with three questions:
We stay out of details (that's for offline and follow-up). It's a status meeting more on accomplishments and progress over reporting activities (lots of folks are doing lots of things, so it's crisper to focus on accomplishments.) The more distributed the team, the more important the meeting.
Keys to Results
The best pattern that has worked over time is ...
Another way of thinking about this is ... "if this were the end of the week, what would you feel good about having completed?" "Each day, are we getting closer or further, or do we need to readjust priorities or expectations?" ... "What did we learn and what can we improve?"
My Related Posts
One of the things we've learned in our daily standups is that enumerating work-in-process is far more efficient than enumerating headcount. Which, of course, is characteristic of the difference between workflow-oriented Lean thinking vs. craft-oriented Agile thinking.
Thanks J.D. This is a great tip for effective work.