Showing posts with label Professional. Show all posts
Showing posts with label Professional. Show all posts

Thursday, May 29, 2008

Sometimes even small things suck!

You can only sip from a cup full of tea but sometimes a cup full of tea can suck also. If you are leading a team and people look upon you as their lead, then even small things can matter sometimes. For ex. what will you think if the leader of the team is served with a cup of tea and then after 10 minutes tea for everyone follows? It is mere symbolic but in one way reflects the personality.

Tuesday, May 13, 2008

He will still be an employee!

A casual discussion between friends and what better topic than the currently going on IPL. The conversation slowly went into King XI and Team Mohali and their owner Preity / Ness. The majority believed that Preity was slowly getting closer to Yuvraj (we all have opinions and what better topic to have opinions on than something which combines cricket with entertainment). With all the hugs she gives him after every match and it being highlighted in different newspapers everyday, it only made sense. And of course, Yuvraj would earn and get closer to Ness in coming years. But suddenly someone from somewhere in the coversation came out with this:

At the end of the day, he will still be an employee!

Monday, February 18, 2008

Taking Interviews - Part II

In my last blog on Taking Interviews, I had written about few parameters that I use to test out different things in the candidate. In an update, I am sharing a few more new learnings I have had in the past few days:

Stupidity Handling Quotient: Anyone and everyone in this world has been stupid at one time or the other. It becomes very important for the person I am interviewing to have a High Stupidity Handling Quotient. To test it, I act stupid. Sometimes I do not need to :) If I am acting stupid, I would be very interested in seeing the reaction of the other person. Is he / she still smiling and offering me the answers or has the lid blown off? For ex. I will ask them "Tell me the port number on which RADIUS packets are received". Of course I do not expect them to remember it, but if they tell me its easy to find it out in RFC, then they can handle stupids like me :)

Listening Skills: I came across this last week while I was doing a telephonic interview with a candidate and it happened twice in 30 minutes. After asking him a question which he did not know, I explained him the answer. In an over enthusiastic tone, he repeated what I had said, with the only difference that what he said was completely opposite to what I had told him. Now I would have given him the benefit of doubt but it happened again within a few minutes. This was enough to press home the fact that he is not listening properly to the conversation.

Saturday, December 15, 2007

Taking Interviews

Taking interviews is an experience in itself. Different companies place different requirements for recruiting candidates. We need to check out different things. The question is: How do we check those?

Here is my guide on how to check out different aspects of the prospective candidates:

Stability: Ask the candidate about his future plans. Whether they want to study further or not is enough for fresh candidates. For ex. if they say they would go for MBA after 2 years, then check your requirements whether two year is an enough interval for them to be helpful to the company. Past record can tell about experienced candidates.

Gets stuck: Keep on increasing the standard of the questions till the candidate gets stuck. For ex. Ask them what is 5 * 5. Then ask them what is 7*7. Then 11*11. Keep on increasing this level till they are unable to answer. Lets say they get stuck when you ask them 59*51. Does the candidate give up without thinking? Do they try something logically like 59*51 = 59*(50+1) = 2950 + 59 = 3009? If they do, then they are a Thumbs Up on this one. They got stuck and they managed to get their way out.

Seek Help and Move forward: Grill them on one of your favorites. For ex. take them out for a treasure hunt where each next stage depends on the answer of the previous. Check how many stages they are able to cross themselves! Once they get stuck, do they remain stuck forever or do they ask for your help? If they do, do they do it immediately without thinking. If yes, Thumbs Down. If not, then give them hints. Are they able to understand the hints and work logically forward. If yes, Thumbs Up.

Team Work: Tell them that they have to answer a question on How much is 11*Z. Z is an input that they require from a team member but the team member is a little slow and thats why your dates are getting slipped? How will they solve this problem?

