LATEST POSTS

This website is open to anyone interested in Project Portfolio Management (PPM). The site will give you access to material covering latest industry thought leadership, PPM methodologies and techniques, PPM related business challenges, solution / product material, case studies, white papers, book reviews and comments from our PPM experts.

Archive for December, 2006

Seven Deadly Sins of Customer Service

Excellent customer relationship management (CRM) is everything into days business world - no mater who you are and what project you are working on.

The Services Safari blog posting The Bad Behaviors of Service Professionals” gives us some key pointers on what constitutes bad customer service.

For your convenience, we have summarised these sins.

1) Lust - I’ve seen people try to charge in their after-hours wining and dining and expect some third party to pay for the enhancement of their love life.
2) Gluttony - How in the world can four people justify a $1,700 meal? I’ve seen people try it.
3) Greed - One enterprising lad tried to charge in two per diems when he crossed the international date line. Not surprisingly, he didn’t want to reverse the charge when he came back home.
4) Sloth - When lazy consultants or service providers charge people for time that they didn’t even work, it’s wrong and unethical. One practice particularly galled me. Some staffers got the answers to some self-study training materials. So, they charged in the time like they had done the work but they obviously didn’t. Worse for them, I re-tested these folks and they all failed. Then, I fired them for fraud.
5) Envy - I’ve known some partners with a bad imperious streak. They spent more that anyone else because they believed that they were better than everyone else. They weren’t.
6) Pride - “My clients are used to me charging them $8,000/month in expenses. I can’t come in under that!”. Yes, you can.
7) Wrath - Just because the client treated you badly doesn’t give you the right to stick it to them via your expense report.

For the full posting and for more customer service infractions click here

Comments off

Napoleon’s Downfall & Project Management

For me history is the gateway to human behavior, it teaches us not only where we have been, but where we are and where we should go. History underpins everything that is past, present and future and much can be learnt for what others have done. The PMThink Blog 1st of a 3 part series relates the fall of Napoleon to the trials and tribulations of the modern project manager.

Click here to hear Part 1.

Napoleon on Project Management by Jerry Manas: What is it about Napoleon Bonaparte that has led recognized modern-day leaders to study his principles—and countless books on management and leadership to quote his maxims? For one, Napoleon rose from relative obscurity to rule all of Western Europe in but a few years—something the Romans took centuries to accomplish. He brought order out of chaos. He crafted an administration and civil code that is still in use today. His troops adored him, and the people admired him. Even his arch rival, the Duke of Wellington said, “In this age, in past ages, in any age, Napoleon.” Yet, Napoleon lost it all, only to die alone and in exile.

Are there lessons for today’s project managers and leaders to be found in his successes and ultimate failings?

Indeed, there are.

Comments off

The 30 Most Important IT Trends for 2007

CIO Insight published an article, “The 30 Most Important IT Trends for 2007.”  For your convenience, the 30 trends have been listed on Talent on Target web blog.

To read list of trends click here

Comments off

PPM Change Management & Adoption Challenges

The implementation of Project Portfolio Management (PPM) brings more openness to the authorisation process and less ambiguity into the what, where, when and how of the project delivery process. If a PPM process is put in place typical political manipulation around pet projects becomes much more difficult. PPM also makes it difficult to hide mistakes and brings a level of detail that may create a fear factor amongst both senior and operational managers. However PPM is a change project and resistance to change will essentially become the norm.

What are the typical barriers to adoption?

1. - Internal politics and culture are by far the biggest barriers to adoption. PPM by its very nature will demand change within the business, and with change comes resistance – from both above and below.

2 - You will need to become an ‘evangelist’ for Project Portfolio Management, with an ‘executive sponsored guardian angel’. Resistance is inevitable; critics will most likely outnumber advocates, and you will need to continually preach the benefits and prove the value of PPM.

3 - Often management is aware of dissenters or non-conformists in the organisation, but mistakenly relies upon the introduction of the new system to improve these individuals’ productivity and performance, rather than tackling them head-on through direct communication before introducing the new system.

4 - Organisational capability and maturity in programme and project management governance and standards will impact PPM adoption. The more mature the organisation project management capability, the more ready will the business be to adopt PPM.

5 - Top management commitment to and understanding of the purpose and value of Project Portfolio Management is critical. Typically senior management either delegates it to lower ranks, or believes that it is the responsibility of the vendor to design and implement a complete process in isolation, and fails to appreciate that the organisation and its key personnel are a vital part of the adoption process.

6 - Inability of management to agree criteria for identifying projects within the organisation is an important barrier. For example, there will be resistance from programme and project teams to the adoption of a common approach to managing projects, reporting progress and constructing business cases.

7 - Unwillingness of business managers to see their ‘pet projects’ shifted in priority is also a barrier.

8 - Disagreement on the pace of adoption is a challenge. Whether rollout is incremental or rapid, it is inevitable that the business will demand that disruption and productivity loss be minimised.

9 - The willingness of the organisation to support the financial investment potentially needed for implementing a PPM software tool-set will be a major issue, and tool selection is often fraught with technical difficulties. ‘Rip-and-replace’ solutions come at a high price – cultural, technical and financial. The adoption of PPM will need to take into account the impact on existing processes and systems. Will they be replaced? If so, why, and at what cost to the business? Integration, flexibility and configurability will determine the successful choice of any PPM solution.

10 - It is simply human nature, that people will blame the tools and processes to hide their own lack of knowledge and understanding. All tools and processes are created with their own set of idiosyncrasies; it will therefore be important to provide continual support and training. However, you must be prepared to accept that no matter how much you train, hand-hold, and evangelise, some people will simply not understand PPM.

11 - In order for the executive levels to get bird’s-eye view of information on multiple projects, it is essential that the business be able to collect that information and to determine who is working on what. One of the most crucial but often overlooked barriers to PPM is the adoption of timesheet technology as a method of collecting baseline information. It is essential to manage the ‘Big Brother Syndrome’ – the suspicion that the business is only using timesheet technology to keep tabs on the staff. Instead, it is necessary to sell the benefits of increased employee visibility, utilisation and productivity.

Comments off

11 Tips To Reduce Project Failure

Following on from our last set of articles on why IT projects fail I would like to share with you 11 tips from Raven’s Brain on how to reduce them. 

1) Make sure to plan before starting the development or implementation.

2) Pay attention to tasks in the critical path.

3) Set up the necessary processes to calculate and inform the risk.

4) Ensure that the IT project has clear objectives.

Click here to read more

Comments off

« Previous entries