{"id":555,"date":"2020-07-26T19:56:59","date_gmt":"2020-07-26T18:56:59","guid":{"rendered":"http:\/\/www.danieledavi.com\/blog\/?p=555"},"modified":"2020-07-26T19:57:09","modified_gmt":"2020-07-26T18:57:09","slug":"is-your-team-doing-scrum","status":"publish","type":"post","link":"https:\/\/www.danieledavi.com\/blog\/2020\/07\/is-your-team-doing-scrum\/","title":{"rendered":"Is your team doing Scrum?"},"content":{"rendered":"\n

There many tools and checklists to verify wether your team is doing Scrum and how good (or or bad or ugly) is implementing it. If you are a Scrum Master, self-assessing the following statements from 1 (strongly disagree) to 5 (strongly agree) can help you to make a reality check and compare results with your team feedback.<\/p>\n\n\n\n

  1. The results of Team retrospectives are actionable.<\/li>
  2. My team utilizes end user feedback to determine whether features have delivered value or not.<\/li>
  3. I coach the team to practice the agile mindset based on agile values and principles.<\/li>
  4. I assist the team with creating effective user stories.<\/li>
  5. The team interacts in a respectful way<\/li>
  6. The team members have courage to do the right thing and work on tough problems. <\/li>
  7. The team members personally commit to achieving the goals of the Sprint.<\/li>
  8. My team limits work in progress .<\/li>
  9. The team is aware of the product vision and direction. <\/li>
  10. I work with the product owner to ensure high level objectives are set and explain to the team. <\/li>
  11. The team acts on at least one retrospective feedback item during the next planned iteration. <\/li>
  12. The team maintains a steady rate of productivity without being overworked or incurring a necessary technical debts. <\/li>
  13. The scrum team as a shared understanding of the Sprint goal. <\/li>
  14. If I’m gone or on vacation, my team is effective without me. <\/li>
  15. The team is able to swarm when necessary to help complete the remaining deliverables within an iteration.<\/li>
  16. The scrum team is adept at recognising and dealing with impediments. <\/li>
  17. The team members communicate in high-bandwidth manner without undue interference. <\/li>
  18. I work with the team to ensure the product backlog is prioritised in a way which produced the highest value outcome.<\/li>
  19. I actually engage with other stakeholders of the organisation to help remove team impediments. <\/li>
  20. I provide coaching for the team helping them to do the best work. They possibly can.<\/li>
  21. I look for new areas in the organisation where scrum can be applied. <\/li>
  22. I find ways to inform stakeholders about the scrum framework, they roles and expectations. <\/li>
  23. I regularly collaborate with others to share better ways of working.<\/li>
  24. I have a good working relationship with the team. <\/li>
  25. I encourage my team to improve continuously. <\/li>
  26. The whole team knows what they want to achieve for the day at the end of each stand up.<\/li>
  27. Stand-up meetings are effective at synchronising work. <\/li>
  28. Stand up happens, even when the product owner and the Scrum Master are not there.<\/li>
  29. The team gets meaningful feedback about the product during the Sprint review. <\/li>
  30. The release plan and or product roadmap are discussed during the Sprint review. <\/li>
  31. Sprint retrospective is a safe space<\/li>
  32. Facilitation of the Sprint retrospective is a shared responsibility. <\/li>
  33. The Sprint duration in calendar days does not change based on the number of working days<\/li>
  34. The team holds retrospective meetings at the end of each iteration in which they evaluate how they are doing and discuss how to get better.<\/li>
  35. In my team all scrum events are facilitated effectively, even when I’m not present. <\/li>
  36. The team and stakeholders can openly discuss challenges by having visibility of the Sprint and the product backlog at all times.<\/li>
  37. The whole team understand the work to be implemented after the planning session. <\/li>
  38. The team consistently adheres to its Definition of Done.\u00a0<\/li>
  39. The scrum team is happy and proud of the work delivered.<\/li>
  40. The team satisfy the customer through early and continuous delivery of valuable software.<\/li><\/ol>\n","protected":false},"excerpt":{"rendered":"

    There many tools and checklists to verify wether your team is doing Scrum and how good (or or bad or ugly) is implementing it. If you are a Scrum Master, self-assessing the following statements from 1 (strongly disagree) to 5 (strongly agree) can help you to make a reality check and compare results with your […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[263],"tags":[252,253],"class_list":["post-555","post","type-post","status-publish","format-standard","hentry","category-agile-2","tag-agile","tag-scrum"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t