My Experience at #AgileIndia2012 – Day 3.

by Sampath Prahalad

The third and final day of the Agile India 2012 conference being held at Le Meridean, Bangalore. The learning experience got better and reached a crescendo today.

Here are some of the talks and workshops that I attended. Some were excellent and some good.

  • Exploratory testing for Agile teams by Pradeep Soundararajan.
  • Launching a Minimum Viable Product in a month.
  • Coaching: Slowing down to speed up by Rahul Sawhney.
  • Lean: Reduce Waste Campaign by Belkis Vasquez-McCall from McInzie.
  • High Five Driven development by Peder Soholt from Norway
  • Agile Scaling model: Be as Agile as you need to be by Scott Ambler
  • Fun with Agile Gaming by Vibhu Srinivasan of SolutionsIQ.

Read on to know 3-4 key learning points from each of these talks / workshops.

Exploratory testing for Agile teams by Pradeep Soundararajan.

  • Exploratory testing, when done well, is with the understanding of context and starts with a mission. In Exploratory testing, a tester simultaneously tests, designs and learn. With Session Based Test Management, you could help managing many testers doing exploratory testing on a project.
  • Excellent quote: Application Software takes the shape of the container that it is put in. Works differently on Dev, QA, Staging and Customer environments.
  • Excellent quote: If someone says that they have cracked the puzzle of testing, STOP listening to them.
  • Get to know the customer/end user and his mannerisms better to be able to test better for them.

Coaching: Slowing down to speed up by Rahul Sawhney.

  • A coach should be 1 step away from the coachee and encourage him/her to step forward. Should not stay 10 steps away and force the coachee to jump.
  • A good coach is a Game master. He steers and co-ordinates the conversation.
  • A good coach does not provide answers, he asks the right questions. The coach should empathize. He should appreciate, not flatter.
  • Stretch goals motivate as long as they have the team’s consent and don’t stretch the team too much.

Launching a Minimum Viable Product in a month by Aakash Dharmadhikari and Jasim A Basheer of RubyMonk.com

The Gist of the talk

  • Set a deadline. This deadline has to be as real and immovable as possible.
  • Wireframes. Brainstorm on the wireframes. Spend at least 15-20% of time on it.
  • Extreme collaboration. Get all team members working out of a single room. The helps tremendously.
  • User feedback: Show it to as many people as possible in various phases. Capture feedback and address it.
  • Evolve your methodology. Don’t be stuck with any flavor or practice of Agile. Try a practice, evolve it and use it religiously.

Lean: Reduce Waste Campaign by Belkis Vasquez-McCall from McInzie.

  • Waste reduction is better than Recycling.
  • Examples of Waste: Unused features, defects that got into production, documents not referenced, processes and meetings that do not add value.
  • Reduce waste on Technology, Communication, Process and anything else.
  • Agile lets you write your own rules. Make the most if it.

Lightning Talk: High 5 Driven Development by Peder Soholt

  • Give a High 5 to anyone who does something positive.
  • A High 5 never fails to motivate because it is Super Easy, Fun and cool.

After 3 days at the conference, I am excited and energized from all the talks and discussions. Physically a little tired though.

All in all, I had a great time learning lots of stuff, meeting many cool people, some friends from my PMI-ACP group and many speakers that kept me spell bound.

I am ready for more and waiting to meet up with some folks from Agile India 2012 at Cafe’s and take some topics forward…

Advertisements

3 Responses to “My Experience at #AgileIndia2012 – Day 3.”

  1. @ Sampath,

    Thanks for the summary of the conference. You mentioned , “Exploratory testing is Exploring the Software without a context. It is not wandering though.” – which is not what I said but I understand that hand written notes sometimes is confusing to read after a couple of hours.

    Here is what it is – Exploratory testing, when done well, is with the understanding of context and starts with a mission. In Exploratory testing, a tester simultaneously tests, designs and learn. With Session Based Test Management, you could help managing many testers doing exploratory testing on a project.

    Could you please make the correction in the post as well?

Trackbacks

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: