Experience Report Provided by: Kristjan Uba
Date: 16-18 March, 2012
Location: Tallinn, Estonia
PEST2 = 9 peers from 6 companies for 2 days with infinite amount of good ideas.
Not counting the beers and fun.
The conference theme was “Taking one for the team.”
Ideas discussed at this peer conference include: fighting boredom, understanding your team and knowing your team members. Other topics covered were: dealing with situations when you’re forced to use certain tools, ideas to keep your team motivated (and what makes them unmotivated), as well as thoughts for team leads to keep your team healthy.
Details about the event:
March 16th, 19:33, Local Pub.
Seemed like just another Friday evening, unless you examined closely. The air was full of witty banter, challenges and yet unsolved puzzles. A good start for a peer conference.
March 17th, 09:27, Conference room.
Cluttering of tea and coffee mugs faded away. Check-in had started. Now it was time for action.
Given the main theme, “Taking one for the team,” the experience reports and discussions evolved around test teams. Teams: working in one, managing one or creating one. The following questions started the open season (links below navigate to blog posts containing the summary of our answers):
- How does your team fight boredom? (If you are one-man-army then how do you fight boredom)
- What makes your team tick? (if you are one-man-army then what would make a team tick)
- Who are the key members of a team?
The content owner, Kristjan Uba, drove most of the threads to fit the general theme, but some were just too interesting to rat-hole. And few so interesting that coffee breaks were extended to let people talk about them.
The open season was facilitated by Oliver Vilson. He kept us all in order when one thread was being divided into 3 new ones and everyone wanted to speak at the same time.
March 18th, 15:54.
Checkout is finishing. People are getting into starting positions to race for the cake. Oliver uses distraction to get the lead, by shouting “PEST3 is already being prepared, be ready in October!”
Six of PEST2 highlights in no particular order. Some of the very good ideas were too big to fit into highlights and can be read from blog posts on the web.
When you are being ordered to use a tool (in a certain way) then the best way to fight against it – is not to fight (at first):
- Instead, learn it. Find out what it can do. And what it can’t do.
- Investigate, if it can used in a way that would fit your process.
- Then you can support your fight against it with good evidence.
- If you start off with great hostility you will be flagged as troublemaker, whiner, and you will not be taken seriously.
Motivation – has both absolute and relative scale (for each person):
- It is relative to previous value for that person in regard of time.
- It has absolute value to that person (high to low).
Eliminating human interactions as much as possible is apparently very good for highly specialized, after development, code testing for highly critical back-end core system maintenance.
People/teams are most often unmotivated by confusion, try to answer the following:
- So what exactly are we going to do?
- What is the goal of our work?
- How exactly is that useful?
- What resources are we going to have/need for this project?
- How long are we going to go on with this?
If you want to know you have been understood, summarize it incorrectly and see if they point it out.
If not, then you know they did not get it, or are too shy to show you made a mistake. Either way
there is more coaching to do.
Team-leads, to have a healthy team (more about this in web):
- Share boring tasks equally over all members.
- Have a Bug Chase Competition from time-to-time:
- “Be the first to find a reproducing sequence for specific intermittent bug.”
- after 30 minutes, no-one wins. Back to work.
- Remember that you are not “number 1“ in the team, but there to help the team forward. You back them up and defend from external troubles.
Official List of Participants
- Oliver Vilson (Facilitator)
- Kristjan Uba (Content owner)
- Rasmus Koorits
- Ervin Hülp
- Helena Jeret-Mäe
- Raimond Sinivee
- Aare Nurm
- Ülar Aasmäe
- Harles Paesüld
Supporting participant (could not be present at PEST2):
- Aire Kurgpõld
Your Blog Here
Did you pass Foundations? Join us for the next course in our series. Bug reports are not just neutral technical reports. Learn how to write a persuasive bug report that provides high-quality information, is well written, and helps stakeholders make wise decisions about which bugs to fix.
Online Education for Testing Practitioners
Learn more »
Theme The theme for CAST 2014 is “The Art and Science of Testing.” In some contexts and by some people Software Testing is considered to be more of a science and by others more of an art. To some, it’s an outgrowth of computer science, mathematics and physics. To others, it’s an expression of soft [...]
Skilled testers look at testing in a different way every time they need to execute a test. In this video Paul Holland discusses the difference between a skilled tester and a non-skilled tester. Are you a skilled tester?
By: Peter Walen (Twitter/Blog) Test Leadership Camp an open space meeting organized by the LeadershipSIG of AST, held the Thursday after CAST. One of the topics discussed was a fundamental concept, “What is Leadership?” The discussion was wide-ranging and covered a variety of topics. The primary points under discussion involved a variety of topics around [...]
- PNSQC 2014 - PNSQC on CAST 2014 (Aug 11-13)
- Star CAST 2014 - PNSQC on CAST 2014 (Aug 11-13)
- CAST 2014: Theme & CFP on Call for Participation [OPEN]
- Elias Nogueira – Bug ou Feature? Pagamento de Fatura no Itau Internet Bank on “Emerging Topics” Track
- Taking a Break – What taking time off from pretty much everything can do for/to you/me | Sowing Seeds on CAST 2014 (Aug 11-13)
- December 2013 (9)
- November 2013 (37)
- October 2013 (60)
- September 2013 (64)
- August 2013 (95)
- July 2013 (74)
- June 2013 (57)
- May 2013 (52)
- April 2013 (63)
- March 2013 (70)
- February 2013 (77)
- January 2013 (87)
- December 2012 (46)
- November 2012 (51)
- October 2012 (62)
- September 2012 (53)
- August 2012 (42)
- July 2012 (54)
- June 2012 (33)
- May 2012 (44)
- April 2012 (62)
- March 2012 (95)
- February 2012 (60)
- January 2012 (80)
- December 2011 (98)
- November 2011 (83)
- October 2011 (137)
- September 2011 (44)
- August 2011 (61)
- July 2011 (61)
- June 2011 (66)
- May 2011 (60)
- April 2011 (62)
- March 2011 (41)
- February 2011 (36)
- January 2011 (70)
- December 2010 (77)
- November 2010 (56)
- October 2010 (46)
- September 2010 (26)
- August 2010 (23)
- July 2010 (18)
- June 2010 (27)
- May 2010 (40)
- April 2010 (31)
- March 2010 (30)
- February 2010 (3)
- January 2010 (11)
- December 2009 (17)
- November 2009 (19)
- October 2009 (11)
- September 2009 (19)
- August 2009 (16)
- July 2009 (11)
- June 2009 (28)
- May 2009 (5)
- April 2009 (11)
- March 2009 (5)
- January 2009 (1)
- December 2008 (4)
- November 2008 (2)
- October 2008 (1)
- August 2008 (4)
- July 2008 (3)
- May 2008 (1)
- A big thanks to @mheusser @erikld and @simonsaysnomore for organizing #WHOSE2013 about 10 hours ago ReplyRetweetFavorite
- #WHOSE2013 Day 2. A big thanks to @HylandSoftware for providing the meeting space for this event. about 12 hours ago ReplyRetweetFavorite
- #WHOSE2013 starts tomorrow, we are looking forward to what they come up with. http://t.co/ZQCL95jLeg 07:19:16 PM December 04, 2013 ReplyRetweetFavorite
- Need inspiration for your #CAST2014 proposal? Check out past conference talks. http://t.co/7fbHqlHfTr 04:50:47 PM December 04, 2013 ReplyRetweetFavorite
- First CFP submission for #CAST2014 has been received. Are you next? http://t.co/x7lPH5QskV 02:56:48 PM December 04, 2013 ReplyRetweetFavorite