Confidence: Try and test their skills on how sure they are about what they speak. For ex. Ask them how much is 5*5. If they answer 25, ask them Are you Sure? If they say it with confidence, ask them again. If they are again sure, they are one up. Then look out for a question where they are wrong. For ex. Ask them how much is 9*11. If they answer 98, ask them Are you Sure? If they say it with confidence, then they are Thumbs Down on this one. They would be putting bugs here and there without bothering to ask whats right or wrong. If they rethink, then they are a Thumbs Up on this one.

Communication Skills: Ask them to explain something which they are very comfortable but you are not. If you are able to understand, it means the candidate can explain what he knows well to a person who does not know it. Then ask them to explain a thing they do not know and maybe you know. For ex. Ask them to visualize how Alps look like? If they explain it well, they are a Thumbs Up when it comes to explaining both things they know and things they might not.

Tuesday, December 11, 2007

Team Management

How to arrange your team? This is one question which drives all top shots in the industry nuts. There is no SINGLE RIGHT answer to this. Well not really. Actually the ONLY SINGLE RIGHT answer to this is the TEAM MATURITY. But it is normally only there in the wish-list of everyone and never ever in execution.

Before we get into the details, let us understand briefly how most product companies are. A product is made up of parts and the same part can be used in different products. So Product and Part form a N x N matrix between themselves. For ex. Salt, sugar and water are three parts and sweet water + salt water are two products.

Now there are two broad ways of management in a product company:

a) Different Product Owner and Part Owner: We have an expert who knows the exact quantity of sugar that should be mixed in exact quantity of water to get the taste which sells. So this EXACT guy becomes our Product Owner for Sweet Water. He is worried only about quantity and does not spend too much thinking about quality. Quality has to be ensured by the guy from whom this EXACT guy borrows sugar and water from. These guys form the QUALITY guys. Now if a customer comes in the saying water is too sweet, the EXACT guy goes to the SWEET QUALITY guy and breaks loose on him. But it could be that water quantity mixed was less. So this EXACT guy was not REALLY EXACT. He pretended to be EXACT.

HOW CAN THE EXACT GUY DELIVER A QUALITY PRODUCT WITHOUT QUALITY PARTS? He can only if the same QUALITY PARTS are being used in some already proved QUALITY PRODUCT.

WHY WILL THE QUALITY GUYS BELIEVE EXACT GUY IS REALLY EXACT? They will only if the EXACT guy proves it time and again.

b) Same Product Owner and Part Owner: Now there is this ONE guy who knows EXACTLY how much sugar and how much water goes to form SWEET WATER which sells. And this ONE guy knows which QUALITY SUGAR and WATER will get him QUALITY SWEET WATER. Well, this is possible. BUT WHERE IS THIS ONE GUY? Nowhere most probably.

And if he is there somewhere, WHY WOULD OTHERS BELIEVE THAT HE IS THE ONE GUY AND THAT THEY ARE GOOD FOR NOTHING? They will if this ONE guy proves time and again that he is THE ONE GUY.

Monday, November 19, 2007

Guesstimate

A search on Merriam Webster Online gives the following result for Guesstimate.
Etymology: blend of guess and estimate
It is a very common phrase while doing planning in software projects. You have to make your best guess to estimate how much time the human brain would take to complete a certain task. At the start of the project, it is just a guess. Slowly as you get on top of the things, the guess part of the estimate goes and it becomes the real estimate.

This whole process often reminds me of a game I played while attending a birthday party as a child. We were shown a bottle that was filled with lots of same sized pebbles. We were to guess the number of pebbles that were there inside the bottle. It was an easier job because the bottle size was fixed and the pebbles were same sized unlike the current software projects where the brain of each individual involved has its own complexity.

Wednesday, November 14, 2007

Things that have all right answers

How many times have you come across debates where everyone is right? Many. Just today morning, I was having a debate with a colleague on what is the right way of distributing work among the people by a manager. There were two approaches which we debated on:

a) Give all the features to the individual and let the individual decide how he wants to plan.
b) Give a single feature to the individual and after he has finished with it, give him second and so on.

Approach A: If someone loves to plan for himself, then he would love approach one. He would be interested in knowing what is expected of him for the next three months and he plans it accordingly. This has a good advantage in projects involving peoples brains as the brain might not be working every hour at the same efficiency. Also, you might want to balance your work with other personal things and so on. As long as you can commit that in three months work would be done, the manager would (or rather should) not be concerned whats going on in your life. This has lots of assumptions:
a) People commit and meet their commitments
b) Manager does not like to interfere a lot
c) Manager has faith in the employees
d) People raise concerns whenever they see them, instead of waiting for three months.

Approach B: The other approach is nice if you do not know how much time the different features will take. In this case, if you are giving multiple features to an individual, then instead you can ask him to work on one feature. If another individual becomes free, then he can pick up the second features instead of the first individual. It helps in delaying decisions till the right moment comes. This is also helpful because normally individuals finish the study phase for each feature before starting work on them.

We had lots of discussion on which approach is better. Finally it boiled down that there is NO SINGLE RIGHT ANSWER to this. Instead, it depends on the Manager-Individual chemistry and what suits a combination of them.

Following are the different options that can follow depending on the Manager-Individual chemistry:

Manager: Plans
Individual: Does not plan

Approach B

Manager: Gives Freedom
Individual: Plans

Approach A

Manager: Does not give freedom
Individual: Plans

Approach: ???? Will be cat and mouse where the manager will always try to pounce upon the individual.

Manager: Does not plan
Individual: Does not matter

Approach: Does not matter because your team is anyways screwed in this case.

Tuesday, October 30, 2007

This can change the way we work!

The thing which we discussed (and I will go into the details a little later) today can completely change the way we work, only if we execute it. We have tried doing it some months back and it fell flat. The adrenalin flows for a day normally for these things and then everything comes back to the same level. Anyways, its good that we find the courage to discuss it again because if we are able to win this one, we would have what we call a "World Class Team"

What we did today was come up with a list of positive and negative points about the way we work? We are a bunch of guys who wanna work hard, do some good stuff and make money. We have been working together for around 3 years now and know quite a few things about each other.

Positive:
  1. We are very fort right with each other. We say if any other person is doing wrong at his face and that is the hallmark of a good team.
  2. We are almost at the same frequency.
  3. Koi angrez nahin hai humme se, no doc / ppt only guy
  4. We all want to work technically even after 5-8 years experience, so we can be very efficient
  5. None of us is a politician
  6. We have trust in each other
  7. We are open to sharing our knowledge if the other person asks
  8. Despite of cribbing and criticizing everything, we continue to work hard.
Negatives:
  1. We speak in hindi even in meetings where people who do not understand hindi are present.
  2. We are negative in our thoughts.
  3. We look to criticize everything.
  4. We do not focus.
  5. We talk a lot and waste time.
  6. We mix emotions with logic.
  7. We do not show interest in meetings in which we are not interested.
  8. Somo of us do not want to do Docs / testing
  9. We do not take proper initiatives, we want to be managed by someone.
  10. We want that every decision should be made after asking us, which is not possible.

Friday, October 26, 2007

Its does more bad than good

We have been taking interviews during the past few months for recruiting people to our company. There are many things we test people on. In addition to the technical details, there are lots of inter-personal things which come into play when you are being recruited to work in a team. In all these things, it does MORE BAD THAN GOOD to all who speak what they do not mean. For ex. We generally ask a person how comfortable he is on a topic before asking relevant questions on the topic. Based on his assessment, we then start from a certain level of questions and then go into easier or difficult ones. Now, if a person rates himself 7 out of 10 and then is not able to answer questions that I expect a person at rating 3 out of 10 to answer, then either I am expecting too much or he is thinking too highly for himself. Anyways, at the end of the day it is the other person looking out for a job. Being open on what you know and what you do not know is the BEST way to behave in an interview because there would alway be things which you would KNOW and things which you would DO NOT KNOW. So whats the harm in admitting it. Follow it up that you are more than willing to learn things which you do not know (of course only if YOU ARE READY to do this).

