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