Improving quality is much more than simply exploring the software, as we testers sometimes do. It is also about having a solid architecture to avoid product risks, rather than merely mitigate them. Are you aware of the impact of architecture?
To show you the impact of architecture, we use an interesting metaphor which is also a toy for (big) children! Design, build, and test a marble track while applying the SCRUM approach. You must plan, talk, cooperate, build, test, and think a few sprints ahead to anticipate future problems or risks. Besides that, you will change roles between sprints to determine if you are more critical as a tester about things you did not build.
Main topics to be covered:
• Collaboration and communication with a PO, architect, and stakeholders
• Incorporate different quality attributes in the development process
• The consequences of architectural decisions and changes related to testing
• How to keep the focus on people, process, and product
Combining all these topics, you will discover at the end of the tutorial, that it is important to think about:
• Test approaches
• Project environment (e.g. people)
• Product elements (e.g. architecture)
• Quality attributes (e.g. testability, stability)
from the beginning of the development process.
Join our tutorial to have a look from a broader perspective on how architecture relates to testing and quality.
You will:
• experience the interactions within a team while building a marble track.
• deal with restrictions and limitations within product development
• have fun playing with marbles!
Key Takeaways:- Incorporate different quality attributes in the development process
- The consequences of architectural decisions and changes related to testing
- How to keep the focus on people, process, and product
