Sunday, August 23, 2009

How to add Value

As I said in my last post the essence of value is not the WHAT part but the HOW part. I also promised that I will also provide some thoughts on how to add value especially if you are like me; working in an organization whose business is software solutions.

There are 2 questions to answer from the previous post.

1) How to add Value to one's own organization?
2) How to add Value to one's customer's organization?

Instead of directly answering those questions I will narrate instances from real projects and share my ideas thereof on adding value.

1) Identify areas of automation and implement them the moment you spot it.

I was talking to the project manager after a design review of a model and conveyed that there is a potential chance of human errors as the traceability(to requirements) is being maintained manually. He responded saying that the team is really good and they have never had problems with that. He also added that the customer understands the pain and is OK with the additional efforts being spent. As a matter of fact, I too felt that the team was diligent. In fact during my detailed offline review later, i really could not find a flaw with the traceability or missing link.

However there was a clear case for automation of traceability management. Not only would it have reduced the efforts spent in traceability management, but it would have been far more effective as its independent of human errors. Not to mention the possibility of easily finding broken links. It does require some upfront effort ( a.k.a investment), but it pays off in the medium to longer term. I told the PM about this possibility and he said he was not aware that it is possible. From the PM's as well as customer's standpoint everything is fine as-is. But in this situation, i would really have wanted the PM to ask a question to everybody that he can talk to - What all things can i automate in my project?

Anyway coming back to the point - How could automation have added value here ? In the following way..



So that did add value to the customer in terms of cost savings isn't it ? But you may argue that its a loss of revenue to your own organization. Right? Not really! In fact its quite the opposite. And that's for the following two reasons -

1) Technically, it was never your money. The customer could have some day found the clue of automation and he/she could have demanded it from you and you would also be painfully reminded that you were the software experts and are expected to be aware of this! So by proactively doing what could come to you at a later stage, you are proving that indeed you are software experts. And that means winning the trust of the customer which could turn out ( and it usually does) to be a much big revenue earner for you !.

2) By automating some mundane task, you have relinquished one or more human minds!( I prefer mind over brain, btw). Without automation, they were busy doing chores that did not really involve their mind, at least to some extent. With automation, they are now free to focus on more interesting things. And that is what paves way for Innovation. What better value could you ask for?

2.1) Perhaps the project can be executed with fewer people. One less person means less spending which is directly Value in a fixed price project.

I guess with that I have answered both the question at least from the stand point of automation. Lastly, I would like to emphasize on the part 'implement them the moment you spot it'.
Often times, we do spot automation opportunities. However seldom we implement then for some reason or the other. The more you delay, the more are the chances that it will never happen(Not to mention, you would be eating part of your pay back as well). To me, this is one of the key challenges for a Project Manager to not only manage THE project, but also these helper projects that aid in the main project.

I am going to end this post here. I did a quick retrospective and I feel that one idea per post looks much better than packing all the ideas in one . Keep reading and sharing your valuable comments.

Monday, August 17, 2009

The real essence of Value

How often do you get to hear the word 'Value'. I get to hear it a lot. especially as the phrase 'value add' because of the recent recessionary times; sometimes as a quip - 'There is no value add' or sometimes a question - 'Whats the value add?' What bothers me is the way the phrase is used. I get the impression that 'value' is being perceived in the qualitative sense of deliverables; as if to make them more refined or polished. as if it does not have any form and is far off. (side note: I am deliberately avoiding the word - intangible).

Teams keep themselves busy with what they see as tangible deliverables. This includes code, models, specifications, artifacts and of course defects. Even project managers tend to focus on schedule, effort, their variance, change requests and what not. I can usually sense the feeling across multiple projects - Lets first address the normal stuff ( basically get a good Customer Satisfaction a.k.a CSAT) then address the 'value' part ( which is polishing, the way i see it ). I am not against the polishing, but what concerns me is the corroboration of Value to polishing.

Lets first establish what 'Value' is. The word 'Value' is actually a part of the phrase 'Shareholder's Value'. And what is that - Its the share of the profit that a business organization makes kept for sharing with its stakeholders. In simple terms

Value = (Income - Expense
)

