1. Scrum survey

This survey is assessing how Scrum is used and what the outcomes are from using Scrum.

Question Title

* 1. My Scrum Team

  Strongly disagree Disagree Neutral Agree Strongly agree
has team members who are referred to as "resources"
uses Scrum as a work management system to manage unconnected work
is for a non-software product
works with at least two other Scrum teams on the same product
makes a negative material impact to value delivery as confirmed by internal customers
makes a positive material impact to value delivery as confirmed by internal customers
makes a negative material impact to value delivery as confirmed by external customers 
makes a positive material impact to value delivery as confirmed by external customers
has a project manager
uses a "definition of done done" / "definition of ready for release" or similar
uses happiness surveys
makes small bets
uses event check lists, e.g., Sprint Planning checklist
uses role check lists, e.g., Scrum Master checklist
uses "as a ....I want/need .... so that / in order to" user story template for Product Backlog Items
has a dependency / program board
has a definition of ready that is a gate to starting new work
has a definition of ready that is used as a guide 
has applause at the Sprint Review
has work in progress limits that are respected
uses an aged work policy
uses replenishment / pull polices
uses Monte Carlo probabilistic forecasting
uses Kanban board & statistics like cycle time, work in progress count, work item age, throughput, flow efficiency
has Development Team(s) who can influence the Product Owner on the Product Backlog order
counts Product Backlog Items that are "done"
uses Test Driven Development
has continuous delivery behavior to the extent that broken environments are seen as right-now-urgent
has continuous integration behavior to the extent that broken build are seen as right-now-urgent
uses Specification by Example / Behaviour Driven Development / Acceptance Test Driven Development
uses story mapping / impact mapping
uses mobbing/swarming
used "informed consent" to the extent that Scrum Team members volunteered of their own accord to be on the Scrum Team
uses system modelling
sees clear evidence that managers are changing the system / organization structure
implements at least one improvement action for the Scrum Team in the sprint
gets useful enough feedback on the increment at the Sprint Review
shows the increment instead of slides at the Sprint Review
estimates Product Backlog Items using historical reference items
has 4-10 fully actionable Product Backlog Items per sprint 
has Product Backlog Refinement with customer-end-users
works on a product that a customer would recognize, i.e., not a technical component
has one emergent Product Backlog, 1 Product Owner across all teams for each product
has a time-sensitive, customer-centric, self-managing Development Team
has all the skills to discover customer-end-user-needs and deliver a "done" increment
has team members who are full-time to the Scrum Team only
has team members who were not "volunteered" to the Scrum team
has stakeholders and team members who embrace uncertain & recurring forecasts
satisfies the Sprint Goal 
has a Sprint Goal that is stated as a business objective 
delivers a "done" increment more than once during the sprint
has a "done" increment every sprint, in accordance with a Definition of Done
has fresh Sprint Backlog that is electronically visible
has fresh Sprint Backlog that is physically visible
has Scrum events that are emphasized over other meetings
has its own Scrum Team space that it does not get forced out of
is outsourced for projects/project phases
is customer-centric
is a long-term-stable-team
is clear on the product vision
has a Product Owner with authority who manages the politics
has a stakeholder & customer-end-user list in place that is up to date
has a colocated team in the same desk area, on the same days at the same time
has a clear product vision, and an ordered Product Backlog to support the vision
is aiming to shorten the sprint length
is trained on Scrum as per the specific Scrum Team roles of Product Owner, Scrum Master and Development Team
has a Product Owner, Scrum Master and Development Team in place
has a sprint length of 1-4 weeks 
releases a product increment to the customer/market as frequently as quarterly or more often than quarterly
releases a product increment to the customer/market as frequently as monthly or more often than monthly
invests in multi-learning, tools & infrastructure, and the reduction of technical debt / failure demand
has a consistent sprint length