Skip to main content

Why Project Management Skills Can Make You an IT Hero

In the race for IT and business success, reaching the finish matters most. So it’s no surprise an important IT career path is project management.

"In American business, growth is associated with the ability to lead other people," says Sid Kemp, author of three books on project management, including Project Management Made Easy. "If you demonstrate an ability to lead teams, you're on your way to being an IT project manager. And good IT project managers can write their own ticket at a lot of companies."



So why does the path to glory run by the Gantt chart? A number of factors make project management important to IT professionals, even for hard-core technical specialists:

The increasing complexity of IT projects.
The emphasis placed on teamwork and communication skills.
A heightened need to meet budgets and deadlines.
The pressure on top executives to deliver results.
On Time, Under Budget -- or Else

Techies who lack project-management know-how may not be able to complete their work on time, leading to embarrassing snafus if not outright disasters. And in today’s unforgiving business environment, the business and career consequences can be severe.

"We have to demonstrate some basic project/task management ability or someone else will do it for us," says D. Keith Casey Jr., CEO of CaseySoftware. "Currently that could mean outsourcing -- offshore or not -- or it could mean replacement."

Project Management Starts with Self-Management

With the increased attention on IT initiatives, all project members need project-management skills, not just the designated project managers and team leaders. While team members can rely on project managers to keep the overall project on track, each individual must take responsibility for his own work as it relates to the broader project goals.

"It is essential that everyone on a project team have core project-management skills," says Kemp. "The core of project management is self-management, which leads to highly productive work. With these core skills, each person can define deliverables clearly, estimate their own work time and then deliver on time. Then the entire team can build a realistic project schedule and deliver as promised."

Technical Skills Are Not Enough

"Hardly anyone ever says, 'Our software project failed, because our developers were technically incapable -- if only we had smarter developers who knew their technical stuff,'" says Thomas Myer, author of No Nonsense XML Web Development with PHP. "Most of the time, it comes down to eliciting requirements, communicating status, setting expectations, meeting goals and pushing back on clients who want to keep adding more and more features."

Of course, it's one thing to gain project-management skills and quite another to move into project management. Kemp, who holds a PMP certification, suggests following these steps to move into project management:

Learn to complete your work on time and within budget constraints.
Gain know-how in formal project-management terms and concepts through organizations like the Project Management Institute.
Express interest in serving as a team leader in order to demonstrate your abilities in project management.
That's not to say technical skills don't have their place. They do, but alongside project-management skills. "Yes, you can do me and our clients a world of good by being a great coder," says Myer. "But you have a much better shot at greatness by being a great project manager and a good coder, as opposed to a great one, and you'll get a lot more respect and appreciation from the client."


By Allan Hoffman, Monster Tech Jobs Expert
Source: http://career-advice.monster.com/career-development/education-training/Project-Management-Skills/article.aspx
Post a Comment

Popular posts from this blog

Escalate, Escalate, Escalate!

What is escalation at organizations? Is it a way to solve problems? Is it a way to report things? Is it a way to put more pressure? Is it a CYA technique? What is it? How do you use it at your organization? How other colleagues of yours use escalation? Really, think about it and observe.

At IT service companies, leadership measures the performance of IT Help Desk by number of escalated work items over a period of time. The less escalation the better. The reasons are simple:

It is cheaper for companies if an IT Help Desk Specialist resolves an issue than an experienced technical specialist at one or two level higher. This is simple math, one gets $X and the other get $X*2And when client gets result fast, he/she will be happier. So, less escalation equals happier client in IT Services. Client raise an issue, IT Help Desk Specialist resolve it, BOOM, Next!

At organizations, It is amazing (sadly) to see how much lower level managers escalate problems, that they and their fellows can resol…

Moving from Basic DAD Scrum Based LifeCycle to Continues Delivery (Kanban Based) Lifecycle

I was thinking what the title of this blog post could be, I had couple of options to select from and decided to use a title that uses Disciplined Agile (DA 2.0) Lifecycle. Other options for titles were: Moving From Scrum to KanbanFrom High Performing Scrum Teams to Hyper Performing Kanban  The bottom line is that at some point you may want to move away from Time boxes to a flow of work and service oriented teams and improve performance and throughput without massive and sudden organisational change.  As always, I only share my experience and this may not apply to all situations, context is important. 
Another reason that I selected “Moving from Basic DAD Scrum Based LifeCycle to Continues Delivery (Kanban Based) Lifecycle” as the title, was that for many it is a question mark how to navigate through DAD life cycles. and I think this blog post could be one of the ways to navigate. 
Context: A Delivery Team started with Type A Scrum with 2 weeks Sprints. After a while, they deploy their …

New Organisational Model For Project Based Companies

Elliot Goldratt suggested a Strategy Tree for project based companies. While that may work for some companies, it will not work for knowledge based workers or Software Development Companies, or Digital Agencies. On the other hand traditional resource planning and resource allocation is also not effective despite all the effort one put into it to make it less of a command and control model - Here I assume we know who are knowledge workers and how their productivity works, Peter Drucker has a fantastic article about Knowledge Workers that I highly recommend you to read, if you have not read it yet: http://www.forschungsnetzwerk.at/downloadpub/knowledge_workers_the_biggest_challenge.pdf
Also, it has been proven that stable teams work better together on long term projects in software development. However, almost majority of software development companies or digital agencies break teams and reassemble them based on new projects or clients. This creates unnecessary complication and waste w…