Thursday, May 17, 2012

Subscribe to the RSS Feed

Agile Testing Days 2011: DAY 1 - What a fabulous Day!

Posted by jc-Qualitystreet on 2011/11/19

The Agile Testing Days (Nov 14-17 2011) is the annual European conference for and by international professionals involved in the agile world. As the French Ambassador of the conference  taking place this year in Potsdam (near Berlin), I couldn’t miss it. So, second participation, high expectations and absolutely NO DECEPTION!

This first day was I think my best conference day ever! So thanks to Jose Diaz, and his team, thanks to the speakers and participants.

After a very good full-day tutorial given by Jurgen Appelo (”Agile management: Leading Software professionals”…. a course that I do recommend in a 2 day format to all managers) and a dozen of games/exercises to try “At Home”…

Jurgne Tutorial.. Metrics Matrix to try

Jurgne Tutorial.. Metrics Matrix to try

the conference Day 1 opened with Johanna Rothman’s keynote…

Johanna Rothman “Agile testers and test managers: Now what?”

This keynote was the first of an impressive set of amazing presentations

Agile management is a hot topic to me since I do more and more agile coaching with line managers. I’ve explored the domain and of course already read Johanna’s books and articles. However, I found this “testing oriented” presentation very valuable.

Agile Test Managers Keynote

Agile Test Managers Keynote

Johanna first discussed the changing role of the testers in the agile organization. The agile tester looks like the First Class Tester (she previously described in 2003), as they, for example, work with developers from the very start of a feature…

“Testers ask questions… are curious”

The second part of the talk was dedicated to Agile Test managers…

“Agile test managers are leaders in the organization”

The key activities:

  • Manage the project portfolio
  • Remove organization obstacles
  • Build trust relationships
  • Lead hiring decisions and process
  • Build the capacity of the organization
  • Build communities of practice

Interesting thoughts

“Have management iterations” (To try!)

“Allow managers to see the system”

“Instead of individual reviews build a trusting relationships share the strategy share the profits”

“What keeps people in job? Trust”

“No micromanagement meet often one on one to build a trusting relastionship”

David Evans “What testers and developers can learn from each other?”

The presentation was efficient and David, as a good speaker, made a good use of analogies:

“Thinking you can improve quality by doing more testing is like thinking you can loose weight by weighing yourself more”

Analogy

An effective analogy

With ease, David focused both on things developers can help testers learn and things testers can help developers learn for the benefit of the whole team. The parallel was interesting. After pointing out ironically that ISTQB certification is mostly useless, David discussed common issues like coverage and concluded with things we all need to learn:

How we learn - David Evans

How we learn - David Evans

“Testers are friends”

“Teams need testers like people need friends” (I like that one!)

Rob Lambert “Do agile teams have wider awareness fields?”

“Not always”

but Agility gives you an environment to be a first class tester added finally Rob.

A good presentation that Rob was able to make interactive. I appreciated.

Rob started by introducing the concept of awareness and distinguished social and personal awareness, which was useful.

“Awareness is the ability to feel, perceive, know and be conscious of yourself and the world around you”

Awareness

Awareness

Other interesting thoughts…

“Awareness is the first step to change…”

“You need to know yourself and you team”

“You need to know your limits”

I like very much the idea of Learning Roadmap (closed but maybe richer than my To Learn List).

Learning Roadmap: What a good idea!

Learning Roadmap: What a good idea!

And finally, Rob pointed out the grower importance of social media and social tools (like twitter) as modern ways of widening awareness. I can just agree :)

Linda Rising “Who do you Trust? Beware of your brain”

Last year, I didn’t notice it immediately but Linda’s keynote gave me inspiration for a year. This time, once again, she did the job, and I must admit that emotion was in the air (and in me) at the end of her speech! She is a fantastic storyteller!

Based on experiments coming from the social sciences field, Linda shows us how quickly we categorize others, how quickly we naturally stereotype and label other people…

“We continually sort others into groups and out-groups”

rising1

The bad thing is that stereotypes and their expectations are not only a source of conflicts but also can affect performance…

“Stereotypes are prophetic”

The good thing when we look at the results of social experiments is that Humans like to be in small groups and quickly develop identity, no matter countries, cultural dimensions or even religions…

“This is the good news we like collaboration”

This is what we call Social Interdependence. The benefits?

  • increased effort to achieve,
  • positive relationships,
  • improved psychological health…

And you know what? agile practices are practices that help. Therefore, sharing a common goal, as well as be trusted and respected are the keys.

