OUR NETWORK: CompTIA TechLore DijitCommunity TiVoCommunity MyOpenRouter About UsAdvertiseContact Us
The Largest Online Community
for Software CEOs and Executives.

Insight Into the IT Project Manager's Work and How To Help Them

According to a Gartner analyst firm report, 15% of all IT projects failed that year because of high cost variance, while 18% were unsuccessful because they were substantially late. [i]  This means that in 2008, 1 in 3 technology projects failed.  Why such a dismal success rate?  Such projects primarily involve the management of human resources in order to accomplish the target schedule, cost, and quality, so it is safe to assume that poor resource management played a large role.  Unfortunately, without effective resource management processes, such organizations are left asking questions like:

  • “Who is working on what?” 
  • “How do I get this project back on schedule?”
  • “How much more work will it take to finish?” 

The Problem with IT Projects Today

Resource Management

            IT project teams are made up of knowledge workers who are categorized by skill types or job functions.  For example, a project team might require business analysts, developers, team leads, project managers, architects, or database analysts.  Finding the right person to assign to a project or task can be the most challenging problem confronting the organization.  Typically, quality staff is scarce and therefore heavily sought by competing projects.  Without resource management processes, the organization struggles with allocation of its staff across projects.  

Project Management

            In addition, project managers are responsible for keeping scope, budget, and schedules on track.  How can project managers achieve this when they don’t know how many hours it takes to accomplish a task, or how many hours remain in the project?  Without an effective system in place, project managers must constantly intrude on team members to get estimates.  Likewise, the management team is always asking for status reports and accurate information on projects so that they can make critical decisions.  Of course, the project manager is always the last to know when one of his or her critical resources has been magically “re-assigned” to another high profile project!  In the words of a famous song, many project managers are “stitched up, out of their mind, feeling strung out, lagging behind, trapped in, can’t do a thing because they’re locked down….” [ii]

Executive Decision-Making

            From an executive perspective, it is impossible to make effective decisions when one does not know what people are working on or how the projects are doing. Additionally, if strategic projects do not have priority for critical, scarce resources, it will cause stress for the organization as a whole. 

            Many organizations feel that it is enough to track project progress on a percentage complete basis.  Unfortunately, this is not consistent with established methodologies, which nearly always suggest that the only accurate measure of progress is tracking work effort (i.e., time).

The Answer

Integrating Plans with Actuals

            Projects are executed in order to bring in a positive return on investment (ROI).  The ROI might be lowering risk, enhancing the organization's strategy, streamlining processes, complying with regulations, or otherwise improving the state of the organization in some way.  This potential return must be quantified in financial terms, even if it is only a very rough estimate of the benefit provided.  It motivates people to understand why they are working so hard, and a big number is a good motivation.

            The other half of ROI is the investment or cost. Project managers and executives cannot know if a project was successful or not unless they understand its cost.  In today's globalized knowledge worker world, project costs are mainly derived from the cost of labor.  Consequently, tracking time to projects and tasks is an inescapable requirement for measuring project ROI.

            If 10% of a project's allocated budget has been spent and only 5% of the work has been completed, there is a problem. Project managers who track employee actuals and find this out early in the project have a fighting chance of recovery.  Those who don't will find out much later on that their projects are drastically over budget.  This is just one example of how real-time data enables project managers to fix problems before they start.

Insight Into Resource Availability

            In a 100 person organization, there are always five or ten people who are overbooked.  Everyone wants these people to work on their projects.  Every time they take a vacation or becomes ill, the organization groans.  Conversely, there are other people who are under-utilized.

            Even when project managers understand resource availability, it changes.  They might run around and get all of the vacation schedules recorded in a big spreadsheet, only to find that a week later it has all been moved.  What project managers need is real-time access to team member schedules, tasks and available time.  This makes assigning people to tasks much easier.  (Such a system must also be web-based, since the team is probably not all in one workspace 24 hours a day.  This is why spreadsheets don't work very well.  Not only are they unable to be audited, but they don't allow for global access from various participants.)

Real Data for the CXO

            It is extremely important to present project data to management in an easily consumable way.  Executives just want to know, at a glance, what is broken or about to be broken. They are problem solvers, and they can only succeed if they have up-to-date, accurate information.  Such data will also allow executives to prioritize projects based on their value to the organization at large.

The Bottom Line

            When IT workers track their time by task and project, project managers can address problems as soon as they surface and executives can understand cost expenditure. This will put an end to project failure, as well as eliminate the waste of resources on projects that are not profitable to the organization.  No IT organization can afford to have 1 out of 3 of their projects fail, but with the right procedures in place, they won't have to.

About Curt Finch 

Curt Finch is the CEO of Journyx. Founded in 1996, Journyx automates payroll, billing and cost accounting while easing management of employee time and expenses, and provides confidence that all resources are utilized correctly and completely. Curt earned a Bachelor of Science degree in Computer Science from Virginia Tech.  As a software programmer fixing bugs for IBM in the early ‘90’s, Curt found that tracking the time it took to fix each bug revealed the per-bug profitability. Curt knew that this concept of using time-tracking data to determine project profitability was a winning idea and something that companies were not doing – yet… Curt created the world's first web-based timesheet application and the foundation for the current Journyx product offerings in 1997. Learn more about Curt at http://journyx.com/company/curtfinch.



[i]               (Apfel, Hanford, Light, Stang, Mieritz, & Fitzgerald, 2008)

[ii]               (Mayer & Hancock, 2005)

Read More In: Strategy and Leadership

Tips & Tricks from Software CEO Curt Finch


Tags : executiveITmanagementplansprojectstechnologytimesheet

You must login to discuss this item.

 
 

Please log in or register to participate in this community!

Log In

Remember

Not a member? Sign up!

Did you forget your password?

You can also log in using OpenID.

close this window
close this window