Classical mistakes at daily scrum meetings
•
0 gostou•830 visualizações
Classic Mistakes • Missing Team Members • Not Starting the Meeting at the Same Time • Not Making the Meeting at the Same Place • Turning Daily Scrum into a Report Meeting • Not Getting Prepared For The Meeting • Zombie Team Members • Lack of awareness for the obstacles • Meetings without burn down chart, or updated scrum board • Turning Daily Scrum into Technical / Requirement Meeting • Talkative chicken on the floor • Not listening to other team members during the meeting • Meetings with Computers • Lack of Acceptance of Meeting • Extending the meeting over 15 minutes
Recomendados
Recomendados
Mais conteúdo relacionado
Destaque
Destaque (20)
Semelhante a Classical mistakes at daily scrum meetings
Semelhante a Classical mistakes at daily scrum meetings (20)
Último
Último (20)
Classical mistakes at daily scrum meetings
- 2. Daily Scrum Meeting • What is Daily Scrum Meeting? • Timeboxed with 15 minutes, • Done at the same place, • Done at the same time, • Scrum Team shares the answer of: • What has been accomplished since the last meeting? • What will be done before the next meeting? • What obstacles are on the way? For more details: http://www.scrumguides.org/ http://www.erdemseherler.com
- 3. Classic Mistakes • Missing Team Members • Not Starting the Meeting at the Same Time • Not Making the Meeting at the Same Place • Turning Daily Scrum into a Report Meeting • Not Getting Prepared For The Meeting • Zombie Team Members • Lack of awareness for the obstacles • Meetings without burn down chart, or updated scrum board • Turning Daily Scrum into Technical / Requirement Meeting • Talkative chicken on the floor • Not listening to other team members during the meeting • Meetings with Computers • Lack of Acceptance of Meeting • Extending the meeting over 15 minutes http://www.erdemseherler.com
- 4. Classic Mistakes • Missing Team Members • The meeting • For the team • For sharing and aligning knowledge • For giving feedback • If team members miss it • Last minute information cannot be gathered/shared • Feedback is not taken/given http://www.erdemseherler.com
- 5. Classic Mistakes • Not Starting the Meeting at the Same Time • The meeting may not be done daily • The meeting may not be done at the same time • Late team members • Efficiency of the team members • Many teams prefer to make the meeting first event of the day • Consider efficiency of using the time before the meeting http://www.erdemseherler.com
- 6. Classic Mistakes • Not Making the Meeting at the Same Place • Location of the meeting • In front of the scrum board • Team should see the scrum goals • Team should be able to see the status of current stories or tasks http://www.erdemseherler.com
- 7. Classic Mistakes • Turning Daily Scrum into a Report Meeting • Reporting to Scrum Master • Reporting to Product Owner • Reporting to a non-team member (Chicken on the floor) • Precautions: • Remove eye contact between the Reporter and the Reported • Moving behind another team member to get out of the eye contact • Make a hand sign by showing other team members for the team member to speak to them rather than to me http://www.erdemseherler.com
- 8. Classic Mistakes • Not Getting Prepared For The Meeting • Forgetting the answers or not getting prepared for the three questions • Not selecting what to do until next meeting before the meeting • Not thinking about impediments, or documenting them before the meeting http://www.erdemseherler.com
- 9. Classic Mistakes • Zombie Team Members • The voice of the speaker • Hard to hear • Can be heard by himself/herself only • Automatic answers • Worked on task 123 • what is task 123? • Not finished, I’ll continue to work on it • When will it be finished? • Why is it not finished on time? • Do you need help on task? • I’ll start to work on a new task? • Which one? • I have no impediments • If the person had one, will s/he share it? • Why is the tasks are taking longer than the estimation if there is no impediments? http://www.erdemseherler.com
- 10. Classic Mistakes • Lack of awareness for the impediments • Lack of sharing even if there are impediments • Lack of awareness about the impediments • Not running after continues improvement opportunities • Not knowing the continues improvement techniques • Not thinking to make something better • Get used to problems or ignoring • Do not value to write the impediment to impediment list • No impediment list • Trust issue– (how other team members might act about my personal/technical gap?) http://www.erdemseherler.com
- 11. Classic Mistakes • No (updated) Scrum Board • A daily scrum meeting without a scrum board • There might be a scrum board but has outdated information • Cannot see how far is the scrum team from sprint goal • What is the velocity target for the sprint? • What is our velocity before the meeting? • What will be our velocity at the end of the day? • No burn down or burn up chart • On which tasks do we have to work for our daily target? http://www.erdemseherler.com
- 12. Classic Mistakes • Turning Daily Scrum into Technical / Requirement Meeting • Telling more than the context of three daily scrum questions • Extending 15 minutes (the timebox for daily meeting) • If there is a need for a technical or requirement meeting • Schedule a meeting with only the necessary contributors after the daily scrum meeting http://www.erdemseherler.com
- 13. Classic Mistakes • Talkative chicken on the floor • The daily scrum is for the team members • Chickens can attend and listen • It is not preferred a chicken to come and get into conversation • If any chicken needs knowledge sharing, or status meeting it should be handled as another meeting separately. http://www.erdemseherler.com
- 14. Classic Mistakes • Not listening to other team members during the meeting • Any issue that causes not paying attention the other members should be removed • Every team member should be able to see each other • Circle Style Meeting • Removing noise or any attraction taking staff away from the environment http://www.erdemseherler.com
- 15. Classic Mistakes • Meetings with Computers • Sometimes the team prefers to keep the scrum board digitally. In such a case: Attention can be taken • via single computer with a projector, • to the speaker who controls the computer; • if all of the team members have their computers in front of them; their focus turns into their own screens rather than the shared screen and sharing team member http://www.erdemseherler.com
- 16. Classic Mistakes • Lack of Acceptance of Meeting: • Team members do not value the meeting • common indicator: scrum master who needs to invite other team members to start the meeting http://www.erdemseherler.com
- 17. Classic Mistakes • Extending the meeting over 15 minutes • Topics out of the agenda (3 questions) • Turning meeting into another meeting i.e. technical / requirements meeting • Chickens on the floor • Depending on the team size, every team member should given 2-3 minutes. (15 minutes max all) • A timer can be used for to track the time http://www.erdemseherler.com
- 18. Contact Me This presentation is based on the article at http://www.erdemseherler.com/pages-in-english/classic- mistakes-at-daily-scrum-meetings/ For feedback and questions www.erdemseherler.com/contact-me/ www.erdemseherler.com @erdemseherler http://www.erdemseherler.com