Remember the silence?
© Copyright Frank D. Kanu 2000-2008
Remember the
Imagine yourself announcing:
The most common problems When Your IT Project Is Late, Over Budget, and Looks Like It’s Never Going To Work are:
Technorati (All Links are external): bad reputation budget bugs communication communication breakdowns confusion control considerations destined due consideration enjoy the silence extra time hick ups late not working over budget program tests project project management protocol quality control remember the silence standards testing business it leadership management
silence
when you announced the last project would come in late?Imagine yourself announcing:
“The next one will be done early.”
Enjoy the Silence!
The most common problems When Your IT Project Is Late, Over Budget, and Looks Like It’s Never Going To Work are:
1. Not Enough Time
2. Open the Lines of Communication
3. Testing a New Program in the Production Server
4. Inadequate Testing
5. Pressing the Budget Too Tight
6. Never/Rarely Checking the Progress of the Project
7. Not Reviewing Existing Standards
2. Open the Lines of Communication
3. Testing a New Program in the Production Server
4. Inadequate Testing
5. Pressing the Budget Too Tight
6. Never/Rarely Checking the Progress of the Project
7. Not Reviewing Existing Standards
Solve these and other common project management hick-ups by:
- Give it more time. This vital step must be given due consideration. Adjust your schedule as needed, and you’ll find the rest of the process goes much smoother. Yes, you have to make it to market before your competition. But if you make it to market and your product is filled with bugs, what do you get? A pile of returns and complaints, and a bad reputation.
- Identify communication breakdowns now. These can only lead to confusion and complications down the road. Never assume that everyone understands. Take just a little extra time to create an environment that is destined to produce a product on time and under budget.
- There should be specific protocol setup for security and quality control considerations for new program tests.
- Remember problem #1? Ditto! Yes, you have to make it to market before your competition. But if you make it to market and your product is filled with bugs, what do you get? A pile of returns and complaints, and a bad reputation. Test all the way through the process, and you’ll save a lot of time in the end.
- Create an accurate budget. Also, outline ways to develop better upfront planning of the resources.
- Define “checkpoints” throughout the project. Give attention to those things that need to be adjusted along the way, even if they cause minor delays. Fixing them now, rather than later, will take less time overall.
- Take time to review the standards used for each and every project. Keep a running list of what worked, what didn’t, and how to do it better next time.
The next time your IT project is late, over budget, and looks like it is never going to work, review this list again.
Tags:
bad reputation budget bugs communication communication breakdowns confusion control considerations destined due consideration enjoy the silence extra time hick ups late not working over budget program tests project project management protocol quality control remember the silence standards testingTechnorati (All Links are external): bad reputation budget bugs communication communication breakdowns confusion control considerations destined due consideration enjoy the silence extra time hick ups late not working over budget program tests project project management protocol quality control remember the silence standards testing business it leadership management
This blog-entry is protected by a digital fingerprint:785273ed81985582c8a1be62f78c9459
