Agile IQ assement for Business teams

A good question.

There are five questions whose language currently reflects a software development team. Think of these in the following way:

68. Team processes promote sustainable development.
Team processes promote sustainable execution of the work in the Sprint.

69. Architectures, requirements, and designs, emerge from the self-organising team, not from big upfront requirements activities.
The team is self-organising and defines its own solutions to items in the Product Backlog. No one from outside the team hands down fully formed solutions to them and expects them to deliver it.

71. Product Backlog items are iterated through the Sprint with multiple define-build-test cycles (e.g. work within the Sprint is not “Waterfalled”).
Product Backlog items are iterated in the Sprint. The Sprint isn’t split into phases of activity, such as design-build-test or define-draft-review.

72. The team recognises no titles for Team members (e.g. Lead Developer, Lead Tester), regardless of the work being performed by the person.
There are no functional team titles or built-in hierarchy within the team directing people how to do their work. Everyone has an equal say and contributes equally to the Increment of work for the Sprint.

73. The team doesn’t create sub-teams or streams of work to address elements such as analysis, design, testing, etc (e.g. functional silos or “Waterfalling” within the Sprint).
The team doesn’t create sub-teams or functional silos to address and deliver specific types of work, e.g. analysis, solution design, documentation, review, etc.

In a future Sprint, we're going to adjust the language again so that it can reflect a more work types rather than being software specific.