Right methodology for the right project….
Currently I am working on a sizable project, which is nearing completion and as usual, you always make those common mistakes project after project.
Over the years, everyone involved in managing projects have observed that projects have common characteristics that can be formalized into a structural process, which allows the projects to be managed more effectively.
Each phase can typically be brought to closure in some logical way before the next project phase begins, and each phase results in discrete milestones or deliverables, which provide the starting point for the next phase, also cost and schedule estimates, plans, requirements, and specifications should be updated, evaluated and accepted at the end of each phase.
Adopting an incorrect methodology or having no project framework in place can very easily cause you to have:
• Schedule and cost slippages
• Miscommunication within the team
• Wasting of time on administrative tasks that have no purpose
• Reliance on technical magicians to get projects done
I have decided not to make this mistake again (as usual). Two things which I realized in this project:
- Specifications for each pending phases should be revised at the end of each phase
- Never follow readymade templates for Project specifications (it should only be referred to), it back fires in the following ways:
- Makes you fill up lots of information which is normally not required
- Diverts you from your standard requirements, in some cases even helping you miss out key project requirements
- It looks a great format as far as presentation is concerned, but with hollow contents
March 3, 2007
· 
Rahul Desai · 
No Comments
Posted in: Project Management, Talman news
Leave a Reply
You must be logged in to post a comment.