Quality Assurance and Project Management

September 24, 2012  9:41 PM

5 Myths of a Developer that Spoil His Career

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

We all have certain amount of myths within us and sometimes we start loving to live with them. A developer’s job is quite critical in any software development project as this is the guy who is doing all ground level work. Whatever he produces goes to the customer though after passing through testing phase.

Understanding the customer requirement is most critical for a developer even if he is master in coding. All excellent developers do not turn into successful ones dues to this factor. It is not bad living in myths if those are positive ones and have a narrow gap with the reality. The higher is the gap of a myth with reality, more difficult it becomes for others in the team to digest and ultimately if might produce a negative impact for overall project.

If we try finding out 5 myths of a developer that could turn dangerous for his own career could be listed as below:

1. I am supreme and am not bound to produce any bugs in my coding. Once this feeling chips in, developer starts negating any improvement points required for his coding and all bugs though get fixed by him but keeps him working carelessly.

2. Tester is just there to find out faults in my coding. If intentions of a tester are doubted by the developer, then probably he will not be able to take his feedback positively.

3. I must write a code that keeps my team dependent on me. Coding in an unstructured manner is a crime but some developer love doing it.

4. I can steal this code as I am writing it. This is unethical. Whatever a coder is writing, he is being paid for it.

5. Keep provisions of code going haywire with a future timestamp? This is a crime.

September 16, 2012  4:44 PM

Overcome 7 Road blockers in the Way of Project Signoff

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

This is a video by ProjectManager.com and presented by their Program Direction – Jennifer Whitt, PMP. The topic is – Learn 7 steps to avoid project closing pitfalls and be left holding the project bag. Basically whatever is done in a project is for the successful closure, closure sign off and commercial closures. The whole journey of any project is based on certain pillars to make it stand, run and reach to its destination. First you have a look at the video and then we discuss few points further down the line.

Inputs, Acceptance approvals, documentation may all appear to be quite simple procedures and small activities but in real life these are basically the activities that if not done smoothly choke the progress of any project.

September 9, 2012  8:23 PM

Celebrating Indian 100th Space Mission And Getting Project Learning

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

India has achieved its 100th Space mission and it makes India as a strong contender one among the top technically strong nations across the globe. India in fact is a unique example of absorbing so many cultures, so many castes, communities and so many contrasts complementing and supplementing; and making the whole nation as successful in various streams.

The same zeal and fire is required in a project manager who must understand the wider and long term goals without bothering about short term hiccups and criticism. Let us celebrate the day and move in the direction of managing projects with a higher level of responsibility and authority.

September 9, 2012  11:59 AM

Video: Would You Stay An Ordinary Project Manager Or Do Some Wonders

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Your qualities are unacceptable as long as you don’t vet them yourself. Your value is ignored as long as you do not accept it yourself. The moment you realize your real value, you will wonder, that everyone else also becomes aware about it. Doing ordinary things in ordinary fora but even in ordinary projects you can manage or handle things in extraordinary manner so as to bring it to new achievements or heights. Doing same things in same manner endlessly will make you mechanized, inhuman and brainless entity.

IF you carry your brains with you, you are supposed to do small innovations in all aspects of life. A project will always have a scope of improvement in its various stages. Watch this video completely to understand what I have said above:

September 9, 2012  11:37 AM

Projectophobia: Fear of Project Failure: Overcome Watch This Video

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

People who fear in life does not mean that they fail in all aspects of life. But keeping a fear in mind out of certain failures can hamper your progress, growth and success in a bigger way. It may become a mere showstopper and block all paths of your life intended to take you towards success and growth. People who do not fear in life for failing or making mistakes have higher tendency of doing extraordinary, amazing and out of box.

Every project will be a hit, success and finish in time is a misleading concept. There are issues – bigger or smaller – in any project. Running away from problems or failures will not let you each to your destination. Watch this lovely video of less than 2.5 minutes that will give you some energy to stay away from fear of failures.

September 9, 2012  11:14 AM

Video on Leadership: Quite Inspiring: Must Watch

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

A Project manager is supposed to lead some teams namely – development team, implementation team, Business/ Requirement Analysis team, Quality/testing team, Process team, support team and so on… Though these teams will be having their own respective leaders (or managers?) but a real LEADER at the top edge of this triangle is a must. There is a big difference between a leader and a manager. Manager is the one who manages, leader LEADS.

Enjoy this video which is quite inspirational, motivating and will definitely fill some real knowledge on leadership.

September 4, 2012  10:44 PM

Dilbert Video: Why Projects Fail

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Why a project fails? It is quite an interesting subject to ponder upon and introspect if you are a project manager. In real life everyone is a project manager irrespective of what role he plays in professional life. We all have to manage multiple things most of the time and success of what we are trying to manage is very important to progress in personal and professional life for all of us. Now let us look at various roles a project manager has to perform during a project life cycle. Have a look at this lovely video:

The life of a project (project initiation) starts with something known as Feasibility Study. And then life begins to look at resources for everything that is about to happen in the project. Resources for feasibility study, resources for development, resources for deployment, resources for hand-holding, resources for training, resources for post implementation support and so on.

At each step of project you move ahead, or rather make any move, based on certain set of assumptions. Assumption that the team built for the project is perfect. Assumption that projected timelines will have no variance. Assumption that design will perfectly match with what customer is dreaming of, Assumption that this project’s success will pour in many more projects…

This video, which is of less than 5 minutes duration takes you through a complete project, stage by stage, making you part of it.

September 4, 2012  10:15 PM

Video: History of Project Management: A Must Watch

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

This is a good piece of video on Youtube titled History of Project Management. It is quite interesting and though provoking kind of video that seriously tries to provide good amount of information on how project management could have begun years back. What made it happen? What could have generated the requirement of project management? What could have been the starting point of project management? How Project Management got evolved?

