Strategical Agile Thinking
For more than a decade, the agile manifesto and principles stir up organisations. Agile, SCRUM, Kanban, the spotify model, .... they disrupt ongoing business. Companies change their methodologies and SDLC to benefit from the numerous advantages of the agile mindset.
The result is less appealing: the ride is often bumpy, there's a lot of resistence and the change takes longer than expected. Even worse, when we drill down to the numbers, we notice that projects are not managed in a better way: they're not drastically deliverd better or faster.
are the elements that prevent a good agile approach? And what can we do
- as individuals but also as organizations - to enjoy the benefits of
an agile approach?
Shift Left - testing in the land of acronyms
Shift left, and all related buzzwords starting with continuous are in the quality policies and statements of IT professionals worldwide. But is this something new? What is the shift left movement preaching?
The talk will explain the concepts behind shift left, even with all the technological background stripped. We'll highlight TDD, BDD and ATDD, including its hallmarks, pitfalls and differences.
The secrets in game testing (синхронный перевод)
Mobile apps and games are taking over large parts of the software industry. These apps and games vary in size, complexity, business model, price and lifespan, which makes it difficult as a tester to create your own testing toolkit to verify and validate the quality of these apps and games. There are, however, quite some secrets embedded in those pieces of software.
This talk will help you - as a tester, but also as a
developer or analyst - to better understand how apps and games are
created (or should be created), and thus how it should be tested. I
elaborate on the design patterns in these apps and games and how users
unconsciously are tricked into spending more time behind their
smartphone or tablet. How can we - as testers - verify the efficiency
and effectiveness of the design pattern, or even improve the pattern
based on our feedback?
How to reduce your test cases... magically!
Team lead: “Can you please execute these 20 test cases?”
Tester: “Sure, no problem.”
Team lead: “On Windows 7. And 8. And maybe also Vista, and XP. And let’s not forget iOS!”
Tester: “Euhm, Ok, and on which browsers?”
Team lead: “I guess all of them: Internet Explorer, Firefox, Chrome, …”
Team lead: “One more thing: the developers use a new version of .NET framework, so you have to test it with 4.5, 4.0, 3.5, 3.0 and 2.0. Earlier versions are not supported anymore”
Can you imagine running every test, on each combination of operating system, browser and framework? Manually testing this is pure drudgery. Automation is not always the answer.
This workshop will familiarize you with a technique
that reduces the amounts of testable combination drastically, while preserving
the expected levels of quality. Less effort, less budget, same quality.
When you take a deep dive into the wondrous world of test documentation, you encounter a lot of ideas about when software is good enough are incorrect. Either we don’t reach the described quality level, or we put the software in production, no matter what. In short: our quality expectations are too high!
Are there other ways of thinking about quality? One thing is certain: our vision (as testers) on quality is different than the vision of most people. If we cannot change that, testing will remain to be seen as the main bottleneck in software development.