Please enable JavaScript.
Coggle requires JavaScript to display documents.
Agile Testing Days 2018 (Collaboration (PICKLE (Participate, Innovate,…
Agile Testing Days 2018
Mood/Athmosphere/vibe
have more fun in dailies
Take care of yourself
Take brakes
Be aware of your cognitive biases
Confirmation bias: supports existing view, ignores contradictions
Anchoring bias: Too much value on first information
Conformity bias: Asch experimten (everyone raises hand, so will you)
Availability bias: if answers already exist we don't seek new information
Train your cognitive skills
Enigmas
Riddles
Point and Click Video Games
Escape Games
Collaboration
improve connections
Trust
Believe
Listen
Engage people early on
Communicate clearly
Involve Stakeholders more
Ask the right questions
PICKLE
Participate
Innovate
Communicate
Knowledge
Listen
Evolve
Share
Pull instead of Push
Drive change
Build internal agile capabilities
make clear what kind of change you seek
Every change starts with awareness and willingness to take action! YOU make change happen
Get organized and find allies and change influencers and Agile Champions in your company
Sponsors: They open doors
Coaches: Help to set goals
Teachers: Give Instructions and informations to learn
Rolemodels: Inspire
Help senior management
Avoid poor Engineering practices
Poor Story Splitting/Creation
Slow Recovery from Failure
Blouted Process
Poor/Ignored Feedback Loops
Poor Monitoring
Lack of Callaboration
Test Environment Setup
Build Times
Make Quality visible to stakeholders
measure the right things, measure value
Emphasis for Metrics should be on learning. Have simple metrics
How happy are you with current release
Strengthen Release Planning: A strategy on how to aim to release on time
Have an overall strategy plan
3 questions of release planning
What problem should be solved and what is considered successs? Have the end in mind. Outcome > output
What are the risks?
What is my next assumption to validate?
Prioritize! Not just feautures
build value / risk chart for different stories. cut low value high risk
Quality is the headlight of the project
Testing = Headlights
Quality = journey
Business Outcome = Destination
determine Qualtalability: how easy or hard is it to measure quality at any time?
Improve Skills
it's ok to stay in comfort zone for a while
don't go to panic zone, learning happens in learning zone
Automation
Understand Needs
Test strategy by TEAM!
Consider different levels of testing
Reduce E2E tests (ice-cream cone)