Was it PERT, IPMA, PMI, PMBoK or was it something else that created the need of its existence? Was it GANTT in 20th century or it had taken birth way back in the days of Giza Pyramids. Probably Giza Pyramids is the best example where one can see well structured and matured project management in place. Have a look at following video and put your ideas right about the subject, in right place.

August 31, 2012  11:59 PM

Funny Video On Communication: A Good Learning For Managing Projects

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Just enjoy this funny video and check if this is what mostly happens while managing projects

August 31, 2012  11:32 PM

Communication Gap While Working On Overseas Projects: Excellent Video

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

You will really enjoy this video published on Youtube that very crisply conveys its message on the gap between the communication arising due to different nations having different ascents for speaking even the same language – say English. This is what actually happens on overseas projects. Having a good vocabulary, speaking power or ascent does not do as good as being versatile and smart to grasp your client’s style of communication though talking in the same language.

August 26, 2012  1:43 PM

A Video on How Clear Communication Helps During Project Management

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Have a look at the video below, that is lovely and crisp enough to convey its message about how to convert all your communication during various project phases into effective and result driven communication. This is a small video, not more than 1.20 minutes but is strong enough to convey its message clearly. Have a look:

August 26, 2012  11:39 AM

Project Management Skills Video

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

This is a video I found on Youtube and though it is a promotional video about some company assisting in Project Management, but video has an example showcasing a project management team headed by project manager Zack. He experiences different ups and downs and different kind of people during management of his projects. The video tries to highlight certain magical project management skills required in a project manager so that he is able to manage his project well.

Here it is, enjoy the video:

August 19, 2012  10:37 PM

Video: Chair Assembling To Educate On TQM

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Hey Guys! While exploring in the ocean of videos called Youtube, I managed to find another good video that was educative, informative, guiding and humorous all at the same time. It is focused on some of the very important aspects of product development or production. Customer requirement is most important aspect of any project – be it production or service oriented. Both ends while understanding customer requirements should be very clear about finalizing business critical issues that are required to be issued in the product or service in question.

Once customer requirement is clear, any outsourcing or in-house development requires some material and resources. It is very clear to get these material and resources in place in time so that the planned development goes as per schedule and resources are well utilized in order to achieve success in developing right product first time. Higher the rework or bugs in the product, higher is the wastage in time and resources and eventually high risk grows in terms of not being able to deliver to customer as per committed datelines.

It becomes very important to streamline and follow processes so that optimization is attained in cycle time, production and defect free delivery. Logically it is not only the project manager of the product manager who drive the project or product but involvement and commitment of each and every member of all teams becomes equally important.

August 15, 2012  10:02 PM

TQM and Continuous Improvement Go Hand In Hand Indefinitely For Any Process

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

This is a lovely video on TOTAL QUALITY MANAGEMENT (TQM) produced by by Rafael Cravioto Torres. It makes you understand well in a very simple manner on all aspects of TQM, the factors responsible to promote it in any organization and some factors on the other hand that demote it or do not let it happen within the organization.

August 15, 2012  8:44 PM

Have You Seen Modern Chairs Video On TQM

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

I was just browsing through some quality related videos on Youtube and found this lovely piece of video having a length of approximately over 10 minutes but is quite interesting to watch patiently and think about how we keep working in our day to day life tasks wasting so much of time. It demonstrates a simple task being done by 6 persons as a team in two different ways and that is what makes a difference in the way we think and perform a task assigned to us.

TQM means Total Quality Management and is having no limitations for optimization of performing any tasks in work area (or personal life) in an optimized and best possible manner. This video was made for TQM training to be imparted to final year students of Edinburgh University. Its purpose was to ensure that the goal of training to students about teamwork, optimized manner of performing tasks, exploring different ways of working on the same problem, redefining process, reducing defects and striving for never ending improvement. This video was directed by Eric and produced by Stuart.

It forces you to introspect on optimizing any process by reviewing the current cycle time and process. Synchronization of Production, Cycle Time, Team Size, Process and Desired Results is very important for optimization of any process to increase results.

The same concept can also be applied in Software development lifecycle where different teams of varying size work on a product that is under development.

August 5, 2012  3:57 PM

QTP versus Open Source Test Automation Tools

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Logically it is not Quick Test Professional (QTP) versus Open Source Testing Tools but I would rather say it is a comparison between paid/ costly tools vis a vis open source tools which are supposed to be presumably free of cost tools. There can be a number of differences between the two categories that can be listed down based on technical capabilities of these tools, commercial aspects and overall procurement and support function.

Following differences can be listed:

1. Paid tools are Paid but Free tools are Not Free: Paid tools have a value tag attached to them like QTP has a value imbibed with it and depending on your needs of test automation, the final cost is evaluated by the vendor.

2. You have a visible person in picture working with a particular company authorized to sell that specific paid tool.

3. If you plan to go for a free tool, think twice before you ascertain that if you are quite capable of managing the show on your own – go ahead. But if you need an assistance, you will be wasting a big amount of time in searching for a suitable capable party who can download the tool on your behalf, customize it for you and make it run for you with all kind of support required.

4. Support in real time for paid tools: You have a vendor to whom you have paid for tool, got it deployed at your location and may be bundled training on that tool also in the deal. You will have a well defined support level bundled in the deal to make it a safe deal.

August 5, 2012  3:02 PM

Test Automation Tool Has Become Basic Need Of Testing In Current Environment

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Test Automation has become predominantly and unquestionably a ‘must’do’ entity in project management, especially of larger size and involving higher stakes. Scenarios are changing at a faster pace from legacy, orthodox, out of date waterfall model of testing to ‘quick to attain perfection’ in smaller pieces based agile methodology. Everyone around the globe, engaged in software development, must be aware of some kind or the other testing automation tool.

