{"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":{"ngg_post_thumbnail":0,"footnotes":""},"categories":[263],"tags":[252,253],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p90hsv-8X","jetpack-related-posts":[{"id":462,"url":"https:\/\/www.danieledavi.com\/blog\/2020\/02\/run-daily-scrum-like-a-pro\/","url_meta":{"origin":555,"position":0},"title":"Run daily Scrum like a pro","author":"Daniele Dav\u00ec","date":"February 13, 2020","format":false,"excerpt":"The daily scrum is the heartbeat of a scrum team.As Scrum is a compression algorithm for organizational and engineering best practices, this meeting is not a Scrum invention but it is considered an Agile best practice independently from the adopted framework. It is also known as StandUpMeeting (1993 Jim Coplien),\u2026","rel":"","context":"In "Agile"","block_context":{"text":"Agile","link":"https:\/\/www.danieledavi.com\/blog\/category\/agile-2\/"},"img":{"alt_text":"daily plank","src":"https:\/\/i0.wp.com\/www.danieledavi.com\/blog\/wp-content\/uploads\/2021\/03\/daily_plank.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.danieledavi.com\/blog\/wp-content\/uploads\/2021\/03\/daily_plank.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.danieledavi.com\/blog\/wp-content\/uploads\/2021\/03\/daily_plank.png?resize=525%2C300&ssl=1 1.5x"},"classes":[]},{"id":734,"url":"https:\/\/www.danieledavi.com\/blog\/2021\/10\/no-time-for-agile-meetings\/","url_meta":{"origin":555,"position":1},"title":"No time for agile meetings","author":"Daniele Dav\u00ec","date":"October 23, 2021","format":false,"excerpt":"One of the most recurring topics in many organizations is time spent on meetings.\u00a0If you are a Scrum Master, you may find yourself rolling your eyes like in a Robert Downey Jr meme and you wish you would get a euro for every time you hear someone saying in agile\u2026","rel":"","context":"In "Agile"","block_context":{"text":"Agile","link":"https:\/\/www.danieledavi.com\/blog\/category\/agile-2\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.danieledavi.com\/blog\/wp-content\/uploads\/2021\/03\/Again.jpg?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":791,"url":"https:\/\/www.danieledavi.com\/blog\/2021\/03\/changes-are-welcome\/","url_meta":{"origin":555,"position":2},"title":"Changes are Welcome","author":"Daniele Dav\u00ec","date":"March 10, 2021","format":false,"excerpt":"There are different levels of understanding\u00a0Agile.The first one is where you care about rules. You take every best practice, guide, book, training suggestion and you make a strict process out of context and without interpreting the reality. That's not Agile. That's you using Agile to cover your need of implementing\u2026","rel":"","context":"In "Agile"","block_context":{"text":"Agile","link":"https:\/\/www.danieledavi.com\/blog\/category\/agile-2\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":504,"url":"https:\/\/www.danieledavi.com\/blog\/2019\/12\/update-yourself\/","url_meta":{"origin":555,"position":3},"title":"Update yourself","author":"Daniele Dav\u00ec","date":"December 18, 2019","format":false,"excerpt":"A manifesto for Scrum adoption in your life. By Johanna Pung made this for Wikimedia Deutschland - Wikimedia Deutschland, CC BY-SA 3.0, https:\/\/commons.wikimedia.org\/w\/index.php?curid=19189236 Assuming you already heard about Agile, Scrum, Sprints and Retrospectives. As in any scrum team, the iterative and incremental process culminate in a retrospective, where members receive\u2026","rel":"","context":"In "Agile"","block_context":{"text":"Agile","link":"https:\/\/www.danieledavi.com\/blog\/category\/agile-2\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.danieledavi.com\/blog\/wp-content\/uploads\/2019\/12\/Evolution-des-wissens.jpg?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.danieledavi.com\/blog\/wp-content\/uploads\/2019\/12\/Evolution-des-wissens.jpg?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.danieledavi.com\/blog\/wp-content\/uploads\/2019\/12\/Evolution-des-wissens.jpg?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/www.danieledavi.com\/blog\/wp-content\/uploads\/2019\/12\/Evolution-des-wissens.jpg?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/www.danieledavi.com\/blog\/wp-content\/uploads\/2019\/12\/Evolution-des-wissens.jpg?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/www.danieledavi.com\/blog\/wp-content\/uploads\/2019\/12\/Evolution-des-wissens.jpg?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":671,"url":"https:\/\/www.danieledavi.com\/blog\/2020\/02\/spikes-101\/","url_meta":{"origin":555,"position":4},"title":"Spikes 101","author":"Daniele Dav\u00ec","date":"February 10, 2020","format":false,"excerpt":"Scrum is often described as a very prescriptive framework despite this is not the case. Take for example the various type of backlog items that we are used to deal with in our favourite backlog visualisation tool. Some work with Epics and User Stories only, others use a mix of\u2026","rel":"","context":"In "Agile"","block_context":{"text":"Agile","link":"https:\/\/www.danieledavi.com\/blog\/category\/agile-2\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":673,"url":"https:\/\/www.danieledavi.com\/blog\/2020\/02\/spikes-102\/","url_meta":{"origin":555,"position":5},"title":"Spikes 102","author":"Daniele Dav\u00ec","date":"February 11, 2020","format":false,"excerpt":"In my previous article \"Spike 101\" I introduced the concept of Spike and it's general use in Agile. In that article we saw that: Spikes are investigation activities -e.g: research, design, investigation, exploration, prototyping- to gain the knowledge to solve a problem.\u00a0As Scrum doesn\u2019t prescribe any particular type for Backlog\u2026","rel":"","context":"In "Agile"","block_context":{"text":"Agile","link":"https:\/\/www.danieledavi.com\/blog\/category\/agile-2\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"amp_validity":null,"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.danieledavi.com\/blog\/wp-json\/wp\/v2\/posts\/555"}],"collection":[{"href":"https:\/\/www.danieledavi.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.danieledavi.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.danieledavi.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.danieledavi.com\/blog\/wp-json\/wp\/v2\/comments?post=555"}],"version-history":[{"count":1,"href":"https:\/\/www.danieledavi.com\/blog\/wp-json\/wp\/v2\/posts\/555\/revisions"}],"predecessor-version":[{"id":556,"href":"https:\/\/www.danieledavi.com\/blog\/wp-json\/wp\/v2\/posts\/555\/revisions\/556"}],"wp:attachment":[{"href":"https:\/\/www.danieledavi.com\/blog\/wp-json\/wp\/v2\/media?parent=555"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.danieledavi.com\/blog\/wp-json\/wp\/v2\/categories?post=555"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.danieledavi.com\/blog\/wp-json\/wp\/v2\/tags?post=555"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}