“You don’t to be my best friend”

Linda ended her presentation with 2 good examples (”Trench warfare” and “primates”) showing reasons for hope and nothing is carved in the rock.

Happy Ending

Happy Ending

Huib Schoots “So you think you can test?”

This session wasn’t originally on the program. A good surprise!  Huib is an experienced and passionate tester.  His talk was dedicated to the factors that can help you to become a better tester. Huib listed three main activities:

  • Adapt to context (context driven testing…)

“There is no best practice”

  • Collaborate. Most of the job of the tester should be to ensure that the right testing is done (executing tests should be a small part of the activiy)
  • Learn & Practice. Huib pointed out a set of learning options (Books, conferences, testing dojos, week end testing, pair testing, collaborative workshops, peer workshops…)
Passion...

Passion...

“You should train and practice”

“Be passionate” (to me, PASSION makes THE DIFFERENCE)

and one of my favorite quotation of the #AgileTD:

If you want to do a good job I think you should invest in yourself

Be passionate

Be passionate as Huib is

And finally a good question, why don’t we have a Testing coach?

Gojko Adzic “Product Management using Effects Maps”

This session wasn’t originally on the program. A good surprise too!  Gojko presented the Effect mapping, a visualization tool invented by Mijo Balic and Ingrid Ottersten.

Effect mapping supports product management activity by focusing on business goals. It enables high level project visualization, helps to deliver software iteratively (starting by the fastest simple way), and reduces user stories management issues…

“People horribly misuse user stories”

“As a system, I want…  a system doesn’t want anything a system wants to sleep”

The starting point and the first level of the map is always the WHY (the business goal, how the business will be different 6 months from now if we achieve well).

Effect map

Effect map

Then, are drawn the next levels:

  • WHO (can contribute to the business goal)
  • HOW (can they help us)
  • WHAT (we can do as a team to support this activity)

Once the map created, deliver the simplest thing to deliver  (a path) and measure the effect (very similar to the Learn Startup approach introduced by Eric Ries…). IT should be seen as an investisment, not as a cost

The effect mapping, a tool to try…

Janet Gregory - Lisa Crispin “AppendixA: lessons learned since Agile testing was published”

We all know Lisa Crispin and Janet Gregory, authors of the famous Agile Testing book…

party2

Lisa Crispin... later at night, at the party and ready to announce the award for the most influential agile tester of the year... DO YOU BELIEVE IT?

For this keynote, Janet and Lisa decided to discuss 5 Hot topics related to agile testing:

1 Feature Acceptance

Working feature by feature makes you often forget the global picture: during her talk, Janet used the puzzle analogy and stressed the necessity to understand the business value of a feature to deal with this issue and help prioritization. Establishing story tests but also defining story doneness, feature doneness are crucial.

2 Automation

Collaborate to automate and overcome impossible challenges. In term of test strategy, Lisa and Janet reminded us that context is everything, and so that for example, the well-known test pyramid should be adapted to the specific needs of each organization. According to them, “tests as documentation” is the only documentation guaranteed to be up to date… (as long as they run green).

3 Large Organizations - large Teams

In the case of large organizations, Janet and Lisa pointed out the necessity to consider other teams.

Key challenges : Multiple Teams

Key challenges : Multiple Teams

“You need to extend your family beyond your project team”

I totally agree! (see devops movement)

4 Distributed Teams

The world changes, and today’s the business is more likely distributed. A fact that I can easily confirm doing some agile coaching in various situation like French/ French distributed sites,  French / Indian context or  French/US/ German context. For such a context, my opinion is that reducing the distance is the key… Lisa and Janet presented 3 practices to succeed: establishing relationship, taking advantage of the technology (the virtual team member…) and experimenting!

5 Culture & Continuous learning

Agile is all in learning. Yeap!!! According to Lisa and Janet, culture is even more important that we thought: personal safety and allow people to make mistakes are essential. Janet insisted also on the important role of Play in the learning process. An element I am also convinced…  as well as the necessity to be CURIOUS

gregory2

“I really encourage you to be curious and learn new things”

“I like to see testers to be curious”

The last part of the talk was “attendees” oriented! Janet and Lisa wanted to hear about the stories of the attendees (”the Agile Testing book”, “Testing dojos”, “Twitter”, “Tests & Feedback”…)

And Finally the Party to close the day