Even the organizations those are still not using test automation tools, do not indicate that their testing teams do not require any tool, or the test guys are not aware about the existence of automation tools. It merely might be happening in two cases – one, where the test team understands the need but has not been able to make management understand the need and importance of the same; two, management also understands the need and importance but is not able to justify the investment if currently the customer base is low; or product volume turnaround is lesser.

Note that test automation tools will never be able to replace manual testing completely. There is nothing called 100% testing automation. There needs to be manual testing component in all kind of testing, which has its own importance and need for existence. Only thing is that now the test automation and manual testing has to exist in right proportion so as to do full justification with the product testing and thereby producing an ultimate bug free product at the end of the day.

A manual tester might not be the perfect guy to perform automated testing and vice versa.

August 5, 2012  2:34 PM

Top Management Must Act As a Solid And Transparent Bridge Between Customer And Project Teams

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

There is a lot of information that floats and flows between top management and customer management. Even though some of this information might not be directly linked to the project but might impact seriously on the growth and progress of the project thereby marring the tempo and momentum despite all good efforts being put by various project teams engaged in the project. These scenarios generally arise all of a sudden, out of blue, unexpectedly; but there is no point in hiding or overshadowing them.

One classical example of this that has happened in real life is decision of deploying an ERP in the organization, change in top management key members in a short duration, decision of deploying the same ERP put on hold for a couple of months and ultimately reversed. And during all this period when management at both ends were aware about this situation and rising clouds over the fate of ERP, Project teams were not at all informed about the same and hence finally all these efforts went into a dustbin.

Some fool in the top management who knew all these changes happening in the management of customer side, still was hopeful that this project will not get shaken at all inspite of getting such indications from customer end. The project teams especially the development team sensed decline in relevant information flow from customer’s key users who were aware of the final fate of project by that time.

Had top management took a wise decision of putting the same project on hold till things getting clearer from customer end, and deploying teams elsewhere on other project; it would have been better in terms of financial results and performance.

August 5, 2012  2:12 PM

Thee Critical Touch Points For Project Manager During A Project

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Project manager has to be a versatile and universal kind of entity in an organization rather than limiting him/herself to a particular department or specific focus area. Project Manager has to be visibly an overall scale predicting the progress and health of the project. He has to be informative about all round progress of project even from the corners where relevant activity has ended or is yet to start. It is not that start happens only when it visibly or apparently appears to start, it starts much before that.

Taking all this into consideration, a Project Manager has to act as a radar or high frequency antenna so as to keep capturing relevant information related to project automatically or to a large extent without much of an effort. This can happen only if Project Manager takes care of his/ her important and regularly to be monitored/ reviewed touch points from where all important pieces of information will come through. By joining thread of these various pieces of information, project manager can attain very useful analysis about the progress and health of project.

Thee Critical Touch Points for Project Manager are:

1. Customer: This will be the source of first level of information that will be raw, useful and foundation of product in asking.

2. Management: It is important to understand management goals and vision prior to setting your own goals for any project.

3. Quality: This is the area which needs to be focused upon carefully. The guys should be set free to raise any kind of query related to customer and product that may turn out to be a bigger introspective point for management to look into.

August 5, 2012  1:43 PM

Three Logistics of Project Management

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

If, for any kind of project, focus on three important areas when put right since the beginning of project; might help in attaining desired results and outcomes in appropriate, timely and within budget targets. The logistics are not mentioned here in terms of their importance as I feel all of them are equally important in order to drive a project successfully. Irrespective of the hierarchy they have been mentioned below, understanding and adherence is more relevant.

Three logistic points of any project management can be listed as:

1. Information flow from Customer: It is very important to keep a continuous information flow from customer end regarding their business requirements, changes required, enhancement perceived, and expectations from the new project in terms of deliverable, value addition in business and processes etc.

2. Customer Requirement flow to all concerned in Project: It is not only development team that is demanding customer requirements to be built in within the product. It is quality, implementation and any other stakeholders for whom this information is a good source of introspection and product logic discussions.

3. Internal flow of documents and information: Code is not a secret entity within any organization engaged in development of a product for a customer. It needs to be shared among various other teams (other than development team) so as to get them the flavor of product in the building process and hence prepare their relevant tasks accordingly. It might become a handy and useful tool for teams like QC, QA, Implementation, Deployment etc. so as to prepare accordingly.

July 29, 2012  11:05 PM

No Piece of Code Should Bypass Quality

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Measure what is measurable and make measurable what is not. ~ Galileo Galilei

A code is always testable. large of small, but each piece of code that is catering to a specific need of the business must be tested thoroughly. A small piece unattended may spoil the whole product.

If we always do what we’ve always done, we will get what we’ve always got. ~ Adam Urbanski

If we keep doing the same thing the same way, we keep getting what we have already got, nothing more nothing less. That is why Change is must, in process, in product, in testing, in development – in everything. Change can get you ‘better than previous’.

“The starting point for improvement is to recognize the need.” – Masaaki Imai

Unless and until you know what is to be changed, you will never be able to get the optimized product. It is something like if you are not able to find a bug in a product, you will never be able to find out the actual defect and hence the improvement that is required in the product.

Like tools, mind also gets rusted if not used regularly.

July 29, 2012  10:33 PM

Five Excellent Quotes On Quality

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Failure is only the opportunity to begin again more intelligently. ~Henry Ford

Everything can be improved. ~C. W. Barron

Quality in a product or service is not what the supplier puts in. It is what the customer gets out and is willing to pay for. ~Peter F. Drucker

Professionalism means consistency of quality. ~Frank Tyger

It is quality rather than quantity that matters. ~Lucius Annaeus Seneca

July 29, 2012  10:22 PM

Quality Lessons From Freddy Heinken and Philip Crosby

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Heineken is one of the prime brands in liquor industry and one of the top beers sold across all continents on the globe. The whole credit of success of this Dutch beer brand becoming most popular across the globe goes to its founder Freddy Heineken. Freddy used to be too conscious about the quality of the product rather than focusing on producing in large volumes. He never let his success spoil his quality conscious mind and was always used to get disturbed even for a single quality issue arising anywhere in the globe related to his product. He used to take any bad bottle of Heineken as a personal insult to him. And that is what makes him a great successful businessman.

Philip Crosby gave a different perspective on Quality. He wrote – “Quality is free, but only to those who are willing to pay heavily for it”. Quality is not given and deemed by everyone. Quality has more relationship with conscious rather than anything else.

July 29, 2012  10:01 PM

Quality Lessons From Mahatma Gandhi And John Ruskin

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Mahatma Gandhi always emphasized on the quality of work rather than quantity of work. He wrote once that it is the quality of work that will be easily able to please God rather than the quantity of work. A Programmer if takes a learning from here can go a long way in building bug-free code during his career. Usually programmers are more focused on quantity of work, to demonstrate their capabilities to their seniors. They have a mental blockage in doing work faster and finishing it in of before time and in turn might compromise with the quality of work they produce.

John Ruskin in one of his writings indicated that there is always a scope of compromising with the quality of a product. A product can be picked, compromised with its quality and then can be sold in the market at a cheaper rate. What it really meant was that a compromise in quality, or by making a product little worse, its value can be degraded or lowered and then it can be sold at a lower price in the market. But in software industry, all those companies those tried to follow it, failed and vanished over a period of time.

July 29, 2012  9:41 PM

Learning Quality From Aristotle

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

“Quality is not an act. It is a habit. – Aristotle 384BC-322BC, Greek philosopher and scientist, student of Plato and teacher of Alexander the Great”. This great philosopher, scientist, learner, student, and teacher from Greece knew decades back the secret of quality what even the current era quality gurus are not aware of. Ignorance is a bliss – it is said, but is applicable for fools only.

Quality requires additional sense. Quality comes from heart. Quality has to be in blood, has to be habit rather than acquiring it off and on. A person who becomes a quality analyst, quality control, or quality assurance department has to quality conscious not only in particular projects or products but in all aspects of his/her life.

How many of you guys belong to quality related job and wear quality specialist jacket only at work place?

July 29, 2012  9:03 PM

Learning From Failures Is A Good Practice

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

: It it not good to fail in all your projects and in achieving your goals. But it is inevitable to avoid failures or delays at times. This can happen in any kind of project and at any stage of the project. One bad habit that is counted as good is the ‘Passion of Winning”. Everyone has an urge to win in life. But few are there who are passionate about winning always. There is a good quote I found somewhere whose author is not known. It goes like this: “Good decisions come from wisdom. Wisdom comes from experience. Experience comes from bad decisions. ~ Anonymous”.

This is an excellent quote that fits into all times and eras. We do take decisions in our day to day life, whether in projects or in personal life. All decisions do not go in favor. Sometimes some decisions do large amount of harms that result into project disruption, delays. Wiser men do not let go this opportunity waste. They do learn from the bad decisions taken and their impact on project. This experience if carried forward in further projects and decisions come too handy in going right next time. Such experiences make you wiser one step further every time.

July 28, 2012  11:35 AM

5 Points That Make Software Project Similar To Love Making

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Sounding good or bad, but in my opinion, a software project resembles making love or having sex. There are many similarities that can prove this verbatim. Let us look at the resemblances:

1. Mental preparation: You have to be mentally prepared to achieve your goals and set your milestones. Clear vision and urge to achieve mission is the ultimate goal in your mind in both the cases.

2. Physical Vigor: Without having strength to achieve what you want to achieve, target setting has no meaning. If you assign a bigger task for yourself, you need to be physically prepared for it.

3. Passion: Having both above, and not being passionate about your goals, it is going to hit you badly from both perspectives – yours and the other party.

4. Achievement: Achieving stipulated goals in estimated time is very important. You can’t relax in between even if you want you. Delayed response may end up in no enjoyment during the journey.

5. Respect: Give respect to feeling and requirements of both the parties involved. You just can’t keep on singing a song that is boring to the ears of other party.

July 22, 2012  10:59 PM

If You Are Still Following Waterfall Then You Are Certain To Fall

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Waterfall Video

Hey guys, this is not a technical video attached here in this post. This is a waterfall in a place called Panchkula near Jammu in India. This waterfall video I have watched n number of times and every nth time I watch it, it strikes me of the situation of quality of software that is still in a sorry state in many of the software organizations. Many software development companies are still scaling quality at a lower mark and find their entry in the picture only at the time of completion of development of product.

Waterfall sometimes reminds me of a well organized development team engaged in a project in which they are supposed to develop a business suited product that is meant to cater to the complete business cycle. The business analyst prepared a well structured thick document signed by all stakeholders to vet that yes, this is what is required to be built in the product. Development team is handed over the document with expert comments of project manager and a timeline stating when the product is supposed to get ready and when it is to be handed over to the testing team. Well so far so good, the document has not gone to testing department. They are not aware about the business requirements of the customer and neither are they aware about the beginning of the development of the product.

One fine morning, Project manager reviewed the product and found it okay to be handed over to testing team for finding out the shortfalls.

Is this the biggest shortfall in itself?

July 22, 2012  10:30 PM

Experts Comments on Book: Technology Specific Guide for QTP

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Details of book - cost, availability This new book on QTP for Web Testing is a simple, crisp and a must read for all beginners, novice and experts in the field of software testing. I thought of producing and making all testing guys aware about what all experts are saying about this book – “Technology Specific Guide for QTP” written by Aditya Kalra and co-authored by Timothy Rajan Alex.

Joe ColantonioThis is Joe Colantonio – an expert in test automation tools and is helping all testing guys across the globe through his website by providing latest tools, tips and expert advice in this field. And if an expert is praising about this book, it means a lot. According to Joe, the book is a bouquet full of roses for all QTP learners at any level of their expertise or career. As per him the book, if read thoroughly, is bound to make an individual expert in the field of QTP for test automation. Joe, though using QTP since its launch, has had lot to praise for the book, in terms of learning something new from every chapter of the book.

Sivasankar Jayagopal is one of the Senior QA Managers in Adobe Systems and is happy to see the content written in a very organized manner to cover almost everything that QTP potentially is capable of.

Shalaka Dani, Program Director of MindTree shares his idea about this book by confirming that the content has been chosen quite seriously, full of examples and in a very easy to understand manner.

Technical review of this book has been done by Sandeep Laik – published in the beginning of this book. Sandeep is an end to end test engineer for Unilever Project working with MindTree.

July 22, 2012  9:12 PM

Video: 7 Critical Ideas For A Tester In Any Software Project

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Hey Guys, another attempt to present my one of the earliest blogs in a video. If is not very much different in terms of context of the article but listening to a song and reading its lyrics, makes a big difference. I am not sure whether this attempt is good or not, probably you guys would be the right judge to pass on your opinion openly without any hesitation.

Here is the video:

and the link:
7 Important Steps for a Tester during A Software Project (Video)

July 22, 2012  8:51 PM

Video: What Stops A Good Programmer Becoming A Good Tester

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Hi Guys, This is basically the video version of my long back posted article here on IT Knowledge Exchange website. Probably that is one of my earliest blogs and it got quite popular among readers belonging to Project Management, Software Projects, Quality Assurance, Quality Control fields.

Here goes the video that is published on YouTube:

What Stops A Good Programmer Becoming a Good Tester

July 21, 2012  1:41 PM

Authors Overview – Technology Specific Guide for QTP

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Technology Specific Guide for QTP

The book is precisely of 200 pages, if you include the last 2 pages meant to jot down notes. It is a well written, well titled, and crisply sequenced book written by Aditya Kalra and Timothy Rajan Alex. Aditya or more popularly known as Ady among his friends, is carrying a little less than 4 years of rich experience in software testing in companies like MindTree, Fidelity and JP Morgan. Currently he is Test Automation Architect in J P Morgan, Bengaluru. Aditya Kalra

Ady started his career as Test Automation Engineer and very soon climbed the ladder to reach to a height with a new title – Test Automation Architect.

Timothy, co-author of this book, is has a great journey so far in test automation in companies like – Keane, Sapient and Adobe. Currently, he is Automation Tech Lead in Adobe Systems, Bengaluru. Timothy Rajan Alex Having an excellent experience of over 6.5 years, Timothy is a thorough professional naturally equipped with software testing skills. Starting his career with manual testing, he has excelled in both flavors of testing – manual and automation. By now he has got an expertise in developing any number of variants of automation frameworks – be it open source, or commercial one.

Timothy is as passionate about testing as he is strong in technical skills in software testing. He has mastered and specialized in Web and Windows based applications – JAVA, .NET, SAP, VB – using different tools at different times – HP’s Quick Test Pro Automation tool, Selenium 2.0 (Webdriver), TestNG framework and so on.

June 30, 2012  11:59 PM

Change in Priorities Are Boon For One But Bane For Another Project

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

1. Change in priorities are always a big hurdle in a project
2. Change is not always good
3. Change does not always brings in good
4. Change is good to avoid at times
5. Change in priorities will boost one project but at the cost of many other ongoing ones

June 30, 2012  11:52 PM

Frequent Interruptions In Project Mar Its Charm

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Any project if goes well and ends well keeps drawing stakeholder’s attention during its lifecycle. This attention drawing goes all in positive manner, cheering teams, glorifying moments of milestones’ achievements, project completion etc. It might go other way round also in a way that it does draw everyone’s attention but this time, in a negative manner. Milestones not achieved in time, repeated number of times, teams getting demotivated and demoralized, management losing hopes over completion of project, most of talented people looking out extensively for another job.

If it is later, the situation is not too good for any of the stakeholders. If some of the stakeholders are not getting affected due to these adverse conditions, probably they are holding fake keys in their hands. It is well evident that it is team that makes any project success or failure. A single person may put extra energy or efforts in a project to drive it faster, but a project cannot fail on the whole merely with the wrong intentions of a single person of the team.

There is a big difference between mistaken happened due to ignorance and intentional mistake. A sensible person if makes a mistake ignorantly will learn a big lesson from it and shall never dare to repeat it. Repeated ignorance can be treated as bad or harmful as a big mistake done intentionally to harm project progress in a big manner.

June 30, 2012  11:20 PM

3 Unavoidable Factors Responsible For Change In Requirements

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Change in requirements does happen frequently or infrequently depending on the acceptability level of development team. It also depends on how tightly activities are planned and milestones are being monitored. At times there are certain changes that come right in the middle of a project but shake the progress in a big way. It might happen that the changes are inevitable and may nullify all efforts done so far at both ends.

In such a case there will be a fresh start with a valid reason and justification. Such changes are driven by big and usually external forces. Some of such factors are listed below:

1. Economic downturn: A big deal got undone due to certain reasons thereby shaking the anticipated inflow of funds over a period of time in a negative manner will definitely force management to think twice why they should not stop investing big amount in an ongoing project. Why not shrink requirements to save the larger chunk of investments in the project at a later stage when inflow gets stabilized.

2. Political imbalance: It is not about national or international politics. It is about politics that rests within an organization. An imbalance occurring due to any reason may impact the requirements defined for a project to a large extent.

3. Change in top management: This change at the bottom layer of sea and top layer of management usually brings a hidden storm within itself. The changed brain starts impacting existing brain by infusing ideas to mold them in a different direction. An ongoing project could be a classical example of this.

June 30, 2012  10:46 PM

5 Negative Factors Responsible For Frequent Change In Requirements

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Change in requirements is not an unknown phenomenon in any kind of project. In software development it is rather happens more frequently. The adaptability of asking for such changes from customer end and accepting such changes at vendor end is quite higher and syncs well to such an extent that when a project has overshot budget or planned timeframe – neither of the two get to realize until it becomes too late for both of them.

There could be many positive and negative factors that control demand for changes during an under development project. Some of the top negative factors can be listed below and if these are controlled well during any project; probably success rate of projects will go higher by 50% from current level of failures:

1. Lack of involvement: Requirements have been given at the beginning of project and a sign off of requirements has happened; hence nobody from customer end is required to vet those requirements getting translated into code.

2. Lack of seriousness: At times project gets imposed on customer end users without them taken into confidence and therefore they might not get involved in the project with all kind of seriousness.

3. Lack of Interest: A key user sitting at a high level might have been ignored in past by management and hence just to take revenge; the key user may keep low interest in the project but keeping full care that it does not smell out in the air.

4. Shortage of time: Key users are given this important task of defining and managing business requirements in the project but along with are engaged in many other equally critical activities thereby leaving them with no time to be sincere with the project.

5. Change in strategies: Management at customer end may have change in strategies at their end thereby pushing the ongoing top priority project to a lower one and hence change the prepositions for all involved in the project.

June 30, 2012  10:15 PM

5 Factors That Drive A Developer To Create Bugs While Development

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Developers are probably most creative group of people who keep themselves engaged in creating code all the time. Since perfection and human beings are some steps apart in whatsoever is done by human beings, there always is an urge found to strive for perfection. This is what makes them good developers. There are certain pre-requisites to attain that stage, lack of which may behold them to reach to that stage.

Top most reasons that hold good developers to build a bug free code can be listed as below:

1. Tight schedules: Tight schedules as such are not an issue for any good developer. But when it gets clubbed with certain more pulling impacts; the developer gets drifted away from developing extremely good quality of code.

2. Disturbing/ Tense atmosphere: This is what impacts a developer, or for that sake, any creative guy most. The developers need a non disturbing and cool kind of atmosphere around them so that they keep juggling new ideas in their mind and putting them in the code they are building.

3. Frequent interruptions/ Change in priorities: This is something that will disable any person for reaching to his goals. You start for something, change your mind for something else, or are forced to change your current work in hand with some other work; you are never going to attain your goals in life.

4. Lack of Documentation: This is something quite basic in nature but is not being followed for ages. Nobody understands the gravity of documentation and hence least attention is paid to this most important exercise.

5. Change in Requirements: Change in requirements is as disturbing in nature as change in priorities. It is usually done from stakeholder’s end and usually happens due to many reasons like – lack of involvement, lack of seriousness, shortage of time, change in strategies etc.

June 24, 2012  3:44 PM

5 Must Have Information For Users For A Web Based Product Launch

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Whenever any application is used for the first time by a user, there is always a perceived notion in the mind of user on the behavior and functionality of the application. If the application being used for the first time behaves better than the expectations set in user’s mind, the battle is won; otherwise it is lost. Although it is very difficult to satisfy every end user by a single application, there are certain apps which have higher tendency of likelihood by its end user and hence such apps do well across the globe.

It happens in any kind of application whether it is based on client-server architecture or is a web based application. For web based applications some basic information, if is launched, along with the application; will help changing the preconceived notion of user from a wider spectrum to a specific pattern. Such information can be listed as below:

1. Browser Support: The web application, in whichever browser is opened, must clearly state the specific browser(s) on which it has been specifically built and tested.

2. Resolution: an application may play weird if not opened in proper resolution of the system. Hence it is important that the use knows well in advance about the best resolution for the application.

3. Limitations: Every application has certain limitations that are well known to its creators at the time of its launch. It is better to make user aware about such limitations so that he does not remain in dark.

4. Future Plans: If you let your users know about what enhancements you are planning, it will keep your users hooked to the app.

5. Feedback: A must have feature on every app to gather user’s feedback.

June 14, 2012  4:45 PM

Find Out The Missing Pieces In Such Applications That Are Launched Half Heartedly

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

It was an astonishing outcome of project manager’s approach when I recently met with a group of project managers managing building of multiple products for multiple customers through multiple development and deployment teams. I started with a survey and as per my feeling most of them failed in that. The survey was focused on deriving findings on their approach, concern, belongingness, bonding; with end users.

It all started with a call from one remote end user who was facing difficulty in using an already launched web application. The screen was to add a new record and had 13 columns to be filled on screen-1 and 7 columns on screen-2. When it was opened by the end user, she could find only 11 columns and despite scrolling down, she was not able to see the rest of columns.

She approached the product manager and this guy remotely did something that she was now able to see the rest of columns. Wonderful though, but next day the same problem occurred to the same user. She approached the project manager this time. The project manager also did some jugglery and set the things right for her.

She could not understand what was wrong and what is being fixed by these two gentlemen that it all becomes ok. It was not at all a comfortable situation for her to work on that application to add any records further facing so many hiccups.

