Planning

A guide on US to optimize their development

Dependencies will help testability

Balance low quality releases with operational circumstances

A charter defines the exploration session of the application to search for bugs outside the existing test cases.

Such a team has no technical barrier to generate the functionality the customer needs

Go to the field to see by yourself

Plan a marketable product, a feature and a release as soon as possible for quick feedback

Developers are working in groups on a single workstation: while one is coding, all the others are participating for an early fix

Non-Functional Requirements are part of the US to have a potentially deployable product increment

Very high goals with key results that help us reach the expectations without ever reaching them (otherwise they were too simple)

Developers are able to work in pairs on the same workstation: while one is coding, the other is reviewing the code for an early fix

Modeling the system with ecocycles to manage changes

Implementing practices like Event Storming, Lean Canvas, 25/10 Crowdsourcing, 1-2-4 All, User Story Mapping

Do everything possible at all levels of the organization to try to shift the testing effort upstream of the solution

Be able to test in production while controlling the impacts

Technical and social testability must be introduced as soon as possible

Rather than at the end of the Sprint or after

Identify bottlenecks and establish the right strategy for optimal production

The team decides that several people work on the same US in order to meet all the DoD criteria in the time of the Sprint