Agility Maturity Cards
State of mind
The cards related to this category deal the mindset to improve testing in an organization.
Cards category
Cards related to this category
The refinement of the US and more generally of the Backlog must also be done in a workshop with a person who plays the role of Tester
The organisation must embed the economic dimension in its structure and decisions
Communities exist within the company but outside the organisation to share knowledge and know-how
It is not about having something perfect but rather about striving for that perfection
Application of the subsidiarity principle
Rather than trying to break it
Move towards an organisation where everything can be done at the same time rather than phasing the work
Intention is better than a perfectly described but ineffective process
The refinement of the US is done in "3 Amigos" mode with post-its to brainstorm on the questions and data examples
Trying to get rid of the unnecessary and constantly optimising
The choices and means must be linked to the satisfaction of the Customer
Learning cycles should be short
Lean concepts are valuable lessons
Evaluate the solution at each increment, not the intermediate deliverables
Try to get rid of the unnecessary and constantly optimise by innovating on methods
Deliver added value very quickly and eliminate bureaucracy
Combination of Double Learning Loop / Panarchy / Theory of Constraints / Testability practices for agile testing
Rather than seeking its presence
Testability is constantly being improved
Any change needs to incorporate more holistic thinking to ensure the scope and actions required
Although they are specialists in their team, they must be able to match the skills of other team members in simple actions
The Product Backlog is understandable to the Customer
The role of the Manager is to shape the working environment rather than the solution
Not just the testers
The domain specific language (DSL) is found in all facets of the solution (the backlog, tests, architecture, code, documentation)
Rather than checking the functionality
Mastery, noble purpose and autonomy
Any choice must assume last minute changes
The amount of work in progress should be as small as possible
Pace improves predictivity, synchronisation facilitates dependencies
Teams have a rotating ambassadorial role, going out into the field and must network to facilitate their objectives