5 Tips for IT Project Success

"This isn't what we wanted!"

"What you have built is not user firiendly!"

"My Team hates what you have built!"

Sounds familiar! According to “Improving IT Project Outcomes by Systematically Managing and Hedging Risk,” a 2009 IDC report by Dana Wiklund and Joseph C. Pucciarelli, 25 percent of IT projects fail outright. Meanwhile, 20 to 25 percent don’t provide ROI and up to 50 percent require material rework.

By categorizing documented causes of IT project failure, a majority—54 percent—are attributed to project management. Surprisingly to some, technical challenges are the least-cited factor at 3 percent.

Here are 5 simple tips to ensure you deliver a successful IT project:

1. Focus on "Why" and "What" before you answer "How" :

Always put Business needs before technology! Work with "Business Process Experts" to understand current processes and systems. Listening is key here. Watch out for their "pain areas". Document your understanding and get it signed off by Business Process Experts and Project Sponsor. Majority of projects fail when you try to retro-fit business needs to the technology you have in mind to deliver solution

2. Get the Solution Design validated before you start build :

Once you have business requirements nailed down, it's time to go to the drawing board and convert them into a Solution Design. This is where you should call out the technology you will be using to develop the solution. Make sure you get Project Scope, Delivery milestones and timelines agreed with Business stakeholders. This will help you address "Scope creep" and "business expectation" issues later on in the project.

3. Communication Strategy :

A well defined (and executed) Communication Strategy is must for any IT project success. Make sure you identify your stakeholders across functions (Business, IT, Human Resources, Compliance etc.) depending on project at hand. Use standard communication template with clear bullet points to communicate your message. Do not leave anything for assumption!

4. Testing :

Ensure you involve Business users (and wherever possible have them write test scripts). This is critical because Business Testing should test what the system should deliver as per business processes and not just test the "happy path" that developer wants tested. Maintain a clearly documented defect/bug log and provide regular updates on bug fixes. Have a clearly documented (and Business agreed) System Acceptance Criteria to avoid ambiguity around product delivery to Business

5. Post Go-live Support :

On the system go-live date, make sure Business users know whom to reach out to for support. Have System Super Users do floor walk and assist users with "How - To" questions and report system issues. Maintain "Frequently Asked Questions" and "Issues Reported" log. Don't get overwhelmed by questions/issues! There will always be teething issues in first few weeks of project/product delivery.

This is, by no means, an exhaustive list of tips as each project will have it's nuance. However, basics always work! Wishing you all successful project delivery!