Monday, September 1, 2008

Leaving Ariba...

Thank you and adieu
I wanted to take a moment to let you know that I am leaving Ariba today.

Transitioning from Ariba is an emotional decision, as I have enjoyed working at this company for many years. I have learned a great deal from my managers and many other leaders at Ariba. Ariba is a big part of my life and I will always cherish the fond memories of my years here. I am proud of what we have built together at IDC, and I am so optimistic about Ariba's future. Thank you all for the support, guidance, and encouragement you have provided me during my time at Ariba.

Please keep in touch, I can be reached at my personal email address baijuglad@yahoo.com . I am also in linkedin.

Thanks again to all of you, and I wish you continued success in the future.

Regards,
Baiju

Last weekly meeting with team
Today is my last week at Ariba. When I joined 5 years back we were just 6 member team owning 5-6 features and some of the automation. 2 years back we have started owning the Quality responsibility for the entire product set. Doing some innovations from India and getting it recognized in Ariba world wide was another big dream. We have proposed , prototyped and demonstrated Selenium as a tool for test automation. We have been working on this for an year and last March it got accepted as the common tool for Ariba world wide. I have learnt a lot on Scrum while working here. Learnt a lot in the Steering Committee meeting. Thanks to Ariba. Today while sitting in the farewell lunch I have been thinking about these. Its time for me to get down from the journey and catch another train.
We have Monday team meeting as usual. Today one of my parting message to team was to focus on testing to improve quality. This is the summary.
Disciplined Testing
  • Testing risky areas early
  • Change in code is risk – so test around the change immediately
  • Focus on where customers are reporting more defects
  • Communicate to your developers and appropriate internal customers regularly
  • Test status
  • Defects – go and show the defect if it’s a blocker to your scrum team
  • Write your defect reports with enough details and follow the best practices
  • Analyse the defects little more in detail – product log
  • Understand why is it not working – need to know the feature block diagram