Outputs of the Daily Stand-Up
The most valuable output from the stand-up meeting is a list of issues that need to be handled. Where traditional development may let problems go for days or weeks without resolution, stand-up meetings in Agile mean they must be worked on within the day. Developers are relieved from waiting on other departments and roles to handle their work. If a developer announces an issue with waiting on an analyst confirmation, analysts must then take responsibility for the issue.
If another department is delaying progress, the development team realizes where the issue is. With this regularly updated list of issues, the Scrum Master knows what needs to be handled by developers to work at peak efficiency.
In addition to the list of current issues, another key output of the stand-up meeting is the current status of each task. The entire Scrum team gets a verbal update, instead of relying on each other to look at a central list.
Developers know without a doubt what each other developer is working on, or has finished. When one developer finishes a task, they already know what other developers are working on, and which task they can pick up next. Instead of multiple developers picking up the same task and wasting development effort, they each grab a unique task and make progress toward finishing the product.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: