The ‘Daily Scrum’ definition from the 2013 Scrum Guide in cartoon form.
(from the 2013 Scrum Guide)
The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. This is done by inspecting the work since the last Daily Scrum and forecasting the work that could be done before the next one. The Daily Scrum is held at the same time and place each day to reduce complexity. During the meeting, the Development Team members explain:
- What did I do yesterday that helped the Development Team meet the Sprint Goal?
- What will I do today to help the Development Team meet the Sprint Goal?
- Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?
The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog. The Daily Scrum optimizes the probability that the Development Team will meet the Sprint Goal. Every day, the Development Team should understand how it intends to work together as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment by the end of the Sprint. The Development Team or team members often meet immediately after the Daily Scrum for detailed discussions, or to adapt, or replan, the rest of the Sprint’s work.
The Scrum Master ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the Daily Scrum. The Scrum Master teaches the Development Team to keep the Daily Scrum within the 15-minute time-box.
The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum.
Daily Scrums improve communications, eliminate other meetings, identify impediments to development for removal, highlight and promote quick decision-making, and improve the Development Team’s level of knowledge. This is a key inspect and adapt meeting.
Take the Quiz!
About the speakers
Power Automate lets power users automate away repeatable manual processes. They can go from zero to hero in under a day!
It’s important for all your SharePoint Sites to be as consistent as possible.
In the days of classic SharePoint, subsites were a popular way of organising your intranet. Modern SharePoint architecture leans toward a flatter hierarchy, where sub-sites are generally not recommended.
Not finding stuff you have permissions to is super frustrating. So this one has always confused us…. Do you consider it a bug?
Having inconsistent resource names across projects creates all sorts of pain:
– Struggling to identify resources
– Unsure what to label new resources.
– Risk of duplicating resources
In this talk, Jason Taylor will demonstrate an approach using permission-based authorization to overcome these limitations by building a flexible approach to managing roles and permissions from within your system. This will improve the maintainability and visibility of access control across your system. Putting the power into the hands of application users and administrators, rather than developers.
On the 4th of February we welcomed everyone back to the office with a fantastic lunch! 🥗
It has been a roller coaster 12 months with restrictions, so it was amazing to see everyone back in the office working side by side again 👏
Join Adam as he delivers the latest Tech News during our March User Group.
Our development team spent a few months working really hard on this new product, and Chief Architect Adam Cogan is officially launching it today.
Do you know the security best practices for both end-users and SysAdmins?
Join Adam for the 10 tips CEOs must know for both end-users and SysAdmins.
Learn from Patrick how valuable Ocelot is and see the ins and outs of building an API gateway and protect the services using Azure VNet.