The purpose of the daily standup is to inspect the progress being made toward the sprint goal and to adapt the work where necessary.
This ensures that the team’s work and progress is visible to all team members and provides a regular feedback loop for the team.
2/14
Effective daily scrums promote collaboration and self-organization.
For PMs, this is a game changer: rather than having to liaise, track, and manage work across the team, the daily standup encourages team members to self-organize and hold each other accountable.
3/14
As a result, there is no set facilitator for a daily scrum meeting. In attendance, at minimum, should be the product team, including the PM & scrum master or delivery manager.
Other stakeholders are welcome, but any attendees outside of the team should be observers only.
4/14
There is no set way to run a daily scrum, but the most common meeting agenda template is known as the three questions format:
1. What did I achieve yesterday? 2. What do I plan to achieve today? 3. Are there any impediments to achieving that?
5/14
The daily scrum is best held at the same time and place each day.
It is common for teams to hold the daily scrum at the start of the day. However, if your team is distributed or has part-time team members, you may need to consider what time of day is best for everyone.
6/14
An alternative daily scrum format is known as walking the wall (also called walking the board).
Rather than having each team member talk about what they did yesterday & what they plan to do today, you walk through the team’s kanban or task board & give updates on each item
7/14
When done incorrectly, the daily scrum can provide little value to the team.
Keep an eye out for anti-patterns. Anti-patterns are behaviors that act against the original intent of the daily scrum. Without correction, anti-patterns can render the daily scrum ineffective.
8/14
Some anti-patterns that could derail your daily scrum:
• Lack of coordination/collaboration
• Lack of communicate outside daily scrum
• Siloed workflows
• Poor attention in meetings
• Lack of accountability
• Redundant updates
• Vague or evasive updates
9/14
Remember, the daily scrum is not a replacement for continuous communication. Product teams often identify the need for deeper and more detailed discussion during the daily standup, but it shouldn’t be the only place where communication happens.
10/14
Some best practices for running an effective daily scrum:
• Hold it at the same time & place each day
• Set aside time for offline discussions after the meeting
• Rotate the facilitator
• Meet in front of the team’s kanban board
• Set a timer & make it visible
11/14
Quick etymological aside: The terms daily standup & daily scrum are often used interchangeably. Technically, the ceremony is a daily scrum, which is typically held in a 15-minute stand-up meeting. This distinction matters because some team members may be unable to stand.
12/14
The term daily scrum is inspired by the idea that modern product development should be more like a rugby team, moving in unison across the field, than a relay race.
Like in rugby, the daily scrum ensures team members are progressing as a unit toward the sprint goal.
13/14
The daily scrum is a great tool for promoting self-organization, accountability, & adaptability
Over the years, new agile methods have gained wide adoption. It's easy to see the benefit in meeting daily to ensure everyone is abreast of the latest trends & on the same page
14/14
• • •
Missing some Tweet in this thread? You can try to
force a refresh
The product lifecycle constantly evolves. Keeping everyone informed w/ a product roadmap is critical to getting the 360-degree buy-in you need to position your product for long-term success.
A product roadmap is a shared, living document that outlines the vision & direction of your product throughout its lifecycle. It articulates what you are building & why. It also lays out a strategy for delivering value & serves as a plan for executing this product strategy.
2/13
It’s the product manager’s responsibility to build & manage a live roadmap that is fluid & resilient. They must convince stakeholders why the investment makes sense, obtain buy-in from inside & outside the org, set expectations, & generate excitement about what’s to come.
If you’re part of a cross-functional product team, you may have taken part in a sprint retrospective. If you’re new to #productmanagement, this guide will get you up to speed on what a sprint retro is and why it’s important
A sprint retrospective is a scrum ceremony that is held once a sprint has ended to reflect on the work that has just taken place.
The team reviews processes, ways of working, and key learnings with the aim of improving the team’s performance during subsequent sprints.
2/12
A sprint retrospective is held at the end of a sprint, before the next sprint begins. If your sprint is 2 weeks long, the sprint retro meeting might be as short as 1 hour. If you’re working on a longer sprint cycle or on a larger team, the retro might last up to 3 hours.
1. Individuals and interactions over processes and tools 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. Responding to change over following a plan
1/10
People often reference the four values without considering the introduction, but it’s important to establish a philosophy of constant change and improvement as well as generosity:
"We are uncovering better ways of developing software by doing it and helping others do it."