As the Aussies team have repeatedly said throughout the series:

Your words should be backed by your actions. It leaves a bad taste if only words flow and actions do not follow.
How tough is it to manage?

Day before yesterday we had our weekly status meeting. A fresher has joined our group and he is reading the specifications to get to pace. As he is a fresher and because he is reading any specifications for the first time, he is bound to have quite a few questions. So our manager assigns a person to help him in his queries. There are four persons in our group who could be assigned as freshers. While asking the fresher to be proactive and ask wherever he gets stuck, he asked him to collate all this questions and ask them once a week to whoever is his mentor. Huhhhh. Once a week :) By the time a week passes, things would be all confused within his brain. Ofcourse, if he starts asking whenever he wants to, that also is not the best way.

So what could be the best solution?

Ask the mentor how much times a week he would like to get interrupted?
Would he like fresher walking in without notice, with some notice or at some fixed time in the day?
Any other concern he might have!

Ask the fresher what he would be comfortable in?

Would he love to ask whenever he has a doubt?
Would he like to consolidate questions once a day / few days and then ask?

As a manager, the next step for you would be to find a middle path that makes both of them happy. Going by past experience, you would definitely be able to find one.

Tuesday, October 23, 2007

One on One

It is a great learning experience to be in a Team. You know so many different ways of thinking about a thing that it amazes sometimes. Human Resource has always been an interesting aspect of management and more so in the world of Technology where everything is in the brain. If you cannot keep your employees happy, you are not tapping the potential of their brains to create value for your company. It is AS SIMPLE AS THAT. As part of ensuring you turn out fire before it spreads, managers and top management have what is known as One on One.

One on One is basically a meeting where an employee sits with his manager and discusses (almost everything which falls into the realms of discussion). It is meeting where in general it is assumed that there will be focus on things which are contentious, things which might be negative about you. This knowledge about what could be in hold for you prepares you in advance. There is nothing wrong because if you do not know you are in a hole, you will never get out of it.

So I had these one-on-one meetings with my top management some days back. Now as it turned out, it was different from one-to-one. It was two-to-one, as top management and my manager were both sitting there to discuss the things with me. There can be both negative and positives about this move which form the basis of a different blog post, but here are some excerpts from the meeting.

  1. The Top Boss set the agenda for the meeting saying that he wanted to hear more of negatives than positives so that we can improve. Positives are already there and so nothing special to discuss.
  2. My manager spoke about me - well he spoke nothing but positive things about me. I think this is not quite right considering this is once a while opportunity to tell what can be corrected. My fault I did not go out of my way to encourage him to do that.
  3. My turn and some things which I think we can improve:
    1. We are involved in decision making too late. It is common knowledge in software world that the later you change a wrong decision in a project, the more costlier it is.
    2. We should get the buy-in of the stakeholders. I read it somewhere and I think it holds true for all teams - For any deal to be successful, it is very important to have buy-in of all stakeholders. If people feel it is their decision, they will go to any extent to make sure it is successful.
    3. It is not a coalition government. You need to think what is best for the company. If everyone agrees, it is ideal. If some agree, it is good. If none agree, then change your decision as it will never work.
    4. Everyone loves good work, so be careful while taking decisions. Different people have different mindsets, so you need to balance it. Managing people is almost a full time job if you want to do it well.

Monday, October 22, 2007

Theres something wrong in Google search!

There is something wrong in the way Google is returning my search results. I gave a string of 'VaibhavMadan Ladoo' for Google to search. It came up with two results - one of them was what I was expecting. So far, so good. Now I open the search result I am interested in and go onto that page. I expect my search keyword to be present in that page. But IT IS NOT. I am not sure what search algorithm Google used, but whatever it was it did not give me the perfect answer. Now my gut feeling on how it worked:

