
The Daily Scrum – Part 11
Inputs to the Daily Stand-Up
Every stand-up meeting typically has an input of 3 questions answered by every team member. The development team must explain what they worked on the previous day, what they plan to work on today, and if they have any issues that are either currently or likely to impact progress. These questions address most of the concerns that might slow progress on the software product. By answering these questions at the beginning of each day, no problem goes more than a day without an update.
These questions apply to any role on the development team, but how do they specifically apply to developers? The question of what developers worked on yesterday typically covers what task they wrote code for. Also, developers should discuss what tasks they finished, if any. If they have an idea of how much time remains on a task, developers can give an estimate to the rest of the team. Similarly, what a developer is working on today focuses on the task. If developers believe that they might finish the task before the end of the day, they might announce what task they plan to work on next.
Perhaps more important than what developers are working on, is whether they are currently experiencing issues. These issues could be a variety of different problems. If developers come to an issue that needs to be confirmed, they may be waiting for analyst confirmation. If multiple departments are working together on a task, developers from one department might be waiting for another department to finish their part of the work. Anything that is preventing full efficiency should be announced as an issue.
59 Seconds Training Video
Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)
Introductory Offer: Free Course
Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)
What is this course?
This ‘Master of Agile – Agile Scrum Developer With 59 Seconds Agile (Video Training Course)’ provides an in-depth understanding of the Agile Scrum Developer roles and responsibilities
You will explore the Agile Scrum project life-cycle, including how an Agile User Story is created, to how we know when it is ‘done’
This course is aimed at those with or without prior knowledge and experience of the Agile values and principles
During this course you will learn the tools needed to succeed as an Agile Scrum Developer
What will you learn?
You will gain an in-depth understanding of the Agile Scrum Developer roles and responsibilities, and you will be able to
- Fully understand the role of the Agile Scrum Developer
- Understand the roles involved in an Agile project
- Create an effective Product Backlog
- Effectively participate in Scrum Meetings such as the Daily Stand-up, Sprint Review and Retrospective
- Identify the roles involves in the Scrum Team

What topics are covered within this course
You will cover the following topics during this course:
- An Introduction to Agile Project Management (Developer)
- The 12 Agile Principles (Developer)
- Introduction to Scrum (Developer)
- Scrum Project Roles (Developer)
- The Agile Project Life-cycle (Developer)
- Acceptance Criteria and the Prioritised Product Backlog (Developer)
- Initiating an Agile Project (Developer)
- Forming the Scrum Team (Developer)
- Epics and Personas (Developer)
- User Stories and Tasks (Developer)
- Implementation of Scrum (Developer)
- The Daily Scrum (Developer)
- The Product Backlog (Developer)
- Scrum Charts (Developer)
- Review and Retrospective (Developer)
- Validating a Sprint (Developer)
- Retrospective Sprint (Developer)
- Releasing the Product (Developer)
- The Communication Plan (Developer)
- Formal Business Sign-off (Developer)
Our Book Recommendations
We found these books great for finding out more information on Agile Scrum: