A project is like a large container of apples having rotten ones among them but hidden well in between the good ones; if it is not QCed well. Quality has a major role to play in determining the health of any project/product and to ascertain when the product is in right condition so that it can be released to the customer.
Three qucik questions that come to my mind for a QC head/ team are as below:
1. Do you Get into the shoe of your customer: As a quality team, your prime role, while QCing the product is to get into the shoe of your customer. If you don’t have that capability probably you might do a good quality check of look and feel but the lifeline of the product – its functionality; would get affected in a major way.
2. Are you Aware about the customer requirements: If you have gone through the customer requirements in detail; have clarified all your doubts cleared with the customer/ development team/ product and customer analysis team; it is very good. Otherwise you are hitting the goal in a total dark condition. You need to learn customer requirements well, complete in all aspects; get it into your blood, and then start analysis of the product built to cater to those requirements.
3. Are you engaged in the project right from begining: If you are partnering the project right from its inecption stage; it is great. Otherwise you have not checked all the compartments of the train but a sample testing.
The quick questions that I wanted to post for a project manager who is managing a project come to my mind as below:
1. Do you own the project: Are you merely acting as a project manager without owning the project. If that is the case then probably you will have enough number of things not moving as per expecations in the project and on top of that you would have enought numbrer of excuses for them not getting closed in time.
2. Do you really love your job: If you have become a project manager not by choice and merely by chance then probably you are going to get in thick soup sooner of later unless you start loving your profile thereby taking project timelines passionately.
3. Are you Proactive enough: Do you have an ability to foresee any showstoppers that are going to misalign your project or derail your smoothly running project.
If you have an answer for these three questions, it is good, at least you care for your project. If your answers to these questions are affirmative, probably you are going to win the game; else be ready for a big disaster at any moment of time.
This article is in continuation from the previous one…
4. Clustering: You have different flowers in your garden. It depends on you how you carve them, mould them, arrange them, and cluster them to prepare the best of the bouquet in the world. Generating a feeling of pride in your team for working with you on a project is something that can fetch the best of results for you in any kind of testing conditions.
5. Cognizant: If you respect conscious of each of your team members, probably your will be the luckiest person on this earth to get everybody’s respect from the bottom of their heart.
6. Common-sense: Apply common sense everywhere, in all aspects of your project, though it is not too common. The more you grow in life, the more you will need it. And it applies in reverse order too. The more you apply it in your work, the more chances you have to grow. Understand the nerve of customer in order to win over any kind of situation.
7. Commanding: You have to be demanding and commanding in order to get the best out of your teams and then give them the best in return.
8. Cameo: Remember that you are the hero for your team(s).
9. Cost Effective: You have to be cost effective if you want to increase profitability of your project. Walking the talk is the best way to achieve your mission.
10. Colourful: Wearing the same face expressions, presenting yourself in the same mood, talking to your team members in same manner all the time will make the journey dull and boring. Be vibrant.
Some people match with their job well. Some jobs match with the people who accept it. Doing something well is one thing, doing it in an extraordinary and simple manner is not everybody’d cup of tea. Very few project managers are there who vivaciously run the show with complete positive frame of mind with 360 degrees of integrity.
Ten Cs that can make any project manager a manager with an extra edge are as below:
1. Consistency: One time win cannot sustain a captain as captain. You have to have an urge to win all the time you get down on the field. You have to keep on achieving success not once but always. You can’t sit on your laurels. Failures are unavoidable at times, but learning from failures and let it not repeat again is the mark of wise men. Never repeat a mistake. Making a mistake and learning from it makes you wise. Making the same mistake again proves you fool in front of others, unarguably.
2. Clarity: Clarity of business, clarity in mind, clarity about your product and clarity about customer is very important without which you just can’t survive in the stream. If the picture is not clear to you, it can’t be expected from your team members to have a better understanding and clarity.
3. Cognitive: Perception of success is as important as success itself. If you can’t perceive success in advance, you won’t strive for success. You must have a passion for winning and getting a smile on every face of your team.
Very few projects get cleared off in terms of timely payments. Mostly the reason is that payment terms are not clearly defined in the beginning of a project due to which there remains a scope of ambiguity or confusion. When the execution party thinks it is the right time it is not the same on the other side.
A situation of conflict, confusion and ambiguity can be overcome if following points are taken care of:
1. Clear cut Project Requirements and Scope: A clear scope and set of requirements can help in proper closure of project as and when the scope under target is completed and the requirements are met.
2. Well Defined milestones earmarked for part payments: usually complete payment of the project is divided in different parts. Each part is associated with some success factor of the project, termed as a milestone. A milestone is something distinctly recognizable and ensures that project has reached a substantial progress mark.
3. Business Goals: The purpose and goals of business justifying the purpose of going for the project must be very clear. The benefits anticipated from the deployment of the project might not be drawn immediately during the deployment but the visibility of those must be there in the picture, with clearly measurable means.
4. Payment Terms: Wherever payment terms are connected to subjective achievements. The achievements that are associated with different instalments of payment during the project must be very objective, measurable and demonstrable.
5. Management Satisfaction: Payments are released or put on hold basically on the directions of top management. Top management go by the words of other key members in the frontline or first level management. It is important to understand management goals clearly, define them black and white, and achieve them, before applying for the payment.
Project management is not a film development studio that requires complete dark for a good quality of film to take place. Project management can neither be treated as a long tunnel seeking light of the day. Project management has to happen in daylight, in open and with complete team participation.
So if project management is something that cannot be done in an isolated manner, it means that there need to be intelligent experts who are proactive enough to control any volcano or black hole in the making during project lifecycle. No mistakes, no errors and no separate missions in a project must be the sole goal of all members of project team. Immediate addressable process must be in place to identify any gaps, fill it appropriately and finding out the learning out of it.
Basically a project progress must be visible clearly from all angles to all its stakeholders. Every step movement in the project must be marked on the project status chart updated in all manners. The status of project should cover tasks in hand, tasks which should have been completed, tasks to be completed with timelines, tasks that crossed their deadlines and tasks seeking extra attending to get completed as per their targets set by the team.
Any Project team would comprise of various level and expertise carrying people. Expertise is different to technical strength. There might be a non-technical project, for instance, but would require almost equivalent level of expertise as in otherwise. Depending on the nature of project, team composition is formed that initially need some fillers in terms of generating team sense, harmony, respect among each other in a newly started project.
With the help of fillers (which may be people as well as some intellectually designed exercises/ activities) any kind of gaps that start taking shape among team members, it can be ensured that those gaps vanish soon, are short-lived and do not form again. For any composition of project team there need to be a well identification of expertise of people forming the team besides having their functional expertise. Primarily there are three kind of people that govern and drive a project – Game Setters, Strategists and Warriors.
The number of people in Game Setters category would be very few. They would have a capability of delivering lot of ideas by saying just a few words. They don’t really need to be visible physically, but ensure their presence is being felt throughout the project journey. They are generally trendsetters, leaders, mentors and self-believers.
Strategists are people larger in number and are strong in mind. They strategize winning tactics on the basis of the Game decided by Game Setters.
Warriors are the executioners. They are most front runners, visible, and seemingly the people who are doing most of the work.
Project lifecycle consists of many stages. It starts from Project initiation phase. Although project initiation phase is the formal beginning of a project, actual project related initiations start well prior to that which gradually lead to this stage.
Though every stage of project management has a meaning and importance, it is the Execution Phase that if starts in time, goes well meeting all its milestones within stipulated timeframe and budgets, gets least of jolts and completes its journey successfully; adds a lot of value to overall project success. Every project execution is a new journey, and a new learning. Usually if an already faced issues in any other project, repeats in the current project, it is easy to overcome it, due to already gained learning. But more important is how you manage a first time faced problem.
A well-defined process to face a new problem, document the learning out of it, and making it a repository for other teams to refer to is always helpful. Some kind of benchmarking is important in setting targets for a complete lifecycle of new and old problems, as and when they arise in any ongoing project, plays an important role in PEM (Project Execution Management).
Tackling an existing problem does not ensure that there will be no further issues in the project. Problems come and go, but need to be addressed in a better manner every time as compared to its earlier occurrence if it is a repeated problem. Logically frequent occurring of repeated problems in a project lifecycle if not at all a good sign for any kind of project.
There are various means of understanding your level of comfort in project management. You might have done good in managing a single project well in time and budget. You might have managed multiple projects in your career but one at a time. So far so good! But are you good and comfortable in managing multiple projects at the same time running at different pace and different stages.
Are you comfortable in the midst of your triangle where you have your management, your customer and your team at the three corners of the triangle? Imagine yourself tied with elastic strings and the three corners having the control of those strings, your most successful factor lies in not letting your balance go off at any moment of time, and not let any string break off, at the same time.
Balancing is a very important aspect in project management. You need to be a juggler while managing a project or a number of projects.
Project Management itself is a matter of quality. If the methodology is not quality prone, it is going to result into mishaps time to time. Yes, one way of getting 100% success in your projects is simply not to have any targets in sight. Let it go as it tends to go, without putting any extra expectations in it. Otherwise if you are part of current economic crisis hovering around the world; then you must be having tight budgets and timelines to complete your targets and hence you need to inculcate high level of quality levels in managing your projects.
Five areas where you really need to have quality could be:
1. Customer Dealing: If you know how to identify your prospective customer, covert the deal into a long term customer, then you are a winner.
2. Product Range: If you have quality product in your pocket, your efforts are decreased in getting instant nod from your customer to sign a deal.
3. Customer Requirements: You must understand what customer expectations are when the deal is being signed. Customer might not able to tell you all, but you have to have your quality measures to understand its needs.
4. Team Building: There need to be an appropriate team that faces the customer. Each team members must understand the customized manner in which a customer needs to be managed.
5. Product Sizing: Customer might have agreed for a sample product of different size but his actual needs might not fit well in this size. You need to understand the right size of product (be it a service) that will cater to all needs of the customer.
Is it that project management is denounced so often; it has become a hyped or rather an overhyped subject in the market. Does it require so many consultants, so much matter and so many companies working to correct your ways of managing projects. As a matter of fact, are those consultants, portals and companies working towards improving your project management style, they having a great level of management of their own projects?
There are two ways of learning and specializing in any field of life and profession. One is to take up any challenges and then learn by means of facing them. Second way is to learn from some experts beforehand jumping into a special task. Former would be a painful process and would also be quite time consuming.
But if everything goes well, it is the first way listed above that will produce the gem of an expert. Second way will no doubt be lesser painful and it will also product an expert in return, but those experts produced by means of method 2 will be limited to their prescribed path only and any expertise required in areas away from their path will lead to a demand of another training from expert. These guys might be lesser prone to take up new and unknown challenges as compared to the first ones.
But does it mean that project management experts keep putting their hands on new techniques so frequently so as to get the flavour of them and analyse the pros and cons out of those techniques so as to find out the best of the deal.
Project management is a set of processes and not a tool. Rather it comprises of a number of tools depending on the maturity of an organization in relation to management of projects. It is not mandatory to have tools to manage projects but it is always a boon to have good and effective tools to make your decisions quick and responsive in time.
Tools assist in aligning your goals and targets and somewhat proactively addressing to any road-blockers in the progress of your projects. There has to be a complete sync between your processes, tools and milestones that you want in your projects.
Managing projects efficiently is a great art. Organizations that achieve this art have always an edge over the other organizations struggling
Project portfolio management strategy seems to be a heavyweight but actually it is more about managing a project in a scientific manner so that the success can be ascertained well in advance based on the way it behaves during its progress chart growth.
There has to be a Steering Committee, a PMO, and a group of project managers who altogether decide and define the process of management of multiple numbers of projects running the business involving a large number of teams. It is very critical to understand the critical factors that contribute towards the project success. Level of understanding is a good factor to assess the maturity level of the organization managing good amount of projects. It is good to see whether project management is a struggle in the organization or it is so well defined, smooth and easily manageable.
After all everything in the business is cost based. When it is all ok, not much pinpointing is there, but it start happening otherwise thus making the situations much complex and unfriendly.
Post implementation stage comes after a project implementation has been executed well and completed. Formally there is a project sign off after which the product is handed over to the key users at customer end. Customer management also ensures that a good amount of confidence has been built in the product users at their end in terms of product awareness and usability. Ultimately if an investment has been done by the management on a product, it is for the sake of making their life better, giving them quick and useful results; thereby resulting into the optimization of business process.
But under the carpet, there is always a lot that remains to be addressed after the project completion. And that is why there has to be a very clear process defined process to manage the support function on the product from a remote location so that no disruption is faced at customer end while using the product or getting desired results out of it.
Rather than customer, it is the product owner, who knows well what all kind of issues arise usually at customer end, once the implementation team returns back and the product becomes the ballgame of end users.
Project sign off is a stage where customer has to be very cautious, and awake. Product team will always try to convince about the completion of tasks by way of some or the other evidence. That evidence has to be vetted by customer before agreeing to what the product implementation team claims about the product.
In fact a good company while launching their product in phases will always keep their customer attuned regarding achievement of targets and milestones at each stage, putting it on live, and taking sign off from customer for each step.
This way getting a final sign off at a later stage would not take more time, efforts and energy, at both ends.
If any project team assumes or has a functioning style of working in an isolated state, or away from customer (not physically but in terms of involvement and awareness); then probably, the project success would remain a big question mark. Simple reason is that you have your customer requirements drafted well and confirmed by customer, as well. And you get back into your work den to start development in a full blow.
The whole requirements understood are now transferred to development team for taking it further and translating the requirements into product specifications. What if some workflow and templates are built, even if in a document or a presentation, and shared with the customer, will get everyone involved in sync so as to avoid any confusion at a later stage.
It is always better to hang on at this stage, fully take customer’ attention towards what you plan to build, in a detailed manner, and then move ahead.
Customer end involvement in a project is as the project requirements and deliverables. Very few project teams in the world exist that are highly professional in understanding customer requirements in first go, define their project specs with crisp mapping with the customer requirements, and then building & delivering the product to customer right in time.
If all this can happen with least involvement of customer, the whole credit goes to the project team. Some credit goes to customer also in this case that a high level of trust was maintained throughout and probably the business requirements were defined so well that there remained to ambiguity or confusion over it.
Usually customer has to get into the project to a large extent, throughout, so as to ensure that it moves on with right pace and direction.
Development team is not sure about exact business requirements and how the final product would look like but due to high pressure of timelines and targets, they decide to carry on and produce on the basis of whatever they have understood.
Will this save time or would result into serious risk of non-completion of project. Product built in such a manner would result into a half cooked dish which nobody would be able to understand and digest. The development team would not be able to convince about what has been built if they themselves are lacking clarity of what was required and what has been built.
Had it been not better and wise to jot down the requirements even if they were not understood well and then get them vetted by the process owners so as to avoid such dark and directionless situations at a later stage.
Documentation is not my cup of tea. If you are a project manager and think like this, you are going to have a bad time after some time. Team management, task tracking, milestones, risk assessment, and project management is all what you need to manage all the time.
If you don’t have a proper way of recording your tasks, backlogs, target dates, tasks assigned to various team members, alarm and alert system etc. in place, then you are at high risk.
PMO is a controlling hub or facilitation hub – is always a point of debate among project management specialists. Is PMO a group of highly powered people in the organization aimed to take control of all kind of situations in a project? Or is it a group of highly resource rich persons in order to provide all kind of support and assistance to any member of the project.
PMO’s role is to take a project out of crisis? Or proactively ensure not to let project getting into any kind of crisis. Both kinds exist, and work. One situation is opening of umbrella when it starts raining; and the second one is working under an umbrella under any kind of weather conditions.
Does it take more out of life of umbrella if it is overly used or does it make an umbrella jammed if not opened and used for long.
And then there are those kind of third category of people who know before getting out of house that it is going to rain – but don’t bother to pick up the umbrella. They might be some special kind of people able to manage any kind of situation even under high level of resource crunch.
Can a project run without a project manager? There are two ways of looking at it. One – the ship is so strong in technical aspects that it does not require a captain; and another – the boat is in so bad shape that whether it has a rower or not – does not matter.
Well there is no project in real life that can not be revived back from its doomed shape. If there is a way out for coming out of a bad situation, it need to be thought of and worked out instead of leaving all hopes and lay down all your weapons.
A project team decided to run the complete project lifecycle – initiation, development and deployment – without any involvement of a quality person. Does it mean the project team is totally ignorant about the quality factor in a project? Or does it mean that they are overconfident about managing the quality part on their own without engaging any quality specialist in the project.
Or it could mean that they have already been doing it in the same manner and have been quite successful in their past.
There could be a third angle to it. The project team itself comprising of dual specialists in each role. Meaning thereby, that the development team is specialist in two aspects – development and quality. And the same implies to each and every member of the team – doing whatever role – is a quality expert besides being expert in his/ her running role.
Project manager is too technical and less business savvy. In today’s world is it possible for a project manager to be highly tech savvy but lack in business knowledge of the domain or vertical in which he is assigned to run the project successfully.
It is possible, if it is too technical a project in which very less business domain knowledge is required. Something like setting up of a data center for a rubber producing company. Here the technical knowledge of the project manager in such projects will be highly important. It does not matter whether the project manager knows anything about rubber industry or not.
But same thing does not imply in all cases. If it is required to set up a data center for a media company or a call center, it is very important to understand the business needs as this would be a unique case for the project manager.
Based on a report published on a research site, scope creep is one of the biggest culprits responsible for failure of project. Scope creep is nothing but shortfalls in the requirement gathering from customer during the customer requirement documentation phase of the project. It is quite relevant to a wrong map in your hands will never be able to land you in right destination.
Howsoever clearly designed map you have in your hand, with clearly defined paths and directions, but if it is wrong map, if will certainly never let you reach the desired destination. Probably a small shortfall in the requirement specifications could lead to a huge gap in acquiring the goal within stipulated budget and timeframe. Extrapolated budgets and schedules do not lead to internal or external satisfaction of the stakeholders in a project. It impacts hard on all fronts and thereby resulting into disharmony and loss in involvement of stakeholders in ongoing project.
It is not that a risk can’t be mitigated. But before going for a mitigation plan, it is important to understand the level and severity of risk. Once you understand the gravity of a risk, it becomes easy to hit its causes and put all efforts in mitigating the risk.
Any risk and its mitigation cost – directly or indirectly – and put its negative impact on the performance of a project. Therefore it is always better to leave a scope of higher amount of risks in your project.
As per a report published by Info-Tech Research Group, in last two years there is a meagre 15 percent of organization across the globe that have been able to finish projects within the projected limits of time, budget and scope. It is really good to see that somewhere some group is able to achieve with some proven or innovative kind of strategy, philosophy and tools. But it is bad that the percentage is too low.
Why is it not possible for all projects to have a good ending meeting all desired targets and achieving a high level of success? This research report identifies four major buckets that cause project failures. It also helps in identifying those four categories of failure traps and how to prevent getting into those traps.
There are different ways of looking at it. You start a big project, follow some preset methodology by forming a strong team and adhere to your plans. Success usually doesn’t come by fluke. It involves a big amount of every step introspection and team discussions. It never happens that everything goes as per plan. Some failures, hiccups or roadblocks do arise but that doesn’t mean that this is the end of road.
A proper management and mitigation of internal and external opposing forces paves a smooth path for project roadmap and ultimately a grand success. At the end of the day what matters most is where do you decide to fall in during your project life-cycle – in a small chunk of 15% successful companies or the other side.
Sales department is the one that brings in the business for any organization. Most of the sales start with leads and cold calls which gradually transform into hot calls, though not all. Once customer show willingness towards product, sales team pushes the lead to techo-team so as to educate customer about the technical details of the product and overall cost impact on the solution desired by customer.
After signing of the contract it is the project team that starts managing the customer. Once specs are defined, during project initiation phase, when customer requirements are studied and understood in detail, it is taken over by the development team. One entity that is project manager has to continuously keep a track of project progress and health; be it at any stage in any of the phases. Project manager is the longest phase window to customer. Project manager in a way is front office of the organization to face the customer front during project lifecycle, with no doubt, a good amount of team members at the back end engaged in various amount of tasks.
There are ups and downs during any project, and there are a number of doubts, queries and questions raised by the customer which have to be faced by project manager. It is the sales pitch in project manager that has to come handy during these interactions with customer. Even if grass has not grown as per expectations, project manager has to convince customer that it has started growing, and is all green.
PMO comprises of the core members of project management responsible to drive project in right direction under all kind of opposing situations. It is responsibility of PMO to ensure that project has to meet all milestones in project timeframe so as to reach to its final destination of success. Any risks arising during project lifecycle need to be understood well in advance by PMO with an immediate course of action to mitigate those risks so that the project does not deviate from its path of success.
Still there are many mistakes done by PMO that lead a project in wrong directions resulting into a big disaster. Some of those serious mistakes could be:
1. Start with a big bang and then lose the track: A high noise is created to start the project but it is so loud that the actual essence of project gets lost.
2. High Speed but without real sense of directions: There is high level of meetings and plans but all teams working 180 degrees to each other. What it means is that there could be some alignment in some teams among various present in the project but overall resultant comes out to be negative.
3. Rewards: Give big rewards to team/ members for smaller achievements thereby creating a big amount of disharmony among team members overlooked for serious achievements and hence a downgrade in momentum and tempo.
4. Respect Customer: Respect customer blindfolded, so much so, that unreal demands are accepted.
5. No Controls and Checks: There might be some there on papers but not in reality, hence creating a big chaos.
We all are human beings. Projects are made to be driven not only by human beings but it implies to all living world. Project comprise of deadlines, targets, follow-ups, meetings, team creation, team management, and so on. An apple plant has a target to bear apples when it grows into a tree. How does it know that it has to bear apples and not some other fruit?
What drives an apple tree to bear apples is an amazing topic to introspect. The same water, air, sunlight and other natural ingredients that go into a weed plant go into a plant borne to bear fruits. Is it bound of any compulsions of others wishes to bear any other kind of fruit, if it is an apple tree. What it means is that the tree decides on its own that it has to bear what kind of fruit. Or rather it is the seed that designs the complete project plan of plant growing to tree and bearing large amount of fruit, which is apple in our case.
What does it implies? It implies that if a good quality of seed, which can be correlated to project initiation plan, it can never give any chances of failures during its complete lifecycle. The air, water, soil, sunlight in this case is various teams that are formed to be part of project team. It is now the responsibility of these teams to ensure that the seed grown with a high amount of responsibility grows at the desired pace and bear the right kind of fruits, in right time.
There are ways to make a project successful and more number of ways to find out excuses for failures. There is no project that does not encompass of showstoppers, critical or serious issues. Most of the senior team members are always prepared to come across any unwanted or untoward issues arising of a project and finding out suitable measures to overcome them. The top most priority of core project team is to take care of such untoward incidents and ensure a proper mitigation of such risks.
There are ways to ensure a project go fail and gradually you can get accustomed to it where no extra effort shall be required to do so. The top few ways can be listed as below:
1. Overlook troubles and hiccups in a project and thus find no ways out to recover through them.
2. Make no plans and if someone else does that effort, never take it seriously. It is not mandatory to adhere to the timelines marked in the plan.
3. No plans will also ensure no monitoring, follow ups, alerts etc. thereby making your life smooth and hiccups free.
4. Don’t rely on your people or processes to make it successful. Don’t let your team be guided in right direction to make a project successful. Also ensure no good processes in place to take people in right direction.
5. Never give a priority to your customer. Lead your product’s development in 180 degrees rather than in alignment of customer requirements.
There are more ways than mentioned above. It is not difficult for you to find out in real world.
Project execution comprises of various efforts done by team members. This becomes a pool of energy moving in the direction of making a project successful. More collated form of energies generates higher chances of success of their efforts.
Right form of energy in right direction at right moment of time with right level of thrust returns higher chances of success in its goals. Logical right mix of team member leads to timely completion of project tasks. An individual, a team, a project; all have their specific carbon footprint. What factors would mainly contribute in determination of carbon footprint of a project. Let us try indicating few of them as below:
1. overshooting budgets and expenses
2. delayed decisions
3. missed targets, deadlines and milestones
4. team losing focus, tempo, momentum and goals
5. No Learning from mistakes
All points listed above if go in affirmative direction, will lead to a higher level of carbon footprint in the project. The same can be reduced by negating the points mentioned above.
Do you feel physical presence of your team around you is important and is the only way to manage them or control them. Do you think that your team should report to you and keep you making feel important all the time because you are Project Manager and as per your perception you are one of the key pillars of your project?
If you think traffic police constable standing on a crossing and controlling traffic resembles the role of a project manager whose overall responsibility is to control teams, project and management; you might be right. Only thing is that you have to manage the show more tactically and less mechanically. Your movements have to take place more in mind rather than the physical ones.
Basically a project manager must be able to manage the teams which are far off, as effectively as the teams around. It is the way you find out to manage in an effective manner which need not be a proven and orthodox. It may be a totally new and innovative manner of handling your teams.
Technically an engineer these days doesn’t require going and inspecting a machine physically. There are tools and ways to manage remotely and quite effectively. This does not only saves time and energy but give a more economical leverage to shell out project completion in a highly productive manner.
This is in continuation from previous post…
3. Test Cases: Never underestimate product’s capabilities, customer’s expectations and development team’s performance. Besides all good factors, there are always chances of things going weird, not because someone intentionally wants it to happen but due to any kind of ignorance, miscommunication or misunderstanding. Build all kind of test cases to cover up the product testing completely.
4. Perform Testing as Prayer: Don’t keep a difference between the product testing that you perform and the prayer done for the supreme power. With a great amount of clarity in mind and set goals of delivering the best to customer, there are least chances of getting things going wrong.
5. No Gap with Development Team: Ensure that whatever you are doing is for the improvement of organization and not for the purpose of pinpointing anybody’s mistakes. Same should happen with the development team too. It must be very clear to them that test team is not there to point out their lack of knowledge but to find out leakages in the product so that there are no eruption of volcanoes at a later stage thereby causing higher amount of damages.
There are many more important factors that are required to be kept in mind but if above 5 points are well adhered to, probably the chances of winning the battle are higher.
Test team has an important role to play which leads to project success. It is said that the time required for development and testing should never be compromised. A small amount of ignorance at any of these two stages may lead to a big disaster at a later stage. This does not mean that all other stages are of lesser significance.
Although a significant amount of attention is given at all stages of the project but test team need to adhere to some important points which should not be overlooked or compromised in any case. Those important points can be listed as below:
1. Start with open and fresh mind: Every project has its own merits and demerits. It is good to carry on with the good deeds done during that previous project that made it a grand success but move on with a mission of overcoming the mistakes done during the last project that caused certain delays or hiccups. There has to be no regrets about any failures in the past and equally important is to forget any ill feelings about any of the team mates if project is desired to move smoothly and strongly.
2. Focus intensely on customer requirements: Don’t hesitate in performing a post mortem of each and every clause mentioned in the customer requirements document. Ensure that the document is well in place, complete in all respects, has been signed off by all respective and responsible representatives and is well documented in a manner that it is not going to create any kind of confusion among development and test teams.
—– to be continued/-
There are least chances of failure if you let life go as it is. Having no targets in life, no plans to execute, no aspirations to achieve, no dreams to live with and no ambitions can give you a trouble free time in life. Do you think it is true?
Real way of achieving success in any kind of project is not to lose hope and fight with all hurdles arising during a project. Overall if you see, project is a team effort and its success (or failure) cannot be assigned to a single person of the team. Team in a real sense is a combination of all complimenting and supplementing factors so that to lead, follow, execute, assist, drive, assign, plan, achieve, approve and provide resources.
Probably it is quite uncertain to predict that a project will run smooth throughout and will face no troubles of any kind during its any of the phases. It is practically impossible to believe it and claim at all about any kind of project sizing from very small to any big size. Troubles and hiccups are integral part of a project and that is why a project comprises of involvement of good amount of persons in the project team.
Project basically is a triangle with stakeholders, project executioners and customer at its three corners. Project deliverables, timelines, milestones, plans, meetings, targets are all ingredients that are the fillers of the triangle. Some of these ingredients are singularly connected to any one corner of the triangle; some could be jointly connected to two corners while rest would be linked to all the three corners of triangle. It denotes basically that more or less everyone is connected to the project at all points of time and get affected due to success or failure of project. Sometimes it could not end up in total failure of the project meaning that it might result into a final sign off but any unexpected delays during a project lead to loss in revenue, confidence and team momentum.
As long as project is running smooth and hassle free, it is harmonious and happy atmosphere around. But in otherwise conditions, it results into conflicts, disharmony and unhappy atmosphere. Who doesn’t want every project to be successful but still everyone faces some or the other challenges during its lifecycle.
Hey this is the last blogs post for the year 2011. Here is a list of my all blogs written during the year 2011 at ITKE.
Jan 12 2011 10:11AM GMT http://bit.ly/hL2AHA
Business Value And Software Product
Jan 12 2011 10:15AM GMT http://bit.ly/fKzupE
Business Value And Sustenance
Jan 13 2011 10:43AM GMT http://bit.ly/gt4xqr
Business Value And Its Consistency
Jan 13 2011 10:46AM GMT http://bit.ly/fBx0aw
Treat Bugs As Software Enhancers
Jan 17 2011 11:21AM GMT http://bit.ly/h4aUUM
Consistent Delivery Does Matter In Case Of Project Manager
Jan 17 2011 11:25AM GMT http://bit.ly/fENhBw
Project Management Lessons From Cricket Coach John Wright
Jan 19 2011 11:45AM GMT http://bit.ly/f0qQhe
Ten Facts About Product Backlog
Jan 19 2011 11:49AM GMT http://bit.ly/enJsL8
Backlog Monitoring Helps Greatly In Accurate Estimations
Jan 28 2011 11:17AM GMT http://bit.ly/f0adVq
Lean Organization Architecture And Project Management
Jan 28 2011 11:22AM GMT http://bit.ly/ek66Xj
Key Difference Between Lean And Agile Testing In Project Management
Jan 31 2011 10:41AM GMT http://bit.ly/fhK4ur
Some Teammates Make A Big Difference
Jan 31 2011 10:45AM GMT http://bit.ly/f6BDoO
Quality Control Of Bug Report
Feb 3 2011 10:58AM GMT http://bit.ly/gP5vIn
Project Management Versus Change Management
Feb 3 2011 11:01AM GMT http://bit.ly/g7cXsX
Project Management And Total Involvement
Feb 4 2011 11:07AM GMT http://bit.ly/gN260E
Project Management And Project Strategy
Feb 4 2011 11:12AM GMT http://bit.ly/ij7Ixo
Business Process Management And Business Process
Feb 7 2011 10:57AM GMT http://bit.ly/ehIZ4f
Different Training Methodologies During Project Management
Feb 8 2011 12:02PM GMT http://bit.ly/fW3JFz
Project Management And Team Management
Feb 8 2011 12:06PM GMT http://bit.ly/hxx6Ir
Five Golden Guidelines While Heading For A New Customer Win
Feb 9 2011 10:43AM GMT http://bit.ly/fuGJhY
To Choose Between Initial Quality Expense And Later Product Interruptions
Feb 9 2011 10:47AM GMT http://bit.ly/gOMN6X
Is Quality Expense Or Income For Software Development Organization
Feb 11 2011 11:42AM GMT http://bit.ly/fe3T6J
How Important Is Project Dashboard For Project Management
Feb 11 2011 11:51AM GMT http://bit.ly/fZCdi2
Compliance And Testing Coverage Against Project Specifications
Feb 23 2011 11:48AM GMT http://bit.ly/gDFqrA
Innovative Project Management And Project Harnessing
Mar 4 2011 11:16AM GMT http://bit.ly/dQwAT6
Good Service And Good Product Alone Does Not Drive Business Growth
Mar 9 2011 11:40AM GMT http://bit.ly/ekdGB4
Never Panic If Captain Departs From Ship In Mid Of Troubled Waters
Mar 9 2011 11:48AM GMT http://bit.ly/fMciCy
At No Stage You Can Claim Project As Fully Matured
Mar 11 2011 12:37PM GMT http://bit.ly/gCzfkH
Thoughts On Recruitment And Employee Retention In Software Company
Mar 11 2011 12:40PM GMT http://bit.ly/dSHSrb
Outsource Or Recruit Or Hire Contract Is a Big Question In Software Project
Mar 14 2011 11:28AM GMT http://bit.ly/efim7L
Project Growth And Organization Work Culture Progress Hand In Hand
Mar 15 2011 12:04PM GMT http://bit.ly/i9IkRU
Outsourcing Or Hiring Is All Situational Game
Mar 16 2011 10:29AM GMT http://bit.ly/hwD4CB
Who Actually Drives Your Project
Mar 18 2011 9:46AM GMT http://bit.ly/h1Etia
Project Management And Innovation
Mar 21 2011 11:35AM GMT http://bit.ly/hOvt7o
Five Pillars Of Quality Drive
Mar 29 2011 11:46AM GMT http://bit.ly/gIESvR
Check If Project Manager Fits The Bill Or Not
Mar 29 2011 11:52AM GMT http://bit.ly/gp2gd8
A Classic Sad Tale About Project Management
Apr 5 2011 9:48AM GMT http://bit.ly/fsyhH9
Constituents Of A Test Plan
Apr 7 2011 11:10AM GMT http://bit.ly/hszPKZ
Steps For A Process Head To Become Innovative
Apr 7 2011 11:16AM GMT http://bit.ly/eO9mvA
Limitations of QC
Apr 13 2011 10:07AM GMT http://bit.ly/fWTrV4
When And Why Build A Test Plan
Apr 13 2011 10:12AM GMT http://bit.ly/gvdRex
If Following Traffic Rules Is A Process There Are Many Violators On Road
Apr 16 2011 9:22AM GMT http://bit.ly/fQBoKn
Most Of Software Delays Are Because Of No Proper Requirements Gathered
Apr 16 2011 9:27AM GMT http://bit.ly/hOLuob
Good Process Quality Can Put Appropriate Checks
Apr 25 2011 5:05AM GMT http://bit.ly/guySiN
Lean In Software Project Management
Apr 25 2011 5:16AM GMT http://bit.ly/eyH73B
Six Sigma Can Be A Catalyst To Project Management
Apr 26 2011 11:29AM GMT http://bit.ly/e1mJYo
Success Failure Product And Techies
Apr 27 2011 10:52AM GMT http://bit.ly/gqaAAk
Five Testing Angles For A Tester To Perform Efficiently
Apr 29 2011 9:54AM GMT http://bit.ly/lIMIdi
Segregating Customer Desire Need And Greed Carves Project Success
May 12 2011 11:50AM GMT http://bit.ly/iK8Hlo
Some Thoughts On What Makes Software Product Lose Credibility Or Touch Sky Heights
May 12 2011 11:56AM GMT http://bit.ly/iWldAC
Six Standard Norms Customer Seeks In Software Product
May 14 2011 8:22AM GMT http://bit.ly/itu8Fn
Four Critical Places To Ignore Quality And Invite Disaster In Your Software Project
May 14 2011 8:29AM GMT http://bit.ly/ilyp3j
Why Quality Manager Cannot Be Project Manager And Vice Versa
May 17 2011 9:59AM GMT http://bit.ly/j79z1L
Five Requirement Based Face Saving Statements Against Customer To Hide Shortcomings
May 18 2011 12:20PM GMT http://bit.ly/7AgpBz
Dynamic Team Vs Static Team
May 23 2011 10:49AM GMT http://bit.ly/la7fZB
Project Team Sizing And Optimizing
May 23 2011 11:31AM GMT http://bit.ly/lot4hM
Understanding A Complex Situation Is First Mantra Of Success For A Project Team
May 24 2011 11:03AM GMT http://bit.ly/mPsOMl
Positive And Negative Traits Of Project Say A Lot If Analysed
May 25 2011 11:20AM GMT http://bit.ly/ld7YiD
Three Initiators To Lead A Team Without Being Team Leader
May 26 2011 12:24PM GMT http://bit.ly/jkvjZe
Test Environment Versus Live Environment
May 30 2011 11:00AM GMT http://bit.ly/moa0kF
Four Simple Tools To Enhance Project Success Rate
Jun 24 2011 6:06PM GMT http://bit.ly/imDPnw
An Insight Of How To Turn A Good Developer Into A Good Tester As Well
Jun 24 2011 6:37PM GMT http://bit.ly/meMxKa
Testing And Project Progress Go Hand In Hand
Jun 25 2011 6:15PM GMT http://bit.ly/mILf4K
An Approach To Ascertain Leverage Of Developing Bugs In Place OF Neat Software Product
Jun 25 2011 6:39PM GMT http://bit.ly/jM9E0T
Each Bug Has An Element Of Cost Associated With It
Jun 26 2011 6:23PM GMT http://bit.ly/mRuibG
My Earlier Pains About Testers And Developers Are Still Intact
Jun 26 2011 6:51PM GMT http://bit.ly/lWJiC5
An Approach Of Project Cost Estimation And Another For Software Testing
Jun 27 2011 6:24PM GMT http://bit.ly/mMxTxK
Why Software Testing And Importance
Jun 27 2011 6:42PM GMT http://bit.ly/k59DP8
If Doctor Starts Curing His Patients Like A Programmer
Jun 29 2011 7:40AM GMT http://bit.ly/imZdtr
A Checklist Is Must To Ensure Complete Coverage Of Software Testing
Jun 29 2011 8:09AM GMT
Five Good Blogs On Testing
Jun 30 2011 5:38PM GMT http://bit.ly/mHmCUG
Seven Blogs In A Row On SDLC Software Development Life Cycle
Jun 30 2011 5:48PM GMT http://bit.ly/jhTPbQ
Software Requirement Gathering Is Most Prime Stage Of Project
Jul 11 2011 2:27AM GMT http://bit.ly/oYSvCC
Testing Methodology Has To Vary For Development And Support Phase
Jul 11 2011 2:37AM GMT http://bit.ly/pV04kW
Implementation Phase Is Acid Test For Software Project Success
Jul 14 2011 5:59PM GMT http://bit.ly/p4Yz8r
Test Strategy Can Not Be Same For Different Software
Jul 14 2011 6:05PM GMT http://bit.ly/qHKvAK
An Extra Mile Of Testing In Initial Phases Saves A Lot Of Project Fuel
Jul 15 2011 4:55PM GMT http://bit.ly/oAg6ut
Eight Blogs On Project Manager
Jul 15 2011 5:02PM GMT http://bit.ly/pGB424
Nine More Blogs On Project Manager
Jul 24 2011 2:03PM GMT http://bit.ly/nIIgdP
Seven Blogs On SDLC Software Development LifeCycle
Jul 24 2011 2:18PM GMT http://bit.ly/oHcSNA
Six Sins At Product Development Stage That Can Lead Project To Disaster
Jul 26 2011 5:17PM GMT http://bit.ly/qHkEpo
Six Blogs On Release Management
Jul 26 2011 6:07PM GMT http://bit.ly/oYjr1I
Sixteen Blogs On Identificaiton Of Customer Requirements
Jul 31 2011 2:36PM GMT http://bit.ly/p56V3I
Twenty Nine High Fiver Blogs On Project Management And Quality Assurance
Jul 31 2011 6:42PM GMT http://bit.ly/re6yzG
A Dozen Of Super Sixers On Project Management And Quality Assurance
Aug 7 2011 7:40AM GMT http://bit.ly/og91RQ
Everyone Is A Born Project Manager
Aug 7 2011 8:00AM GMT http://bit.ly/pPJHtc
Quality Is Not Something We Are Not Aware Of In Our Day To Day Life
Aug 15 2011 6:28AM GMT http://bit.ly/oqjydr
Dream Based Projects Prone To Fail In Lack Of Vision And Clarity
Aug 15 2011 6:35AM GMT http://bit.ly/pjGtMt
Projects With Least Involvement Of Sponsors Do Not Do Well
Aug 18 2011 5:50PM GMT http://bit.ly/pgdaFS
If Sponsor Is Weak It Is Better To Drop Project
Aug 18 2011 5:58PM GMT http://bit.ly/qgzq6s
Project Starting Without Project Plan Is Like Driving With No Route Knowledge
Aug 22 2011 4:47PM GMT http://bit.ly/nGGmZA
Project Ends With Either Win Win Or Lose Lose
Aug 22 2011 4:52PM GMT http://bit.ly/r2WSZx
With No Measurement Of Plan Project Failure Is Not Too Far
Aug 26 2011 5:28PM GMT http://bit.ly/nZm5ml
Quality Speaks: Product Review: Wondershare Video Converter For Mac
Aug 26 2011 5:34PM GMT http://bit.ly/oIbKTT
Quality Speaks: Product Review: DRM Removal From iSkysoft
Aug 31 2011 1:10PM GMT http://bit.ly/qUYGGB
Project Estimations Is Not Management Ballgame
Aug 31 2011 1:12PM GMT http://bit.ly/rpkOOu
Ten Major Constituents Of Project Estimations
Sep 5 2011 4:20AM GMT http://bit.ly/nFgpPJ
Product Review: Geosurf ™ Secured Private Local Surfing Without Being Local
SEP 5 2011 5:33AM GMT HTTP://BIT.LY/PJAW9Y
Software Review: A Software Development Company For Real Estate Business
Sep 8 2011 6:23PM GMT http://bit.ly/omHSgL
Two Products Reviewed: Mac The Ripper And iMedia From iSkySoft
Sep 14 2011 11:48AM GMT http://bit.ly/nznZVa
Quality of A Product Says Everything about Success: MTS Converter for Mac
Sep 14 2011 7:21PM GMT http://bit.ly/obEluH
Can My Project Management Office Learn From This Kitchen Friendly Website
Sep 19 2011 8:56AM GMT http://bit.ly/q0GiEr
iTube Studio for Mac is Incredible
Sep 20 2011 10:49AM GMT http://bit.ly/q9L7Oe
When You Want To Outsource A Facebook Application Development Company
Sep 20 2011 6:33PM GMT http://bit.ly/p3S7DY
Do You Need A Customer Appreciation And Retention Expert
Sep 21 2011 5:07PM GMT http://bit.ly/qtuiL1
Have You Tried The Power Of DVD Ripper For Mac
Sep 29 2011 3:59AM GMT http://bit.ly/pcjANb
How Often A Project Manager Goes Out Of Shell
Sep 29 2011 4:29AM GMT http://bit.ly/r5aC6B
Why Is It Important For QA Head To See Other Products
Sep 30 2011 5:59PM GMT http://bit.ly/okPxxt
Xilisoft iPad Magic 4 for Windows – A Real Magical Experience
OCT 5 2011 12:06PM GMT HTTP://BIT.LY/MVKVJF
Private Label Solutions Suite Offered By Solution Union
OCT 6 2011 3:32AM GMT HTTP://BIT.LY/NR7UKN
When Did You Last Take Your Information Security Awareness Program
OCT 15 2011 6:56PM GMT HTTP://BIT.LY/NJUAHG
How About Some Entertainment During An Overseas Project Implementation
OCT 16 2011 6:50AM GMT HTTP://BIT.LY/PDGV0H
An Innovative and Unique Project in Electronic Recycling and Other eCycling Services
OCT 19 2011 6:16PM GMT HTTP://BIT.LY/R0P5GM
Something About Private Label Products For Getting Quality Valued Products
OCT 21 2011 6:54PM GMT HTTP://BIT.LY/QNM2UN
Are You Aware About Quality of Tippmann
OCT 22 2011 4:40AM GMT HTTP://BIT.LY/PHWM5C
Solid Management and Reporting Tools for Asset, AD, DC and Computer Management
OCT 22 2011 5:37PM GMT HTTP://BIT.LY/N2NFCS
Should We Not Learn Some Project Management From These NHL Teams
OCT 22 2011 5:47PM GMT HTTP://BIT.LY/O1K1SQ
Can A Project Manager Think Of Customer Comfort Like This
OCT 22 2011 5:55PM GMT HTTP://BIT.LY/QOFCK6
Beautiful and Powerful Features of Office Tab
OCT 23 2011 4:47PM GMT HTTP://BIT.LY/PUGGKH
iSkysoft Video Converter for Mac is Enormously Wonderful Tool
OCT 26 2011 5:12PM GMT HTTP://BIT.LY/RTSPIM
Do You Help Your Project Get Slim and Energetic Like This
OCT 26 2011 5:58PM GMT HTTP://BIT.LY/TUQ1RP
Quality Review of a Quality Service Company in Order Fulfillment
OCT 29 2011 12:58PM GMT
Are You Ready to Learn Computer Languages?
OCT 29 2011 5:55PM GMT HTTP://BIT.LY/VY71NN
Exploration of a High Quality DVD Ripper
OCT 29 2011 6:07PM GMT HTTP://BIT.LY/TZLWSQ
A Powerful DVD Creator to Burn iTunes Movies to DVD
OCT 29 2011 6:22PM GMT HTTP://BIT.LY/TG6MO2
A Glance At One of the Best Video Converters
NOV 7 2011 5:03PM GMT HTTP://BIT.LY/VPS5SS
Top Twenty Pitfalls in Project Management
NOV 7 2011 5:15PM GMT HTTP://BIT.LY/S1SAPM
Why Does A Project Manager Need A Break From the Project
NOV 15 2011 5:36PM GMT HTTP://BIT.LY/SERQK1
ERP implementation in a Greenfield project
NOV 20 2011 1:57PM GMT HTTP://BIT.LY/SDSWKS
It Doesnot Matter SAP or BaaN more than Implementation Process
NOV 20 2011 2:52PM GMT HTTP://BIT.LY/TQJRME
When Top Management Becomes Helpless During Implementation
NOV 24 2011 6:13PM GMT HTTP://BIT.LY/USAZE2
It is Business Functions that Spoil the Show Mostly
NOV 25 2011 6:54PM GMT HTTP://BIT.LY/S4G0YU
Reducing Project Cost can Itself be a Project
NOV 25 2011 7:40PM GMT HTTP://BIT.LY/RDHE0L
Project Stakeholders are Project Watchmen or Drivers
NOV 25 2011 8:13PM GMT HTTP://BIT.LY/VTDV0M
Accelerating Your Project Does Not Need You To Be A Magician
NOV 27 2011 6:55PM GMT HTTP://BIT.LY/UQGQRL
A Rude Project Manager Cannot Have Caring and Connected Team
NOV 30 2011 7:21PM GMT
The Size of Team Decides about the Project Success Well Not Exactly
NOV 30 2011 7:47PM GMT HTTP://BIT.LY/TURFFG
Post Project Stage is Beginning of a New Project In Fact
DEC 24 2011 8:26AM GMT http://bit.ly/shXg2y
Evolution of Team Work in Project Management
DEC 24 2011 8:34AM GMT HTTP://BIT.LY/UUTSWN
What Makes a Project Successful
DEC 25 2011 7:15PM GMT HTTP://bit.ly/rx8F3r
TV Channel Browsing and Project Management
DEC 25 2011 7:27PM GMT HTTP://BIT.LY/RRXNYP
If the Water is Still There is Something Wrong in the Project
DEC 26 2011 7:15PM GMT HTTP://BIT.LY/UPPCQY
Can a Tester be Called Anti Coder
DEC 28 2011 5:15PM GMT HTTP://BIT.LY/VIJYLS
Testers are Either Friends Or Foes of Project Managers
DEC 28 2011 6:12PM GMT HTTP://BIT.LY/VFCVFC
7 Ways in which a Tester can Help in Removing Ambiguities in Business Requirement Document
DEC 29 2011 6:11PM GMT HTTP://BIT.LY/SC5MWB
Benefits of Using Correct Vision During Product Development
DEC 29 2011 6:20PM GMT HTTP://BIT.LY/W003QM
A Customer Can Be Blindfolded But Not For A Long Period
DEC 29 2011 6:31PM GMT HTTP://BIT.LY/SLPFCJ
Try Swallowing the Pill Smilingly That You Made For Your Customer
DEC 29 2011 6:54PM GMT HTTP://BIT.LY/UVV44V
A Rich Product Does Not Require Long Praises To Customer
Product benefits, if really are there, in it, need not require any long explanations to the customer. Mostly a product rich in features and functionality do not require long introductions. Rather if a product is being tried to be sold with extra bounce of praises, it should be taken as a word of caution. A deep probing or investigation in the product in terms of examining what is being told about it may reveal the truth.
It may give both types of experiences when you buy a new product. Logically whenever we buy a product we already have some level of expectations set in our mind for it. If product performance and functionality goes beyond that level, it touches mark of excellence as per our perceptions. And if it stays lower than that level, it might become a nightmare during its usage, depending on how low or high it is.
Higher expectations, mostly, are set by product selling company while presenting the product qualities at the time of initial discussion of cracking the deal. Usually at this juncture, product is either not ready or is ready not as per the customer requirements. So all kind of dreams are shown to the customer when customer puts forth his requirements and all sort of promises are also done to build any kind of functionality whatever is being expected.
And then it is two kinds of vendors, one who do whatever needs to be done, to build in whatever has been promised. And there are ones who don’t bother whatever has been promised and try to cheat by presenting a wrong picture.
It is very tough to swallow the same pill that you manufacture for other when the need is to cater to yourself with it. A product can be counted as product when it generates, not customers, but admirers. It is in real sense a best product, when customer praises about it in front of hundreds of people across the board and highlights about its hidden benefits that would have been passed as a bonus.
A number of customers buy a product bundled with lot of promises when it is sold. But in actual it starts giving pain to the end users and hampers business rather than acting as a supporting or boosting function. A product, if rightly developed, to cater to a business, need to act as a partner of customer in a sense that it helps in lowering pains and increasing gains.
When you develop a product for your customer, keep this thing in mind that whether the customer is going to realize pains after some time or will face bundles of sweet surprises hidden in the product. If the product crosses the level of stipulated of perceived ease of functioning and start giving better results during its usage, it definitely is bound to get full praises from the customer.
A customer during product development might not be able to assess the sincerity and integrity factor in a deeper manner but it can’t be hidden during implementation stage and post-handover stage. Product team or organization may feel happy if the ignorance or non-serious attitude embedded in the product during development stage is exposed post-implementation, post-handover and post-payment stage but that is still, in reality, a loss in business for the product selling organization.
This is mostly taken for granted sort of factor on product side and is almost never realized that one such instance may create a higher amount of loss in business than otherwise. The life is not as simple as it is supposed to be. It cannot be taken for granted for doing a serious kind of stuff in life. Best way of delivering a great product to customer is by having a highest level of seriousness right from the beginning.
One way of developing the product for customer is by keeping in mind as if the product is being developed for your own use. Once product is taking some shape, have a right kind of assessment, whether you would like to buy this product at the price you plan to sell it to your customer?
6/6 vision is not bad. But having 6/6 and not having a capability to look beyond is something that degrades the value of even the correction vision. It is like something valuable that you possess but are not able to get the best out of it, ever! Planting is one time activity, but it is watering and caring that helps in growing the plant. That does not mean that the later could have happened without former activity. It is sequential having both the activities in prime important category.
Testers do have a different blend of vision. They are bound to develop that extra edge of visioning through which they are able to look at the product more from a customer perspective rather than the vendor or product developer perspective. A tester is required to virtually slip into the shoe of end user so as to assess the capabilities and functionality of a product that is going to be delivered to them after passing through QC. Technically and functionally, a product must be able to cater to customer requirements to make business functions smoother, trouble free and less time consuming with higher level of accuracy.
That is what is about a product should be. One should understand, the earlier the better, that which situation is more important in business – merely selling the product by blindfolding or faking the customer or giving a state of the art product to the customer which in turn incurs manifold business through word of mouth and otherwise. Usually a good product even if sold at a lesser margins give greater benefits in longer term.
A tester always has an extra edger over developer in terms of looking at the product or requirements through a critique’s angle. If the requirements or product is not analyzed in a different manner, it might look straight, precise and up to the mark at times. The moment you go deeper or look at it through a different angle, the whole straight thing may appear as the most complex puzzle on this earth.
That is what is important to know that involvement of tester in the beginning gives lot of benefits to the project and various teams involved in the project. Tester or test team when goes through the business requirement document, would like to understand following points:
1. Have all requirements which are business critical and can be catered through development of business application been taken or not.
2. Does it cover the complete business cycle thereby catering to all major business functions
3. Does it cater to main business transactions
4. Does it cater to top management requirements, dashboard and analysis
5. Does it tend to ease out end user’s life or intends to make it more complex
6. Is there a buy in from top management
7. Is system being imposed on users or functions; or is being imposed without them getting involved
This is not the only list that can be a checkpoint for test team. There could be more points, sometimes depending on a typical kind of business having some very unique kind of requirements which are not required in general kind of business.
There are different kinds of project managers – those who take testers as a threat and thus treat them as foes and those who take testers are friends and hence always welcome them to put hands on the product in pipeline. Neither of the two is a strange factor. Both scenarios are natural and realistic.
If the situation is former, it becomes quite tough for testers to break the ice. It is not the question of just putting your hands on the product but also a good amount of cooperation and alignment is required from the development team. Without understanding business requirements on the basis of which the product in question has been developed, it is impossible to test the product. It is something like deciding to ride on a bicycle without knowing about the destination, road condition and distance to travel. Without knowing about the exact functionality requirements, it is next to impossible to test a product.
But logically, if you see, those project managers who treat testers as a threat lack confidence in themselves, their team and the product developed. Though this might not be true if some amount of probing is done in such cases, but it is the project manager that needs to introspect on such kind of behaviour. It could merely be lack of confidence and knowledge of project manager only that forces them to develop such atmosphere of hide and seek. The development team and product might be well in place! And the project manager would have placed them in a poor situation.
Shall we treat tester as a code destroyer? If on one hand a developer develops a code, a tester always tries to find out the holes in the pot. That is where a conflict on personal level originates when a programmer or coder takes it too personal by getting faults being found out in the code written by him. But internally a coder knows very well that the whole exercise of bug finding by tester is for a good cause that is going to benefit all involved in the chain.
Howsoever a programmer is treated as a constructive builder; he is prone to inherently bring in some bugs in the code. Even if a code is sure about some leakage in the code, he would not regret in falling love with his style of coding. That is where a jealousy begins when the code undergoes post-mortem by testing team. As any human being, we prefer to listen to the praise for our creation rather than somebody criticizing it.
Usually why a coder doesn’t have flair of a tester. Does it mean that tester is a saviour for coder? Tester is able to look at a code through a critic’s angle, and only then is he able to find out the shortcomings in the code. But on the other hand, a tester is supposed to possess a good knowledge of product and business requirements behind the building of that product so as to examine the product in right manner.
Probably coder and tester are made for each other to compliment each others’ efforts.
Still water leads to getting things rotten or stale. Flowing water keeps it fresh and healthy. Nobody
likes a project in a standstill position. It needs to be in a ‘move-on’ condition all the time till it reaches
its final position of successful deployment and sign off. Who does not want their project to finish in
time, successfully and without hiccups? But everyone knows it happens very rarely. What could be the
Why is it that among all kind of plans and monitoring activities a project faces delays, hiccups and
troubles? At a broader level a project team can be divided into following categories – planners,
executioners, monitors and decision makers. All four are very important components of a project. A
right mix and timely action from each of the component makes a larger sized positive impact on the
project and vice versa. Higher mix of planers and lesser count of executioners will lead to good amount
of thinkers but lesser amount of doers. Similarly lack of visibility or presence of decision makers in
a project will lead a project to a standstill. And that is where the stagnation and rottenness begins.
Monitoring gains momentum in the project and lack of it acts as a decelerator.
Actual need of presence of eagle’s eye is very important in a project. Someone has to take that role and lead in the project by smelling, sensing and foreseeing ‘Still Water’. This person must have the power to raise an alarm in time and activate the trigger for taking right action by right members of the team. A
universal sync among prominent team members is a must.
I had some spare time that I planned to invest in watching some useful program on TV. Starting with
channel one, moving on to next channel and trying to figure out how useful the coming program would
be; I reached to the higher limit of double figure digit of channels but ending up to nothing of my taste
so far. By this time I had spent almost 20 minutes while switching over from one channel to another and staying there for a while in trying out to figure out if something good or bad was there.
That is what happens in a project. Project starts, initiation activities are performed, teams are formed,
plans are made, methodology is adopted, project moves, milestones are monitored and delays are
justified. Actually does it move as it should move or things keep slowing down whilst during assumptions of them moving at right pace? Sometimes project owners are not able to catch hold of the things in right time. And by the time they become aware of the situation, probably it already has resulted into cracking of the egg. In this case the egg has not cracked in a natural manner but by mistake, done by someone in the team.
Point is not to zero down on the mistake doer, but to catch hold of the mistake and get it rectified at the earliest. It is never possible to rectify a mistake until it has been identified as a mistake and someone takes charge of it.
After half an hour I realized if I had browsed newspaper page that gives channel wise programs
beforehand, I would have headed to the right channel in right time without wastage of much energy and time.
No project is executed and completed without encountering troubles and hiccups. If that could happen
plans were not required. There were no monitoring, follow ups, alerts, alarms; if the projects were there to run smoothly and end up in time with success all over. Is it people or process that makes a project successful?
The same set of people without a good execution plan in hand and well defined processes to drive the
project, will never be able to make a project successful. Similarly the same set of execution plan and well defined processes in place will never end up in completion of a successful project in all places under all kind of circumstances.
So what is it that makes a project more problematic? Or what makes a project sail smoothly on troubled waters. Is it the people who are real driver of project or is it the well defined charter or project that makes it more successful. Even in presence of both, there are good amount of examples of failed projects even in large establishments. Does it mean that there are some more driving forces than the process and people that can win or lose a project success?
Actually it is very difficult to pin down the exact percentage of various factors that are responsible
for the success of a project. But is it a right mix of management, approach, system, people, process,
methodology, plan and control mechanism that makes it successful.
Did I mention that passion and fire in the belly are other two hidden ingredients that play a major role in the whole journey?
Depending on situation and demand of a project, teams are formed in accordance with the project requirements. Earlier when there was no concept of team it was found that based on tasks assigned to individuals in an organization, small teams used to get evolved automatically since in any kind of task, an individual is bound to seek assistance from internal or external member of the organization depending of the kind of task assigned.
Somehow some knowledgeable person in an organization would have studied the behaviour of different functional verticals when put under higher amount of work stress. A major activity that takes place under such circumstances is delegation of authorities, job allocation and team formation. When time is less and more tasks need to be performed, a best way to cut the long rope short is by removing unnecessary steps of the process which otherwise in normal situations would make a lot of sense and equally justify their existence.
Delegation of authorities and power is a strong tool when there is or are certain amounts of projects that need to be finished in very short duration. Though it does not mean that planning or monitoring is not required or such projects can survive without the two. What it means is that a more accurate and concrete form of planning or monitoring is required in such situations.
Post project is not the closure of a project. It is generally the beginning of the second innings of the project in which end users start using the product in actual and face the real fight. During project implementation phase, the challenge is not much as most of the cycle is done in presence of the functional and technical experts of the implementation team. But what happens when all the team is gone and support is not at a hand’s distance.
It is the stretch which is most painful in fact. No support on seat. Actual data to be done in the product and management expects some real bunch of useful reports. The acid test is for all who work on the product.
But it is during this stage that the ruggedness of product gets introduced or the weakness of the product gets exposed. It is usually this stage that the product is either absorbed in business for a long run or gets discarded even after a big amount spent on it.
You need to build a team for any of your project. None of the sizeable projects can be done by a single person. Building a team is not an easy task, as it involves all kind of right skills in the Project Manager to perform a right kind of permutation and combination to choose perfect match of team members. All team members with same or similar kind of members. Exact sizing need to be done with versatile and variable set of talents so as to build a mix of compliments and supplements kind of people in the team.
Why same kind of team members would not work well. Reason for this could be many but I would like to have opinions from readers.
An unconnected, isolated and purely professional project manager cannot and should not expect a connection between him and his team members on personal grounds. If this doesn’t affect the project manager it could be ok for his sake but as far as business and work is concerned, it is a well proven fact that a personal connect between a manager and subordinates delivers a potentially substantial amount of throughput in work. A project manager with rude attitude among or towards his team members does not do a good job for his project and management.
A personal connect with the organization grows with the help of its employees. After all organization is nothing but a collective and organized group of people. A proper tuning and harmony engages employees more with their organization and with each other in the organization. If this level is attained in the organization, its employee turnover is less than average as per industry standards. It has been seen that it is not the workload that makes people leave an organization but the personal connect with the organization that binds them with the organization in absence of which nobody stays in the organization for long.
Even at the time of appointment these things do matter for a newly introduced employee to make up his or her mind for a long term stay. Many a times interviewing managers do not convey the right message about the culture of their organization and hence increase the probability of losing high potential prospective employees.