I read somewhere that google also indexes the links within a page. In the search result I got in my example, the keywords are not directly present on the page returned by Google but they are there in one of the pages for which a link was there. Now I think that Google also searched those links within the pages and happened to return this page. Because I knew exactly where the keywords are, I was able to go to the page where the intended result is. But if I do a random search (and that is what happens most of the time) I would never be able to guess this.

GOOGLE GUYS, ARE YOU LISTENING?

Or maybe, a chance for a competitor of Google to distinguish themselves from Google.

I would not really be happy if the keyword itself is not present in the page I open after a search result. RIGHT PATH TO THE WRONG DESTINATION ......

Thursday, October 18, 2007

Pilot Project

I tried to search the web to understand the meaning of Pilot Project. I could not a satisfactory answer. But somehow this term has found its entry into the dictionary of our office as something which is being tried by a person for the first time. To elaborate, it is something which you are trying your hands on for the first time and it is not your forte till now, but you would like it to be. For ex. A software engineer who has been into testing and wants to move into development would consider his / her first development project as a Pilot Project which would launch him / her into the world of Development.

Not sure who is responsible for generating the term, but it has consumed a major portion of our lunch time discussions and has been the centre of lots of our office humour.

Kehat vaibhav suno bhai entrepreneur
Pilot Project ki leela se bacho dear

Wednesday, October 10, 2007

The Ladoo Principle

Whew! What all does a manager have to talk about to convince his reporting band. Ladoo is a sweet in India. The Ladoo Principle states that if a child is making noise, then offer a Ladoo to him and he will be quiet for a while. Repeat this everytime the child makes noise. Almost similar corollary can be drawn to the world of Software Engineers.

One of the favorite Ladoos which a Manager offers to the employees in the Service Industry is a chance to go abroad on a long term project. In the first half of first decade this century, traveling abroad used to be very lucrative - good exposure, nice money, chance to visit new places etc. I am not sure how much this still holds good with all the Re Vs Dollar ho halla. It used to work earlier.

The above Ladoo does not really work in the Product Industry as chance to travel abroad is almost next to Null. Most of the things you will do outside the office can now be done in the office also. So whats the alternative. Work :) You are doing one of the most critical components of the project. WOW, did I love this one! People in the team would love to do the module you have your hands on, but I believe in you and thats why I offered it to you.

Another Ladoo is to praise the employee when he cries. You are the sole person on whom this whole project depends, a leave won't move without your consent, you are one of the best performing employees, we can give you anything you want except money as you should not be money driven :) Gotcha...... He is talking about a Free Lunch.

With all these Ladoos being exchanged in every place you go, it becomes very important for a Manager to make sure he / she earns the credibility before offering the sweets.


Kehat Vaibhav suno bhai Software Engineer
Kahin too many Ladoos se ho na jaaye Diabetes Dear

Friday, July 06, 2007

Whats my Managers Manager upto?

Are you interested in knowing what your Managers Manager is doing?

If the answer to this question is YES, then either

a) You have been having lots of free time lately. If yes, then instead pick up a good book and read it.

b) Or You are concerned with where your company is moving. If yes, then turn the concern into action. Type the resignation letter and post it.

c) Or You are killing your free time. If yes, then just FORGET IT. You are in a hole and till you realize you need to get out of it, no one can HELP.

Wednesday, April 04, 2007

Some days are just very interesting!

