Wednesday, December 7 – cold. cold cold cold. Overcast. Did I mention cold?
Good thing we’re still inside the Dorint Sansoucci in Potsdam.
Last night’s award dinner and party was a tremendous success. The winners of the Software Testing World Cup were announced (see yesterday’s blog post for that.) What ELSE was announced was the Most Influential Agile Testing Professional Person (MIATPP).
The winner of the 2017 MIATPP was Maaret Pyhäjärvi (@maaretp)! Terribly pleased with this announcement. Congratulations to Maaret! Well deserved.
This morning Michael Sutton is warming people up for the first keynote of the day. This will be Diana Larsen (tweets at @dianaofportland) whose topic is Liftoff: Start and Sustain Successful Agile Teams.
That creates value for the business;
In a timeframe that fits the customers’ needs;
Easily maintainable and supportable;
Leaves the team members with increased capability and eager to work on the next deliverables.
What DIFFERENCES will show up?
Do it for real – learn by doing it. Keep people interested by having them do the work and learn to master the real work! Exercises are OK to start, but get to the real deal QUICKLY!
Team Mission (what is the nature of the work that will need to be done to make that happen?)
Mission Tests (examine and TEST the mission – then write some tests that will help us measure and engage in the tasks at hand? Are we on track?
Core Team – why have people been engaged to be part of this team?
Working Agreement – stuff like, “What is DOD?” “What are our core hours?” “How many meetings will we have & how frequently?” – Stuff that actually guides the work.
And we’re over time!
Break now – then I present!
When was the last time you read something and said “This is precisely what needs to be said on this topic”?It happens occasionally, but it’s rare enough. And since I’m a bit busy and not getting to write new posts (hopefully I’ll get to it soon), the l…
Tuesday, December 6 dawned cold. No, really cold. I’m from Michigan, this was cold. Snowing and still bright. Good thing I’m inside.The morning started with a lean coffee session hosted by Lisa Crispin and Janet Gregory. There was a good turnout and re…
December 5, 2016 dawned cold, a little foggy after very heavy fog day night before, and with a beautiful hoarfrost coating the trees. I had a very long travel day yesterday which resulted in me showing up nearly 2 hours late to the conference center an…
TL;DR This post is about simple bash shell scripts that finds all files that use particular method. In my previous post: Product moving parts as source for test strategy, I described how I use github pull request in order to discover which part of application changed in order to create regression test strategy. Code that … Continue reading Search in project for method usage using only bash script →
Many, many years ago I went to college and graduated as a teacher. I was going to say “became a teacher” but that would be wrong. College gives you a level of preparation to become a teacher but you don’t actually become one until you spend time in the classroom developing the requisite skills and … Continue reading Building Bridges
Once you start to have a larger number of tests it can be important to be able to break them down into different categories or groupings. From a functionality perspective this allows you to only run a subset of tests. They can also help to provide clarity or insight to your test code, by replacing … [Read more…]
A few weeks ago I put out an appeal for resources for testers who are pulled into live support situations:
Looking for blogs, books, videos or other advice for testers pulled into real-time customer support, e.g. helping diagnose issues #testing
— James Thomas (@qahiccupps) October 28, 2016
One suggestion I received was The Mom Test by Rob Fitzpatrick, a book intended to help entrepreneurs or sales folk to efficiently validate ideas by engagement with an appropriate target market segment. And perhaps that doesn’t sound directly relevant to testers?
But it’s front-loaded with advice for framing information-gathering questions in a way which attempts not to bias the the answers (“This book is specifically about how to properly talk to customers and learn from them”). And that might be, right?
The conceit of the name, I’m pleased to say, is not that mums are stupid and have to be talked down to. Rather, the insight is that “Your mom will lie to you the most (just ‘cuz she loves you)” but, in fact, if you frame your questions the wrong way, pretty much anyone will lie to you and the result of your conversation will be non-data, non-committal, and non-actionable. So, if you can find ways to ask your mum questions that she finds it easy to be truthful about, the same techniques should work with others.
The content is readable, and seems reasonable, and feels like real life informed it. The advice is – hurrah! – not in the form of some arbitrary number of magic steps to enlightenment, but examples, summarised as rules of thumb. Here’s a few of the latter that I found relevant to customer support engagements, with a bit of commentary:
- Opinions are worthless … go for data instead
- You’re shooting blind until you understand their goals … or their idea of what the problem is
- Watching someone do a task will show you where the problems and inefficiencies really are, not where the customer thinks they are … again, understand the real problem, gather real data
- People want to help you. Give them an excuse to do so … offer opportunities for the customer to talk; and then listen to them
- The more you’re talking, the worse you’re doing … again, listen
Wikipedia’s article on equivalence class partitioning (ECP) is a great example of the poor thinking and teaching and writing that often passes for wisdom in the testing field. It’s narrow and misleading, serving to imply that testing is some little … Continue reading →
The Problem Early last month I was trying to update some gems on my MBP and ran into an SSL error: ERROR: While executing gem … (Gem::RemoteFetcher::FetchError) SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (https://api.rubygems.org/specs.4.8.gz) In typical fashion I ignored the error and tried updating RubyGems (the package manager). That failed […]