Can you just find out the missing pieces of this puzzle? Try and get back to me to see how many pieces you could find out.

June 14, 2012  4:26 PM

5 Must Have For Web Based Product development

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Business applications are moving from client server architecture to web based. The design and usability have become predominantly necessity as strongly as earlier it used to be for navigation. Screen designs need to be dependent on browsers, resolution and focused audience. Microsoft, howsoever popular or widely used has been, still produces unexpected results for which there are no technical reasons. IE8 differs from IE9 and applications working fine on one, do not work well on other, if are not built with depth and knowledge.

Apps built on one browser do not work on others apparently producing lot of misbehaving results. At times there is an incompatible issue that needs to be addressed has to be brought into compatibility mode. Howsoever advancements technology brings in, the issues keep arising in one shape or the other.

Some important factors that need to be taken care of while building a web based product must have following basic factors:
1. Understand web audience well before starting designing of product.
2. Your users are much smarter now as they are not limited to the office boundaries and using only the product hosted on in-house servers.
3. They have understood the strength of web and must have tasted lot number of web based applications before they will start using it.
4. Current day end users are quite tech savvy and well versed with web apps and their strengths.
5. You can’t give illogical or absurd reasons of certain things not happening in the app which are well done in other products on the web. Tools and platform can’t be held responsible for such actions.

June 4, 2012  2:27 AM

Team Composition Is a Critical Matter In Projects

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Team composition is one of the most critical tasks in any project. It if not the count of people that matters but it is the experience, level and maturity of team members that is to be focused upon while selection of members. Members with more open mind and fewer egos can do well as team members even if they are slightly short in knowledge than other members who have personality otherwise.

The strategy of team composition is highly dependent on the size and nature of project. A large sized complex project would require a higher level of strategy formation as compared to a small sized and simple natured project. Though it would be a misnomer that complex issues do not arise in simple projects, there also it depends on the right formation of team and deployment of strategies. A very small product development project may encounter bigger hiccups if the team composition is not done wisely.

It is better to delay a project for the sake of finding right kind of people rather than just completing the stipulated head count in the team irrespective of the skills and experience matching criteria assigned for the selection of candidates. Inappropriate composition of team members will always delay a project and on the other hand in a delayed project if right kind of people are included in the team, they would be able to cover up the time and milestones achievement backlog.

June 1, 2012  5:01 PM

5 Top Reasons Behind All Problems In Project Management Part II

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

4. Milestones identification and achievement: Any project definitely needs perfect identification of milestones. Milestones have to be achievable, remarkable and not too distant from each other. Unless you identify quick milestones to project to management that things are moving in right direction, quite visibly; management will lose interest in project and that may start impacting the project and teams involved.

5. Reporting: If you are doing good in a project, you should be smart enough to project it well, timely and accurately, to all stakeholders. The achievements are to be acquired and shared well in time if you want to enjoy them the most, else they may lose their gravity and impact.

So in a nutshell if we see, it is a right nix of all above points that is required to win over all hurdles in a project. Correct requirement gathering not only depends on right process owners to define the business requirements but also require wise guys who understand business criticalities and can read the mind of requirement spellers.

Team that goes for requirement gathering needs to perform some homework in advance before landing into the customer’s location. There are lot of information that can be collected and understood before meeting the customer.

June 1, 2012  4:55 PM

5 Top Reasons Behind All Problems In Project Management Part I

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Though it is difficult the assume in advance what kind of problems will percolate during a particular project but more or less all kind of problems faced during a project execution/ deployment/ management can be segregated in five top most reasons or categories. These generic segments/ reasons/ categories will be able to address all issues that are encountered during a project and if these categories are taken care of well in advance in a proactive manner, the chances of failure/ delays in any project get minimized and hence increasing the chances of success.

5 Top reasons can be summarized as below:

1. Customer Requirements: Capturing right requirement first time is an art and a science too. Business Analysts and organizations need to master in this so as to move ahead with crisp directions for development team.

2. Team Sizing: Estimation of right kind of people in team, with right kind of experience and appropriate count of them helps in creating an optimum team size. It could be difficult to do the right sizing well in advance but if customer requirements are documented well, identification of right roles and experience becomes much easier.

3. Team Management: Team management is an uphill task during any project. It is not only the technical aspects than need to be overseen but also the soft side of the personality of each of he individual in the team that need to be addressed to.


June 1, 2012  4:47 PM

Wrong Requirements From Customer Can Do Blunders In Any Project

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Wrong requirement gathering can happen in two ways – 1. The team assigned to collect that information from direct process owners at customer end are incapable to differentiate between picking up right thread and dropping wrong threads so that no confusions arise later. But this is the most critical job and done by least business analysts. And 2. The process owners at customer end are incapable to spell out the right kind of business requirements that need to be built in the new application in question.

This does not mean that the designated process owners are dumb in their roles or knowledge. It is the question of spelling out the right requirement where they might not be expert. Management’s and BA’s role (and experience) comes quite handy in such instances.

Customer needs a tree that needs to have green leaves and bears fruits every season and you documented to build a lemon tree that becomes a cause of failure at the end. Did you ask customer what season should the tree bear the fruit, what should the maximum height and width of tree, what size of fruit will be most suitable for customer, hard or soft fruit required, what are the maximum benefits to be drawn out from the fruit – juice, fibre, extract, sweetness etc.; is very important to capture right in the beginning so as to give maximum clarity to your development team that is well aligned with the customer real requirements.

After all it is the right information that has to flow in building of the application. If it happens RIGHT IN FIRST GO, nothing like it. It becomes win-win for both.

May 26, 2012  5:07 PM

