After watching two webcast and interviews; I have documented some common top practices favoured by IT project managers. They have found them to be very fruitful & improved to crop out consistent outcomes.
1. Act immediately on prioritized task
Usually project manager position is challenging and responsible in nature. Usually, they implement airplane mode; avoid attending personal calls during work hours. It yields to productive work and allows to addresses the targeted issues. Each task is assigned with a priority like action task (must to be completed now, and measurable start & end point) or deferred task (completed, but not now; identify the time to be completed). It has also been revealed that PM acts on each matter urgently with prioritized task.
2. Use project management tool
It is the tendency that every IT projects are guided by project management tools like MS Project/ intervals under the leadership of PM. It requires the people to use & contribute it. This tool is viable across the team from designers to developers, to assign and manage tasks with serious due dates, and to track all of the project life towards launching. It is one of prime supplement of successful project.
3. Hold meetings with purpose
During the project life cycle, it is always wise step to meet only if it is required because time is quite precious during this phase for both PM and team.
- Purpose of the meeting should be clear before organizing meeting with clear agenda.
- Review discussion points before closing the meeting.
- Recap action items and set delivery dates
4. Define and check scope & assumption
Define project scope clearly as soon as possible with signatured agreement, which make sure that every contributors are also in game plan. Clarification is documented. Deliverable falls within the scope. Define assumption along with goal and & intermittently reviewed during project life cycle to make sure functionality and process for delivery still accepted by client. If it is not or there is some alteration; then it should be reflected into change request to client & employee.
5. Version control – cvs/git/svn
This is one of the safety guards against accidental hazard faced in source code. Sometimes due some reason, we end up in working code to buggy code. If we have already implemented any type of version control & checked out the version; then we can recover the old edition of source code. Hence, it gives the sound support in using version control, no matter how small or large the project.
6. Testing
It is recommended to always test application before delivery / launch of application. There had been various cases that people have failed to exhibit the working product during delivery/ presentation. Hence, it is suggested to test in prior to delivery. Considering example, Mississippi State Tax Commission filed a lawsuit against Fairfax, consultancy because the automated tax revenue system that the Fairfax built didn’t work without "multiple incidents of both a critical and serious nature," according to the lawsuit.
7. The Hidden Costs and Dangers of the Shortcut
In IT industry, it is frequent that employee runs out of time leads to pressurized to complete the tasks. However, if in absence of skilled or experience PM, the wrong shortcut may end up costing you a lot more than expected in form of hidden cost.
8. Using ROI to Evaluate Project Management Training
The monetary measurement (ROI) can be done in order to evaluate the efficiency and effectiveness of an investment made by a company. Investments category varies like financial, employee pool, equipment, and training programmes etc.
9. Communication
There should be consistent communication channel with back up alternative for certain situation. IM, Email, Skype & cellular calls are most frequent form to be in team loop. The goal of efficient communication is to make sure that everyone on the same page and can form conversation in need.
References: Webcast & interview - By John Reeve (PM), Pelago Webdesign
- By PMP, Nuwave Technologies
Parth
Posts
