5 Rules for Project Success: Analogy with Cricket

Let it be T20, Fifty Over or Test Arena we have few basic rules that must be observed to succeed in any format of the cricket match. Same goes with Project. Let it be small project, module or a program some basic rules must be followed to successfully complete and deploy a project.

You must be amazed that many success rules can be compared and understood with the basic rule of cricket:

Rule 1: Set clear goal and plan each session/innings realistically

In any cricket match, each team has clear goal (Considering both scenarios – Fielding first or batting first). They also come up with the plans to achieve the goal.

But most importantly the goals and plans are realistic. Coach, captain and team analyze the scenarios and environment and accordingly create strategy. It is easy to say that in T20 game if we score 300+ runs batting first, we would be clear winners. But is it realistic?

Same goes with the Project. Project Manger/Business Analyst must analyze the scenarios, constraints and accordingly come up with the realistic strategies and project Plan.

Rule 2: Opponents are not to help you win!!!

Like in any other game we also have opponents in cricket. We need to plan how to overcome their strategies that they have planned against us.

In Project, Opponents can be competitor companies, support functions/ departments, “To be” members who couldn’t make to the project. Project Manager/Business Analyst must also consider these factors during planning and strategizing for project.

Rule 3: Sachin is Retired hurt on 49*……what next?

Assume that for a cricket match management and captain has done excellent plans. But in actual match, what if our main bowler could not perform? Our star batsman is injured retired hurt? It rains and pitch conditions change? Can captain declare that there were many changes which were not considered in start so the match should be declared cancelled or draw? Captain must have Plan B and Plan C for overcoming such risks which are commonly observed in any match. [Now I am not taking of an unanticipated risk where it starts to downpour in the month of December in Mumbai Match].

Similarly in any project, Project Manager must also have to plan for the anticipated risks that can usually arise in the middle of implementation of project. It is mostly observed that more the risks anticipated and planned in start more are the chances of the project being successful.

Rule 4: Cricket is Team Game; so is the Project:

Excellent performance from one player does not ensure win for a team. If “Team” performs well then only a match can be won. Same goes with Project. Project manager must allocate tasks smartly to the team members. In turn team members must feel themselves responsible for the allocated tasks and try to achieve the same in best way as possible.

Rule 5: Umpire is never wrong:

No player is allowed to argue with umpire. The decision of umpire is final and binding to all.

Same goes with project. Project sponsor / client decision is binding. PM should avoid argument with the client but plan or re-plan project based on any changes which client might come up with between the projects.

It is said in the game of cricket – Match is not over till last ball is bowled. Similarly in a Project, Project manager must not lose hope till the project is finally deployed on Production.

About Author:

Saurabh Kane is a consultant in Systems Plus Pvt. Ltd. Within Systems Plus, he actively contributes to the areas of Technology and Information Security. He can be contacted at: saurabh.k@spluspl.com