In other words, its the most tangible and far reaching deliverable. That it is not counted as a standard deliverable is a different matter ( I will come to that in a moment). Given this, for an organization whose business is providing software solution, the implications are two fold.

1) To add Value to their organization
2) To add Value to their customer's organization.

And perhaps #2 comes first.

So why is Value not counted as a a standard deliverable? Because its not a question of WHAT but a question of HOW that determines value addition and that I believe is the real essence of value. Its not WHAT you are doing or chasing (a.k.a code, models, specs artifacts etc.) . Its HOW you are doing( and sometimes not doing too!) or chasing.

Now you may be wondering.. How in my opinion one should add value? Well, then watch out for my next post where I would like to share my ideas on how to add value for your organization as well as your customer's organization.

And oh.. btw, if you have any thoughts on adding value or simply have a comment, please feel free to post.

Wednesday, May 27, 2009

The sense of belongingness and belongedness

I think its well known that a good organization and a good business requires good resources. And when it comes to Software engineering, needless to say, people resources are the key. The better the quality of the human resources, the higher the likelihood of a better balance sheet ;-)

So here is some food for thought on how to make not just good but great organizations - I have observed this behavior in many teams, so much so that I can call it a pattern - The Sense of belongingness and belongedness. And I believe it is scalable too as organization is nothing but a group of teams all working towards a common goal.

A team member needs to have a Sense of belongingness for the team. I.e. he needs to believe that he owns a share in the team. Now, would you throw mud on your own carpet? No, because you own the carpet. period. [BTW if you said YES, then I wonder how you cleaned it the last time.] In the same way a team member needs to impartially own the team, show commitment to the team's goal whatever it may be. Suppose you are playing as the center forward in a soccer match, will you kick the ball in your own goal post if you did not like the team strategy?

Every action has equal and opposite reaction[No pun intended]. A team member should also have a Sense of belongedness from the team. Now what does that mean. Taking the previous soccer example, suppose you did kick the ball into your own goal post, the team does not refrain from playing you in the next match! Now that's what is belongedness. A clear message from the team that 'You belong to the team' and they are with you even when the going is rough.

I have observed that when both the senses are profound, teams tend to make a mockery of the difficult of goals. When there is lack of any one of them teams tend to flounder a lot from the goals.

Belongedness comes from faith of an individual on the team and the trust of the team on the member. i.e. its mutual. Perhaps that why organizations try to keep their employees in the best of their spirits( they call it motivating!). What I have not seen organizations do much about is to inculcate the 'Sense of Belongingness' which is the solid foundation on which belongedness rests.

So next time if you are taking a decision try this - For a moment put yourself in the place of the owner of the organization and set a premise that if you take a wrong decision, its going to lead to a loss(monetary or otherwise). Ask yourself - What do I feel in my gut?

Wednesday, May 20, 2009

What is Thought Manageering ?

I am sure you may have guessed about Manageering. Its a cross between Management and Engineering. Management is the act of utilizing resources to acheive a specific purpose. Engineering is the application principles of mathematics and science to build something that is tangible .

Fortunately for all of us in the Information Technology stream, we are a bit of an Engineer as well as a Manager. We have a common project goal and we also have individual task goals. We engineer and we self-manage. And it happens at all levels.

If you thought that a Coder does not do m, take a look at PSP (Personal Software Process). There is no other stream where this happens so pre-dominantly and at all levels other than IT.

From a manager’s perspective, unlike other fields, its not simply management of resources. Its much more than that. In other industries, you don’t have to motivate all of your resources because most of them you deal with are machines. Not in Software Engineering. You deal with people.

It does not end there. As things are becoming more competitive, in any organization, right from the root level to the highest position, ‘enhancing or adding value’ is a common goal. This, if not present, needs to be imbibed in each and every person in the organization.

And how do managers do that – They apply mathematical principles, use tools (does Excel, Six Sigma ring a bell ?) and they have a practical goal in hand to build a solution. Guess what, that’s fundamentally Engineering.

So what is Thought Manageering ?

Its applying thought in manageering. Or in other words, applying common sense and what occurs naturally to us in our work. Its as simple as that.

So I welcome you all into this fraternity of Thought Manageers !