How Much Aware Are You About PBL

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Many of you would not be aware about the abbreviation PBL. Well, it is Project Based Learning. Simple. What do you do with it? Can I see a single document that you made during or after a project that comprised only and only of learning acquired from the project? What? There is no document. Well! Then where is the learning gone? How long will it remain in memory? What will be the final resultant of this learning? Has there been a long term beneficial learning from this project?

Project ending successfully in time or called off after spending some extra months over the stipulated ones; give lot of learning. It all depends on the project team, how much matured it is, so as to get the best pieces of learning getting recorded in their knowledge management and keep referring to it as and when required during the ongoing projects in future.

Project based learning can be termed as learning only if each and every success and failure during the project is minutely observed, documented and analyzed deeply to find out the top 5 reasons that made that success of failure happen.

Delays and achievements of milestones, team member’s strengths and weaknesses, identification of real heroes, achievers, motivators and strategists of the project; all that matters a lot to record.
Someone in the management has to intelligent enough to understand what all is happening during a project that is getting ignored and can become a big knowledge base for future projects.

May 26, 2012  5:06 PM

Project Estimation And Project Team Can Become Big Wrongs In Project Management

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Any activity that is not done right becomes wrong. Probably it is not the management of project that matters more but it is the learning from previous projects that can help you in running a project well and completing it in time. There are lot of factors that can help in running a project in a well-structured manner and ensuring achievements and success of milestones during each phase of the project.
It is the struggle that project team has to face and win over.

Various wrongs that can ensure project failure are:

Project Estimation: Project estimation, if not done appropriately, can lead to wrong team sizing, wrong direction and wrong milestones selection. A small hole appearing as no warning in the beginning may become cause of the sinking of large ship in deep waters at a later stage.

Project Team: Project team is the real bunch of warriors that make your success happen in the war known as project. A team needs to be rightly selected, so that all members respect each other, stay in sync, keep motivating each other along with being self-motivators and above all need to be success hungry. Any shortcoming in understanding the core requirements of a team can lead to wrong selection of team and hence giving a wrong shape to the project at every step.

May 24, 2012  1:50 PM

Three Goals Of a Project Manager To Ensure Project Closure In Time

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Most of the projects get delayed worldwide. There could be various reasons for that. Anything can hamper the progress of a project – be it logistics, demographic, person based or decision based reason. A material getting stuck for delivery could hamper the progress of a project. Any local issue also may arise as a showstopper for a project. Persons involved in a project may become a bottleneck. A major decision could even mar the progress.

Why it happens becomes historical and a reason of analysis to work on at a later stage. As a project manager one needs to be proactive to anticipate a problem in advance and find out the reason to mitigate the risk arising out of it. First goal of a project manager should be to ensure that no risks evolve during a project. Though it is impossible to run a project and complete it without encountering any unanticipated risk but then the second goal of a project manager should be to be prepared for any unalarmed risk and promptly finding out a solution for it so that the risks get minimized and progress gets saved from getting derailed.

Third goal of the project manager should be to mentally prepare himself for any kind and any level of problem arising during the project. He should have means and measures to encounter such unwanted weeds growing vigorously in between the useful crop. For each vertical of a project, project manager should work out alternative routes well in advance so as to take a planned diversion in case of a crisis.

May 19, 2012  7:52 PM

What Is ETL Testing – An Overview

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

ETL stands for Extract Transform and Load. ETL can be treated as wider and broader horizon of normal testing that is done for business applications. Technically the process remains same as is there in any other kind of testing. First and foremost step is to understanding of requirements and business.

Once the requirements are well understood and business concepts are clear, it needs to be mapped various aspects like what is there at presents, what is required, in what timeframe and with what kind of resources. In fact once the requirements are clear as well the business goals are understood, one needs to validate and get them vetted by the respective process/business owners. After this estimation needs to be worked out on the basis of timelines being proposed to be consumed.

Once this gets approved, test planning is prepared. Basis of test planning is always the test estimates, business requirements and scope of work. Test cases are built along with the test scenarios based on the requirements and understanding. After the test cases are ready and get approved by test lead, test bed is prepared, pre testing assessments are done, approvals are taken and tests are executed to find out the results.

May 19, 2012  6:12 PM

What Analytics Tools Do You Use For Project Management

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

CPA (Critical Path Analysis) and PERT are well proven age old tools to use for scheduling and management of large and complex kind of projects. They came into existence in mid of 1950 when in US huge projects were looking for ways to control them in a systematic and objective manner rather than their get going in subjective manner without any monitoring or control over them. There are many other planning and analysis tools that can help you in driving your project in right direction with right pace.

Tools are nothing but means to equip you to measure your project at any instance; and take corrective measures in case if required so. Tools help you to assess project in an objective manner proactively rather than taking it for granted going in right direction without any real measurement of it.

It is not necessary to invest big amounts for such tools. Simple but effective templates built in-house can be used for the same purpose of analyzing the progress of a project.

May 17, 2012  5:34 PM

Learning From Failures Is An Art

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Failures do happen in projects. There are definitely sizing and severity of failure in a project. The size and severity of a failure is measured by the impact a failure poses on business in various terms – reputation, financial and future loss in growth impacted by such factors. Some organizations are wise enough to understand the gravity of failure and start working in direction of mitigation of risks that arise out of it.

In fact chances of failures go higher in a project if there is a major component missing during the management of project and that component must be taken care of well in the beginning of a project as a whole; and at the beginning of each phase of the project. This component is nothing but is termed as Risk Management. Risk management in simple terms is how you manager risks. To manager risks it must be clear to you what can pose as a risk in a project and how much impact can it have on the project if it occurs. Measurement of impact needs to be objective.

More realistic assessment of risk, planning preparation to mitigate the risk and actions taken for the mitigation – all deliver to higher chances of progress of a project and its success.

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: