This 3οΈβ£rd principle in SAFe is the first to address the idea of agility, where expectations can change up to the last moment. It is the direct impact of the second #agile principle described in the manifesto:
βWelcome changes in requirements, even late in the projectβ.
This assumption implies in particular:
ππΌ not going too far in the ideation to avoid having to start all over again in case of a change in the needs direction
ππΌ minimal code so as not to have to throw away too much work
ππΌ document in detail only the parts that are fixed
Application to test maturity β¬οΈ
The test should also be designed in the most flexible way possible, for example:
π Using intent-based scenarios, e.g. by a briefly described test objective in order to avoid implementation variants
π By doing exploratory testing
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (0)