30th March, 2007 happened to be my last day with Conexant. As it was the last day, I had lots to do in terms of doing the paper work and saying Hi and Bye to everyone I had known for the past 4 years and 9 months stay with Conexant. As if this was not enough for the day, some thing interesting happened. We have a common parking area for cars. I came in late in the morning and I had to park my car in a zone where it had to be kept on neutral because it was located in front of other cars. After our routine lunch walk, we were going back to work through the parking area when I could not locate my car in the area where I had parked in the morning. The interesting day started. I started looking for the car but could not locate. When I finally managed to find it, it was located at 90 degrees to the original parking location. This could not have been done without the keys of the car or unless Vir Hanuman himself had done it. As the probability of the second option is almost next to none, I took a look at my pocket. Indeed the keys were still there. When I came close to my car, the stereo inside the car was playing and the drivers window was half down. The probability of the first option was also zero as the keys were there. So there had to be a third possible option of which I was not aware of. I asked the security guard how the car came there.

Vaibhav: Car yahan kaise aayi? Iski chaabi to mere pass hai.
Guard: Sir, yeh aapke car hai.
Vaibhav: Koi shak!
Guard (to his friend): Tabhi chaabi bahar nahin nikal rahi
Vaibhav: Kaunsi chaabi. Iski chaabi to mere pass hai.
Guard (finally with the whole story): Sir, hamein laga yeh Ravi Sir ki gaadi hai. Maine unse chaabi lekar isko theek se park kar diya lekin ab chaabi nahin nikal rahi.
Vaibhav (inside my mind): Lag gayi watt.......

How can a car be opened with another cars keys? It can even be started with another cars keys and moved around. Well, DAMM the car companies.

We tried getting the keys out but Fevicol ka mazboot jod tha, aise hi thode na tootega. We then went to a local Automobile market. The local mechanic (who knows everything about anything related to Automobiles) tried to get the keys out. Lekin Fevicol holds ground. He decides that the car lock needs to be opened. Hmmmmm. Now it was getting more complex. We decided to take the car to showroom before everything got opened by the mechanic bhaiya.

In the showroom, the mechanic tried to remove the key from the lock. We asked him why he was not opening the lock instead. He said that the lock is made in such a way that either the key would come out or the whole lock needs to be replaced. HIP HIP HURRAY to the mechanic bhaiya. A new car lock comes for 3.5 to 4K. After some effort the keys came out. THANK GOD for it.

Saturday, October 28, 2006

Career Objectives

A few years back a cousin of mine was planning to give a MBA entrance exam. He was asked to pen down the reasons why he would like to join the institute. I tried to help him to pen down the things. Below is the stuff we wrote in the entrance form:

I want to be part of the elite group of the organization which helps in shaping employees lives. I believe that FMS would help me in developing all the necessary skills required to make a rationale decision about issues that wuold have an overall imapct on the lives of the employees. Someone had right said 'Life is too short to learn everything through experiece, so try and learn through the experience of others'. I hope that FMS, through its esteemed faculty, would be able to mould my experiences so that I can help people who come in my vicinity to make the right decisions. Ten years from now, I see myself heading a group of people whose future might be dependent on the decisions made by the top management. I hope that FMS would provide me with a framework that would help me in deciding what is the BEST for all and make that essential difference between the good, the better and THE BEST.

Wednesday, October 25, 2006

Painless Software Schedules

Some excerpts from the Article on Joel On Software

So, you have to make a schedule. This is something almost no programmer wants to do. In my experience, the vast majority just try to get away with not making a schedule at all. Of the few that make a schedule, most are only doing it because their boss made them do it, halfheartedly, and nobody actually believes the schedule except for upper management, which simultaneously believes that "no software project is ever on time" and in the existence of UFOs.

So why doesn't anybody make a schedule? Two key reasons. One, it's a real pain. Two, nobody believes that it's worth anything. Why go to all the trouble working on a schedule if it's not going to be right? There is a perception that schedules are consistently wrong, and only get worse as time goes on, so why suffer for naught?

Programmers are not interchangeable. It takes seven times longer for John to fix Rita's bug than for Rita to fix Rita's bug.

When you have to pick fine grained tasks, you are forcing yourself to actually figure out what steps you are going to have to take.

