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