Joy of small things in life. Thank you photography



Leave a comment

August 10, 2015 · 9:48 pm

Photography help people to see.


Leave a comment

August 9, 2015 · 2:41 pm

Beneath your feet #Theo


In response to The Daily Post’s writing prompt: “Beneath Your Feet.”

Leave a comment

August 9, 2015 · 12:15 am

Benefits of saying ‘No’ , when you really want to say ‘No’

In the year 2000, I prepared for a presentation for the senior management of an organisation on information strategy planning. In order to impress the audience, I stuffed the presentation with ‘cut and paste’ jargons which even me, the presenter did not understand well. It was the last hurdle, before signing a big contract and the audience included the senior most stakeholders from the customer’s side. I started the presentation well, could manage most of the questions from the audience, and when everything was going as per the script, i walked backward and hit the podium, and it fell down with a big noise, along with my self confidence. After that I could not utter a single word, and the rest of the presentation looked totally alien to me, under pressure. We lost the mega order because of me. That was a great and the most expensive lesson I learned ever in my life, ‘Never present anything which You have not experienced either positively or negatively’, and that great lesson helped me to sail through the corporate consulting world, in a successful manner during the past decade.
Temptations are the acid test of your convictions. Yesterday I had a meeting with a multi national customer, who wants me to teach them project risk management and project financing. It is very tempting to say ‘Yes’ to this assignment. Even if I know these concepts, I have not practised them extensively. The financial package is tempting, so is the temptation to prepare another ‘cut and paste’ presentation. Just manage one more show, thats it. If I say ‘Yes’ to it, I may be able to manage it, and at the same time I will never get a standing ovation from the audience at the end of the show.
I do not want to start an assignment knowing that I will not be able to do well. So, I am saying ‘NO’ to it, and the benefits of that ‘NO’ are;
1) I know that I have a reputation to loose in the industry, and the risk of loosing that reputation is managed.
2) I will not be cheating myself by pretending enthusiasm about the concepts, I am not that enthusiastic.
3) Every failure pushes me into a bout of professional depression, and I take almost a month to get out it. Avoid it proactively.
4) That client may come back to me with another assignment in the area of my current strengths. A failure can shut the doors to that client forever.
5) It takes integrity for not repeating the mistakes..and I feel good about it.
6) My business partner feels bad about the lost business. He would have felt worser with a failed assignment.
7) I am walking my talk by advocating the power of failing fast, than failing at the last moment.
8) Better health
9) Better work life balance
10) More time to focus on the important things in life
Still at times I say ‘Yes’ when I really want to say ‘No’, and as an afterthought I say ‘No’. That is an improvement, which needs further improvement. I am thrilled.

Leave a comment

Filed under thoughts

Another weekend is here…


Leave a comment

Filed under Uncategorized

No one saves us but ourselves. No one can and no one may. We ourselves must walk the path. Buddha


Leave a comment

Filed under photography, quotes, thoughts

Advantage Agile

If you have to highlight one best advantage of agile to the development team member, what is that?. That was a wonderful question that made me think for a while before answering. It is the freedom of the engineer to choose the work he/she wants to do.

In self organizing teams, there is nobody to allocate work, the team members have to choose it by themselves. That is a great opportunity for the engineer to liberate herself from the clutches of the positive or negative halos, perceptions formed in teams where work allocation exists based on the manager’s judgment of the potential of team members.  Even for good managers, it takes a great deal of professionalism to give everyone equal opportunity to restart their career without any biases after the performance appraisals. People get perceived as performers and non performers, and this reflects in the work allocation and has a cascading effect.

Many traditional managers believe that excellence is linked to experience. They think that experienced people must handle complex work.  Excellence is never linked to experience. In a fast changing world, sometimes experience is a burden. In a society which thrives on Matha (Mother), Pitha (Father), Guru (Teacher), Boss Daivam (God); it takes a paradigm shift to thrash the myth that excellence is linked to experience. Agile provides the opportunity for people with potential to demonstrate their mettle to the rest of the world by grabbing these complex work and completing them successfully. In the agile world, stars are born in no time. It does not take years for a star to surface. Even a sprint/iteration can create champions. At least every sprint adds to the reputation of the contributor based on sheer performance.

What are the advantages of agile to engineers?

In teams where work is allocated by the boss, based on the perceived capabilities of the team members, the tendency to cast the members to specific types of work is higher. ‘I know who can do this’ is something we hear everyday in the corporate world. That is okay, if one does not reach the extent of  believing  that others in the team cannot do it. Take it from me, perceptions are very often very wrong. On day 1 of my agile workshops, I tend to form opinions about each participant based on their interaction, dressing etc. At the fag end of the training, I am terribly wrong. Participants surprises me, and that is the best positive kick I get out of my work as a coach. In fact I am waiting for these moments, and the agile way of working have amble opportunities for these kind of surprises, that keeps me moving forward professionally. Agile is the opportunity for people with potential. Since it is highly empirical, the room for error in judgment based on  perceptions is minimal. Grab it, dear engineer, else till you retire others will be telling you what to do and how to do it. Liberate yourself. Agile is the opportunity.

Have a nice weekend.



Filed under agile, management

We are shaped by our thoughts; we become what we think. When the mind is pure, joy follows like a shadow that never leaves. Buddha


Leave a comment

Filed under photography, quotes, thoughts

Start by doing what’s necessary; then do what’s possible; and suddenly you are doing the impossible. Francis of Assisi


Leave a comment

Filed under photography, quotes, thoughts

10 points for those who are transitioning from project to product environments

Here are 10 key points to help those who are transitioning from projects to products

1) In projects, we deliver to one client, where as products get delivered to a market segment.

2) Inorder to build great products, we need people of the highest technical capabilities, where as in projects, the technical capabilities of people may not be the highest. This difference is very clear when we compare product companies to project delivery organizations.

3) Product teams, very often have to deal with millions of lines of legacy code, if they are working in very large established products. In startups, the challenges are different.

4)  In project based organizations, very often the teams may be following waterfall model for software development, where as most of the product companies have either transitioned or transitioning to agile.

5) In waterfall models, the predominant managerial style is command and control, and at the same time the desired managerial style in product based organizations is that of a servant leader. Some product companies promote ‘manager as a host’ styles, where everyone else is trated as a guest, and the manager ensures that they are comfortable. A variant of servant leadership.

6) Since the quality of engineering talent is the best in product companies, it is absurd to tell tell them how to do things. Explain the scope of work, and give them the freedom to choose the best approach to accomplish it. It is a kind of leading from behind, whereas in project based organizations, the predominant style is leading from the front.

7) In product companies, the requirements evolve over a peiod of time. Requirements are allowed to grow. In project based organizations, the focus is on freezing the requirements.

8) In majority of the product based organizations, test automation is in a higly matured state. Without test automation it is very difficult to achieve the desired quality levels, especially with voluminous code base.

9) In project based organizations, it is very difficult to justify the investment on test automation, becuase projects are unique and very often sigle time assignments. The predominant testing style is manual testing.

10) In product teams, the manager is only as good as his team. In project based organizations, the managers tend to position them as better than the rest.

Leave a comment

Filed under management