And when you haven't thought about what you're going to do, you just can't know how long it will take.

If you have to figure out what subroutines you're going to write, you are forced to pin down the feature. By being forced to plan ahead at this level, you eliminate a lot of the instability in a software project.

Most programmers have no idea how to guess how long things will take. That's okay. As long as you are continuously learning and continuously updating the schedule as you learn, the schedule will work.

Updating your schedule daily should only take about two minutes. That's why this is the Painless Schedule Method -- it's quick and easy.

A programmer should never, ever work on new code if they could instead be fixing bugs.

The schedule is not the place to play psychological games.

You might be able to get 20% more raw code out of people by begging everybody to work super hard, no matter how tired they get. Boom, debugging time doubles.

But you can never get 3n from n, ever, and if you think you can, please email me the stock ticker of your company so I can short it.

Not many of them are running business what-if scenarios... these are programmers, here

Monday, October 16, 2006

Why is execution so important?

Almost anybody can tell you what is theoretically right. I know it, you know it and almost everyone in the world knows it. BUT, who ensures that what is theoretically right is executed right. In the professional world, every day we have lots of meetings and everyday we take lots of decisions. YES, all those are right, BUT who ensures that they are executed. Planning takes 30 minutes and its execution 30 hours :)

Below is an E-Mail which I had sent on 7th Feb, 2004 to one of my Ex-Managers. Two and a half years down the lane, we are still trying to execute it. Had I led it to a proper closure that day and at that time, the cost now would have been too low and we would already have reaped the benefits.

Hopefully I would learn something from it and be careful the next time :)

Hi

I have tried to work on a framework with the help of which the automation of the testing of wireless STAs can be done (with the help of WirelessConfigurationTool package). It will require add ons to the code we have for PrismServer and PrismProfileChanged and implementation of test cases. I am giving a brief overview of the idea I have in mind:

There will be test suites and test cases within suites. Test suites are a group of test cases for which the settings of the AP will remain the same. Each test case will have some configuration information in the form of XML going to the PrismPCtl running on the DUT (depending on the test case being executed). The Wireless STA settings will be changed accordingly and the expected result noted.

Before triggering a new test suite, the user will be prompted for permission. This is required because before executing each test suite, the settings of the AP need to be changed accordingly. The prompt would give the user time to change the settings of the AP. This also can be automated by synchronization between the changing of settings in the AP and the transmission of new profiles to the STA.

The framework I have tried to make has the concept of test suites and test cases built in. It prompts the user before starting the test cases within a test suite. The full automation (i.e. automatic setting of AP after each test suite) is not yet done, but theoretically speaking it should not be a tough task.

The ADVANTAGES of automating the test cases are:

a) I think that after a fair deal of automation, only one day should be required per DUT for testing purposes. Thus it should save *lots of time*.

b) There is no need to *repeat the monotonous activity* of running the test cases reading a test case document, after we have considerable faith in the automation of test cases and they start giving the desired results.

c) It should *save lots of firmware dependent bugs* because it is not feasible to run the whole bunch of test cases manually after each firmware / UMAC revision is released (which have been quite frequent going by past experiences).

d) It should be *quite easy to append* new test cases to the test suite as more and more features become available (WPA, WPA-PSK).

e) The test suites test the wireless features and thus they *should be independent* of the type of DUT we are working on. For ex. the same bunch of test cases should work with a USB Cohiba or a PCI device attached to the laptop.

Thanks
Vaibhav

Friday, October 13, 2006

Good things I have learnt from my past managers

Change the circumstances and the same people will behave differently.

It is not the people but the circumstances which create the problem.

Separate the people from the problem.

What would I do if I am a chef of a restaurant and I have customers who are waiting eagerly for a meal? I would put some onion and start frying it. The smell would tell the customers that something is cooking and their patience level would rise. This would give me time to prepare what they want.

I can show you the path, but I cannot walk for you.