Some pictures of the funny party taking place in the evening (during when Gojko Adzic received the award for the most influential agile tester of the year). I enjoyed the show, the performers, the place, liked the beers and the discussions with the frenchies: Laurent, Gabriel, Patrice and Elalami…

party1

party3

So, MY ROTI (Return on time Invested) FOR THE DAY: 5

To Learn List… because learning is essential!

Posted by jc-Qualitystreet on 2011/11/15

… learning again and again!!!

A To learn List for the Team

A "To learn List" for the Team

Agility and learning are intimately linked.

Learning is a key dimension of Agility, a key component of an agile mindset, and a major Human characteristic. In parallel, Agility (with Scrum or XP for example) is a land where learning can really flourish:

  • Co-located and cross-functional teams are sought…
  • Cooperation and collaboration are facilitated…
  • learning situations (Release planning, Collaborative workshops and Product Backlog Refinement, Planning poker, Pair-Designing, Pair-programming, Retrospective, gaming…) are fostered…
  • knowledge sharing is expected…

they all are good examples and valuable opportunities for learning and improvement. But why not going further and giving to the le arning activity a good place on the Team Information radiator?

On the wall, you who already have your Taskboard, your Product Vision, your Product backlog, your Impediments List (obstacles), maybe the Personas for your Product and a Risk board.
Try now the “To Learn list” in order to monitor and enhance this essential activity.

The “To learn List” belongs to the information radiator. Continuously visible and accessible by anyone (management including…), it can be updated continuously even if the “Daily Scrum”, “After daily”, Collaborative workshops or Retrospective are excellent moments to do that.

Personally I have also adopted this “To learn List” at home and am very satisfied with it!

Just Be Curious, Try it!

Retrospective, Agility and Les Bleus: the French Rugby Team in action

Posted by jc-Qualitystreet on 2011/10/17

If France wins the world Cup next sunday, we’ll know why:)
The team handles the notes with dexterity, you can do IT!
So like them,

  • live your RETROSPECTIVE with real agile values
  • play Timeline

Thanks Jean-marc

And, ALLEZ LES BLEUS!!!

A Speed Boat or nothing…

Posted by jc-Qualitystreet on

Speed ​​Boat is one of the “Innovation games“, one of those games that, like Product Vision Box , Remember the future or Buy a feature, is very useful during our Agile and UX workshops.

Speedboat is an interactive, collective and funny way to identify constraints, obstacles, problems with our product or our project, then to prioritize actions in order to remove them!

Speed boat, a boat with many facets…

The advantage of the Speed ​​Boat metaphor is that the game can be very useful in a lot of contexts. Indeed, our boat is appropriate to represent our development project (which does not advance for some reason…), our product, subject to criticisms and comments of its users or the team in charge to bring agility to the organization.

Result of our Speedboat WorkShop ...The goal is the Agile Enterprise

Result of our Speedboat WorkShop ...The goal is the Agile Enterprise

The rules of the game

  • Draw a speed boat on a whiteboard or poster
  • The boat is our system, our product, our project or our team, so name it (Here, the boat is our Agile transition team)
  • Of course, the objective of the Speed ​​boat (our product…) is to go fast (for best performance). So I first ask the participants to describe us precisely what characterizes the optimal performance, the desirable conditions (yellow notes attached to the port or on the island that the boat needs to reach)
  • The boat position represents today and the distance between the boat and the island can be seen as an indicator (not in our case)
  • The anchors represent the obstacles slowing the movement of our boat: impediments or things that our customers or users do not like about our product and affect its optimal functioning. The more they are low under the water, the more they are strong (well, up to you to follow this rule!)
  • The green arrows represent positive elements that push our boat

Facilitation

Several variations exist. Here is mine

  • Steps 1 & 2 After the opening and introduction of the game, I usually ask participants to work individually or in pairs (depending on group size) on the goal (desirable conditions) and the positive factors then to present their work to others.
  • Step 3: Then, individually or in small groups it is time to characterize the anchors (obstacles, constraints, things we don’t like)
  • Step 4: The work done, I ask the participants to post their anchors on the wall.
  • Step 5:  Collective consolidation and anchors prioritization
  • Step 6: I usually close the game with an action plan to set up to remove the major anchors!

In short, we generally have a good time playing that game: enjoyable, useful but also very effective!

Agile and Lean Management: The AGILE MANAGER

Posted by jc-Qualitystreet on 2011/06/02

Here are the slides (English Version) of the presentation I gave last week at the agile France Conference to introduce Agile & Lean Management with a focus on the role of the Agile Manager: