Imagine it’s your first day at a new school and you are asked to join the basketball team as their captain and coach. Everyone is playing along nicely when you show up, the new kid. You have been playing basketball for some time but you never had any decision making position before. And now here you are, trying to figure out how to help the team score more hoops and keep the fans happy.
This is more or less how my first weeks as product owner felt like. I have been in software development for 10 years now, but never in the PO role. Our product is relatively new but being developed by an established team, in other words it is already in good hands. So, to be useful both for my team and product I realised that I needed to come to terms with some challenges.
Read More »
Collaborative testing practices that occur continuously, from inception to delivery and beyond, supporting frequent delivery of value for our customers. Testing activities focus on building quality into the product, using fast feedback loops to validate our understanding. The practices strengthen and support the idea of whole-team responsibility for quality.
This is the authors’ definition of Agile Testing. To me, the biggest differentiator from other testing definitions is that this one promotes to actively improve quality rather than only inform on the status of quality.
When the whole team is responsible for quality of the product as well as quality of the process, each team member needs to be proactive in solving problems.
Quality coaches might educate, prepare or motivate team members to become proactive.
There are many things to consider around your product domain. It is not only the software you are testing; it is the product that your end users depend on.
I find this advice needs to hold true for anyone working in software development.
Read More »