Due to various reasons, it had been a long time that I had attended the Lean Coffee mornings at Cambridge. I was so glad I could make it this time! Lean Coffee was hosted by @
As usual, there were thought provoking discussions some of which I would like to share in this post.
How much pairing/swarming is efficient?
There are several studies that state that it is efficient to pair/swarm to get a story completed in an Agile team. The discussion was about how much pairing is efficient.
In the Scrum team I work, we have found pairing to be helpful during the second iteration of development i.e. bug fixes rather than working on a story together right from the start. Note that Sprint planning is done together as a team.
In our Lean Coffee group we discussed about
- efficiency depending on the kind of people involved in pairing.
- the need to find out what works for your team – some people don’t like to pair during development, introverts don’t like swarming.
- involving testers early on in the development.
- creating your own metrics for measuring efficiency keeping into consideration how to measure over short and long periods.
Strategy documentation in an agile era
Detailed documentation is still created by Companies for their partners and the discussion about its requirement has been a controversial topic to many!
The discussion by the group was around the following areas:
- Is it really a waste of time or is it useful since you get feedback on areas not tested/considered to be tested by partners?
- Documentation can get out of date as soon as its published.
- Possibility of having a wiki doc which can be constantly updated.
Improving tester/personal efficiency
There were 2 different topics in this area which I am combining into one since the discussions weren’t clearly differentiated. The topics were about the themes – how can I as a tester get more efficient? How can I personally get more efficient at work?
- How to measure efficiency – we need a metric of our own
- End of the day we should not have a feeling of ‘didn’t get anything done’
- Are there ways of saying no or taking lesser tasks?
- Reading emails at different points of the day
- Planning next day’s work the day before
- Personal Kanban
- Self retrospectives
- block tasks in the calendar
- Get fresh pair of eyes to check test strategy – mind map sharing
- invite POs – usability
- get help from developers
Performance testing tools for video testing
- No one in the team had experience with this but it was suggested that people in the industry could offer help.
If any of you reading this post have suggestions about good tools to use, please do drop a comment.