Explore this topic further by using one of the tasks / questions below.
Go deeper
What could you measure? How might trends in that measurement help your decisions?
What pitfalls can you see? Write them down, then search to see if anyone has answers
Can it scale?
Would you include time spent setting up? Diagnosis time? Time spent logging a bug? How might this change your measures?
What would you do if you spent most of the session off-charter?
What would you do if you found a problem whch caused a high-impact failure? What if you found something that needed to be investigated as soon as possible?
What would you do if, halfway through a long test session, you had found nothing interesting at all
How would you go about making charters to help you stay focussed?
How would you go about making charters that helped you explore the breadth of behaviours of a system
How would you go about making charters that focussed on a very limited element of the system
Should the team come up with charters? One person? Only the person doing the testing? Anyone except the person doing the testing?
How might it be useful to do one charter twice?
What might you do with charters you haven't used?
Application to your work
Consider what you might manage, and what you might exclude from your measured time. Would your colleagues make the same choices?
What elements of your own work would be a good fit with SBTM
Would SBTM help you report your work? What else might be needed? Check your answers with whoever needs your reports.
What would be most useful about SBTM to you?
What would be hardest to implement about SBTM in your job?
Would SBTM help with talking to your auditors?
Further Reading
From the source: here is James and Jonathan Bach's page on Session-based testing.
My paper Adventures in Session-based Testing is a case study, won awards, but is now rather old...
Paul Carvalho's Lessons Learned in Session-Based Exploratory Testing.
Wikipedia article.
James Lyndsay, Workroom Productions
@workroomprds, +447904158752