Thursday, January 25, 2007

Project Execution

Tom Peters and crew on strategy implementation through execution ... here's a chance for the project manager to shine ... Get the leadership support. Break the plan into chunks. Schedule the first chunk and resource the team. Start driving. ... Sounds simple. ...

... "Great execution happens in small manageable chunks by taking large plans and breaking them into manageable parts. Otherwise, the path to execution can seem so overwhelming, people can't conjure up the energy. " ...


Via tompeters!: Execution through Projects

Labels: , , , , , , , , , ,

Friday, January 12, 2007

Project Management Quotations

Here's a Wiki Quote site with a number of project management quotations. Despite some tired and well worn ones, there are a few gems in there, such as:

"The bitterness of poor quality last long after the sweetness of making a date is forgotten."

"Some projects finish on time in spite of project management best practices."

"The more ridiculous the deadline the more money will be wasted trying to meet it."

"The most valuable and least used phrase in a project manager's vocabulary is "I don't know"."

"The nice thing about not planning is that failure comes as a complete surprise rather than being preceded by a period of worry and depression."

"The project would not have been started if the truth had been told about the cost and timescale."

"You can con a sucker into committing to an impossible deadline, but you cannot con him into meeting it."

"All project managers face problems on Monday mornings - good project managers are working on next Monday's problems."

"At the heart of every large project is a small project trying to get out."

"Everyone asks for a strong project manager - when they get him they don't want him."

"Good project managers know when not to manage a project."

"If you don't attack the risks, the risks will attack you."

Enjoy...

http://en.wikiquote.org/wiki/Project_management

Labels: , , , , , ,

Sunday, December 10, 2006

Managing Small Projects: A Playbook

Wherever I go, I hear the same thing: Project Management methodologies are overkill for small projects or work requests (the threshold for which I've heard defined anywhere from 80 hours to 500 hours---I tend to lean toward the larger number).

Even with that, I still believe that the same "thinking steps" and phases should apply no matter how large or small the initiative. With that in mind, I typically like to have the same high level framework for any size initiative, and let the details scale up or down based on the size (with more or less formality accordingly).

Let's face it, you still need to understand what the goals and objectives are, you still need to provide an estimate, and you still need communicate well and deliver in an organized fashion.

When challenged that the same steps aren't applicable across projects and work requests, I typically respond with, "Which of the steps do you believe aren't necessary and why?" Often, it turns out that most of the steps are still needed, they just need to be scaled back or made less formal for smaller efforts.

Tom Barnett has a nice writeup in Computerworld about a "playbook" approach he uses for the smaller projects (which he defines as 120 hours or less). It's basically a spreadsheet with tasks, owners, issues, and deliverables----in essence combining a task list, issues list, and RAM (responsibility assignment matrix) in one document.

It's not a bad approach for keeping the smaller projects under control, and is an effective way of keeping track of things. I'd still use it within the context of a high level framework, but overall it's a good idea. Check it out...

A Small-Project Playbook

Labels: , ,

Saturday, October 28, 2006

Strategic Portfolio: High Value Differentiated ...

Chevron has created a governance framework for actively managing its high-value enterprise-level projects, differentiating from its volume of small projects. The high-value portfolio is also where most of the investment is aligned. ...

Chevron manages its high-value information technology projects differently ...

... "it's a strategic framework for the company's biggest and most important IT projects. It's intended to ensure that the projects with the biggest benefit to the company as a whole get the right funding at the right time, and that they get special management attention. " ...


Via Computerworld: Chevron: Where Size Is Opportunity

Labels: , , , , , , , ,

Saturday, August 19, 2006

Einstein Project Management Tip #4: Think Value

And so we continue our series on project management tips from Albert Einstein. Here's another...
"Strive not to be a success, but rather to be of value."

This sums up perfectly the problem with most projects today. They focus on "success" without fully defining what success means. Project managers and PMOs track schedule and budget metrics. Then, at the end of the project, some capture customer satisfaction, almost as an afterthought.

What really needs to happen is to insure value to the customer, and this usually goes way beyond being on time and on budget. We spoke about the need for clear goals. Surely that's part of it. We also need to deliver in small, frequent iterations to provide the quickest value and get more immediate customer feedback.

Customer satisfaction should be measured and tagged as an index throughout the life of a project, just as Earned Value uses indices to track cost and schedule performance. This allows course correction to be made in areas such as goal clarification, communication, and other areas needed to provide good value.

And when the product has been delivered, be sure that the customer can maximize the benefits of the product through proper training, tips & techniques, next steps, or any other items that will help them get the value expected.

These are the very items I've attempted to address with my Service-Oriented Project Management (SOPM) framework, with its four phases of Understand, Prepare, Iterate, and Transform (UP-IT).

More Einstein tips coming soon...

Labels: , , , , , , , , , , , , , , , , , ,

Friday, July 14, 2006

Project Management Lessons from Mars

Brian Muirhead, the project manager for the Mars Pathfinder program, had some good tips to share with Projects@Work this week.

Some key learnings, extrapolated from the interview:

  • Innovation and bold ideas are often necessary to meet what often seems like an impossible challenge. The trick is to balance the cost and time savings with the risks.
  • A diverse team is key. It's better to have people that are different, with complementary skills, than have a bunch of people who think and act the same way.
  • A small core team that can share issues, problems, and resolutions, with one person at the helm, is an effective way to run a project.
  • Trust, honesty, and personal committment are traits that need to be prevalent throughout the team.
  • Test, test, and then test again. Don't rely on luck. If you can't test using the exact situation, then simulate it as best you can, testing as much as is possible.
  • A team is only as good as it's weakest link. It's up to the project leader to identify those people that aren't up to the task and remove them or find an area that suits them better.
  • Ensure team members have opportunities to make personal connections and grow.
  • A project manager must simultaneously provide the glue (keeping the team cohesive and focused) and the grease (removing barriers).

    Here's the full interview...

    http://www.projectsatwork.com/content/Articles/232113.cfm

Labels: , , , , , , , , , ,

Friday, June 16, 2006

One-Page Project Status Report; Keeping it Brief

There's a great writeup in Projects@Work about project status reports, including tips on meeting format and frequency as well as a format for a one-page status report.

According to the article, there are 5 Project Status Best Practices:

    1. Consistency — The status process should be basically the same for large and small projects, and consistent with their measures of success
    2. Escalation — The status process provides a mechanism for escalation of key issues.
    3. Simple — One page with the ability to drill down for details when necessary
    4. Public — Status is available to all (as appropriate) in order to communicate issues, risks and corrective action measures
    5. Inclusive — All projects are required to provide status on a consistent set of metrics
For busy managers who see loads of project status reports, it's much easier to have a consistent, brief summary of what's really happening on each project. They don't need a dissertation on all the details, nor will they get a clear picture just looking at performance metrics. Much like on a business case, most just want the executive summary. Simpler is better. Less is more.

For those looking to improve their status reports (and their credibility with management), read on...

http://www.projectsatwork.com/content/Articles/231704.cfm

Labels: , , , , , , , , , ,

Saturday, April 22, 2006

Earned Value Management Trends, Best Practices, and Pitfalls

A few weeks ago, I commented on Part 1 of a three-part series on Earned Value Management on Projects@Work.

While Part 1 set the stage and illustrated some of the challenges of EVM, Part 2 of this excellent series offers some excellent case studies and learnings.

For instance, the US government agency, OPM (Office of Personnel Management) cites the following critical success factors:

- Continuous executive sponsorship (not just up front)
- Committment to funding for adequate tools and training
- Adequate allocation of project managers' time to manage using this system
- Piloting EVM in a small group of projects to illustrate success and fine tune the details
- Not underestimating the culture change management required, involving employees, managers, and timekeepers. Regularly maintained training and job aids are critical.

Another organization, Inter-Coastal Electronics, cites having shallow, simple WBS templates in their ERP system as a key success factor. They claim that a WBS that's too granular becomes too difficult to manage. I couldn't agree more.

I highly recommend this series to anyone attempting to introduce Earned Value Management in their organizations.

http://www.projectsatwork.com/content/Articles/230753.cfm

Labels: , , , , , , , , , , , , ,

Wednesday, March 08, 2006

Business Agility: IT Proactive Partner ...

To support the need for business agility, IT must be a proactive partner in engaging with the business. Todd R. Weiss covers the theme at the Computerworld Premier 100 IT Leaders conference. ...

... "Bringing in new technology ideas -- and sharing those ideas early on with users so they can weigh in with what they need, want and expect from an IT project -- is key to delivering a successful IT deployment. " ...

Business Agility: IT Proactive Partner: Via Computerworld Premier 100: IT can pave the way for business agility, panelists say ...

This message is consistent with recent research findings from the IT Governance Institute: (1) IT has a pretty good understanding of the business, (2) IT is not very proactive at exploring new business technology opportunities with the business. ...

... "Observation: A small majority (55 percent) of IT departments always or regularly inform the business about potential business opportunities." ...


Via IT Governance Institute: IT Governance Global Status Report—2006 (PDF) ...

So, here's an opportunity for the IT organization ... Get some early, raw ideas in front of your business partners and start getting some feedback.

Labels: , , , , , ,

Wednesday, February 15, 2006

Project Management: Microsoft Office Live Beta Now Available ...

Office Live Beta is now available to support collaborative project management in a software-as-a-service model ...

... "the Microsoft Office Live Collaboration service offers small businesses password-protected online workspaces (intranets and extranets). Capabilities include customer management, project management, sales and marketing management, employee management, and company administration, as well as password-protected internal shared sites to facilitate collaboration among employees, customers, suppliers and other business partners. " ...

Project Management: Microsoft Office Live Beta Now Available: Via Microsoft: Microsoft Launches Beta Program for Microsoft Office Live Services: Internet-based services include free Web site, domain name and e-mail accounts ...

Labels: , , , , , ,

Sunday, January 15, 2006

Scrum: Microsoft Adopts For Project Speed ...

In keeping with our scrum theme, this method focuses on delivering value early in the product lifecycle. Simon Avery reports on Scrum software development method employed by Microsoft to accelerate new product cycle time to market. ...

... "To get its classified system to market as fast as possible, Microsoft is relying on what it calls the scrum method of software development, which involves a very small team of engineers. For the on-line classified product, code named Fremont, there are just six developers. " ...

Via The Globe and Mail: Executive Decision: Classifieds force sluggish Microsoft to scrum

Additional resources on Microsoft and scrum ...

Via Microsoft: Download details: Project 2003 Tool: Scrum Solution Starter: "Scrum is an Agile project management practice that employs short iterations and continuous improvement. The Scrum solution starter extends Microsoft Office Project Professional 2003 or Project Standard 2003 and enables project managers to perform basic Scrum work. "

Via Chris Flaat's WebLog : People are not fungible resources: "We are currently using both Scrum and more traditional project management on several efforts going on within our product unit, and I thought I'd share some learnings. Something we're running into is that getting people dedicated to one effort can be hard, depending on the management style of the relevant managers. "

Software Tools and Methods: "This presentation started with a brief context-setting look at why Agile approaches are gaining in popularity. It then discussed the fundamental principles that are common to most Agile methods, and used the Scrum approach to give a more detailed view by example on how Agile projects work. "

Labels: , , , , , , , , , , , , ,

Wednesday, December 28, 2005

Project Management Competency; Using the Learning Ladder

I was recently reading Peter Fogel's If Not Now, When, a humorous book about reinventing yourself, and he referenced the four stages of learning any new skill. It reminded me how valid this is in organizations trying to implement project management.

I've seen these stages also referred to as the "learning ladder" or "The Four Stages of Competence." It's not clear who created it. Some sources date it as far back as Socrates or Confucius, but its modern form has been in psychology books since the 80's.

The four stages are as follows (I'll paraphrase the explanations):

1) Unconscious Incompetence - Eveyone knows you're clueless except you. You don't realize why or when you're not achieving results, and are surprised when people complain.

2) Conscious Incompetence - The light bulb goes off. You suddenly "get it" and realize you need to do something different. You begin taking actions to change.

3) Conscious Competence - You're becoming more confident, and accomplishing goals through checklists, reading, learning, and mentoring. Things don't feel totally natural yet, nor should they, but you're achieving small successes.

4) Unconscious Competence - This is the ultimate goal. Some call it situational awareness. The French call it coup d'oeil. It's like riding a bike or driving a car, and only happens with adequate experience, and some trial and error.

This is funny, but very true---perhaps still the best example of a maturity model I've seen to date. Unfortunately, many organizations think they can mandate this fourth level. The fact is that it can only be reached by progressing through the paths above. You can't just jump levels, although good principles and an adequate support system can speed the path forward.

The bottom line is that we must allow time to progress through the levels and not criticize too harshly. Secondly, we must seek ways to provide principles and support to ease the transition through these levels.

Criticism is not the way to promote maturity. More on this coming up...

Labels: , , , , , , , , , ,

Wednesday, December 21, 2005

Agile Project Management Ecosystem: New Partners ...

Rally works to develop an agile project management ecosystem by adding new partners. ...

... "Rally actively partners with industry-leading companies to help customers acquire the development and project management skills needed to succeed with Agile, one of the world's fastest growing technology trends. Rally's Development and Coaching partners provide a comprehensive network of expert resources that offer a wide range of business, process and technology services related to planning, building and delivering software in small batches that provide immediate business value. " ...

Agile Project Management Ecosystem: New Partners: Via Rally Software: Rally Software Development Adds New Agile Partners ...

Based in Boulder, Colo., Rally Software Development offers the only on-demand, software development management solution that helps software organizations scale Agile development practices across the enterprise and around the globe. The company’s customers include leading software vendors, Internet companies and corporate development teams who are committed to responding faster to new opportunities and changing customer demands. With Rally, larger or distributed teams are able to define, develop and deliver high-value software in rapid iterations. Rally’s world-renown coaches and expert partners complement its on-demand tooling with training, mentoring and consulting services for creating the Agile organization.

Rally is creating the agile project management ecosystem ...

Labels: , , , , , , , ,

Monday, December 12, 2005

Project Management Useful Analogies (or Jokes)?

Some of these you may have heard, some perhaps are new. Sometimes helping people to understand requires an analogy or "funny" anecdote. Let us know if any of these work for you! My comments are embedded here for you also in brackets [].

1. It takes one woman nine months to have a baby. It cannot be done in one month by impregnating nine women. [my favorite - throwing bodies at the problem is usually not the right answer]

2. Nothing is impossible for the person who doesn't have to do it.
[watch it when someone says that someone "JUST" has to do X]

3. You can con a sucker into committing to an impossible deadline, but you cannot con him/her into meeting it.
[when they squirm about a date, figure out how to help them and note the risk]

4. At the heart of every large project is a small project trying to get out.
[break the work into "bite-sized chunks"]

5. A user will tell you anything you ask, but nothing more.
[requirements gathering - yeah, good luck with that. better to observe them in action, and show them prototypes and let them react.]

6. Of several possible interpretations of a communication, the least convenient is the correct one.
[true!]

7. What you don't know hurts you
[also known as "the devil is in the details"]

8. The bitterness of poor quality lasts long after the sweetness of making a date is forgotten.
[read that one again]

9. Everyone asks for a strong project manger - when they get one, they don't want one.
[amen!]

10. Fast - cheap - good - you can have any two.
[see other posts on the triple constraint]

Thanks to www.funny-haha.co.uk for these! See that site for many more!

Labels: , , , ,

Saturday, December 10, 2005

Innovation: Agile Project Teams ...

Companies are trying to break out of "commodity hell" through new product innovation. Embracing innovation requires acceptance that most projects fail and that project teams must be agile - quick, light, etc. Every "failure" yields something of value: data, information, experience, learning, prototypes ... which must be leveraged and reinvested to continue the hunt for the next great idea. ...

... "Bezos isn't just stubborn. He makes his constant experimentation economical by keeping project teams small and nimble. That way, even when they fail, they haven't spent much time or money. " ...

Innovation: Agile Project Teams: Via Business Week: Building An Idea Factory

Innovation project teams must use agile techniques ...

Labels: , , , , , ,

Friday, December 02, 2005

Business Performance Management: IT Project Challenges ...

Project managers need to pay special attention to requirements definition when involved in business performance management, or BPM, initiatives. Craig Schiff discusses the challenges associated with business performance implementations. ...

Business Performance Management: IT Project Challenges: Via DMReview: Maximize Business Performance: Don't Underestimate the Potential Impact of BPM

... "Underestimating BPM's possible payoff goes hand in hand with inadequate sponsorship and support from senior management that relegates BPM to a small IT project to be dealt with in the back office. This tends to result in failure to involve end users in the early stages of requirements definition and a poor grasp of the business issues. " ...

BPM: Business Performance Management is key initiative to drive line of site visibility to operational excellence opportunities ...

Labels: , , , , , ,

Saturday, November 26, 2005

Earned Value - why does it have to be so difficult?

This paper from the recent PMI-SAC conference describes how to apply a simple approach to Earned Value Management for IT Projects. It starts with the question 'why is EVM so little used?' and puts forward 4 of the more common reasons. The author goes on to describe what was originally used as a paper based method. It exploits the natural structure of IT projects, frequently formalised in some form of stage gate process. Industry norms for the relative breakdown of costs by stage and activity or phase within the stage are used to compare to actual costs.
This approach implies that you do not need a detailed bottom up cost and activity tracking in order to calculate the earned value. Of course, it would mean that you don't have much earned value information during phases and breaking the phases down into very small units may stretch the applicability of the statistics used at the outset.
Of course, the method still requires some work, project structure and some organisational discipline. This can be one of the most difficult of the original four reasons to address - Because sometimes management doesn't really want to know!
Earned Value Management for IT Projects

Labels: , , , , , , , ,

Monday, November 21, 2005

Project Implementation; Software Rollout Approaches

When analyzing alternate approaches for rolling out a new software product, consider information density versus percent of population.

For example, you can start with low information density (less functionality, fewer features, etc.) in a large percent of the population (or for everyone), and then roll out more features over time.

Or you can start with high information density (heavy or full functionality) for a small percent of the population (i.e. a pilot group), and then roll it out to wider audiences over time.

Neither approach is wrong. It all depends on the situation, the nature of the product, and where the risks lie.

For example, if the audience for the software can be isolated easily and there are no major issues with rolling out to wider audiences piecemeal, then it may pay to start with high information density in a pilot group.

But if there are major risks to rolling it out piecemeal (such as a need to maintain multiple systems, etc.) and basic features will do for phase 1, then the alternate approach might be a better choice.

One thing's for sure. To begin with high information density in a large or total percent of the population is usually a mistake (unless the full information density is necessary for the product to work, in which case the schedule needs to include time for full rollout and extra testing).

Just some things to think about when planning your next software rollout.

Labels: , , , ,

Thursday, November 17, 2005

Project Management: Google Innovation Machine ...

Quentin Hardy explores insights from Google CEO Eric Schmidt to better understand the project management methods powering the Google innovation machine, such as small teams, data-based decision making, rapid project life cycles, and collaboration networks. ...

Project Management: Google Innovation Machine: Via Forbes.com: Google Thinks Small ...

... "Brin and Page have created a corporate organism that tackles most big projects in small, tightly focused teams, setting them up in an instant and breaking them down weeks later without remorse. " ...


Insights on Google project management methods that power their innovation machine ...

Labels: , , , , ,

Wednesday, November 09, 2005

Microsoft Gates Ozzie Memo: Project Management Services ...

Microsoft Gates Ozzie Memo: Project Management Services: Via InfoWorld: Gates/Ozzie Memos-full text ...

... "Innovations abound from small developers ? from RAD frameworks to lightweight project management services and solutions. Many startups treat the ?raw? internet as their platform. At the grassroots level, such projects actively use standards such as vCards and iCal for sharing contacts and calendars. Most all use RSS in one way or another for data sharing. " ...

Labels: ,

Wednesday, November 02, 2005

Happy Project Management Day: November 3, 2005

Happy Project Management Day !

International Project Management Day November 3, 2005 ...

... "Project Objective: Increase the awareness of the value of project management within the large business, government, small business, and social communities and promote project management as a true profession and key business strategy. This includes, but is not limited to: construction, information technology, entertainment, government, aeronautics, health care, ecology, social, disaster recovery, community improvement, and quality of life projects. " ...


Happy Project Management Day! ...

Labels: , , , , ,

Wednesday, October 26, 2005

Top 10 Project Management Quips

It's not quite David Letterman, but here's a top 10 list of project management one-liners, selected from office-humour.co.uk.

1) If everything is going exactly to plan, something somewhere is going massively wrong.

2) Everyone asks for a strong project manager - when they get them they don't want them.

3) A project is one small step for the project sponsor, one giant leap for the project manager.

4) Some project finish on time in spite of project management best practices.

5) The person who says it will take the longest and cost the most is the only one with a clue how to do the job.

6) The nice thing about not planning is that failure comes as a complete surprise rather than being preceded by a period of worry and depression.

7) The bitterness of poor quality lasts long after the sweetness of making a date is forgotten.

8) What you don't know hurts you

9) A change freeze is like the abominable snowman: it is a myth and would anyway melt when heat is applied.

10) You can con a sucker into committing to an impossible deadline, but you cannot con him into meeting it.

For more of these, see the link below...

Jokes, Photos, Funny Stories and Office Humour - office-humour.co.uk

Labels: , , , , , , , ,

Project Management Collaboration: Google Methods

Insights on collaboration and project management methods at Google ... Dan Farber explores insights from a recent talk by David Merrill, Google IT exec, about their practices. The Google internal organization promotes openness, has a flat structure, and sustains transparency. The workforce can allocate 20% of their time on personal projects. The project portfolio is dominated by small projects with short cycles of three months and fast resource turns, where employees change projects frequently and rotate departments every year. A project database is used as a reporting system at Google. A culture of innovation is fostered through iterative designs, continuous improvement, and data-based decision making.

Project Management Collaboration: Google Methods: Via Rough Type: Nicholas Carr's Blog

... "What particularly struck me is the simplicity of the company's process for sharing information among the many projects it has under way at any given moment. " ...

Google Project Management Practices Insight ...

Labels: , , , , ,

Thursday, October 06, 2005

Conquer the Project Communication Conundrum

My favorite project-related formula explains clearly why as a team grows, it gets harder to keep everyone "on the same page."

# possible communication channels = n(n-1)/2
where n = the number of people on your team

In other words, if there are 3 people (n=3), there are only 3 possible communication channels. (Hint: picture drawing as many lines as possible between 3 points - you get a triangle – only 3 paths).
Increase the number of people (or points) to 5 and suddenly there are 10 communication paths.
Increase the number of people to 10 and WHOA, there are a whopping 45 communication paths!

No wonder keeping everyone on the same page is so hard!

What's the answer to managing this communication channel explosion? A few thoughts that may help:

  1. Divide the work into "bite-size chunks" that small teams can work on (for those of you from PMI-land, this could equate to work packages in your WBS)
  2. Collocation (yes, I spelled it right) i.e., physically getting everyone to work in the same room for the duration of the project; with collocation, communication is:
    • Faster - less meetings are needed - just turn your chair around or walk across the room
    • Easier (to keep everyone on the same page) - everyone can hear everything and jump into a conversation in midstream if the message seems wrong
    • Better - as people get to know one another because they are "living" in the same space, they learn how to more effectively communicate with one another
  3. Build and follow a communications plan (see also my post from 10/03/2005, Project Communication Handbook & Tools)
  4. For people who can absolutely not be in the same room, first, get to know one another in person (highly recommended although not always possible); then use the phone and instant messaging to keep in close contact
  5. Schedule time for team fun! (Highly important!) People that have fun together perform better and are more willing to communicate. We are human after all.

Hopefully these ideas are helpful to you and your project. Let us know your tricks for conquering the project communication conundrum!

Labels: , , , , , ,

Tuesday, October 04, 2005

Project Schedule Seem Impossible? Consider Skunk Works Approach

If you're ever faced with a project with a seemingly mission-impossible due date (geez, has anyone had one of those?), consider lobbying for a "skunk-works" approach.

The term, coined by Lockheed-Martin, defines a small group of people given an extremely important project with an extremely short timeline, where all normal bureaucratic rules are thrown aside in favor of a rabid focus on schedule.

The group is typically co-located and is given carte-blanche to achieve their goals without executive and administrative burdens. There's a strong focus on milestones and near-daily interaction with vendors.

Also, see Max Wideman's definition of "Quick Reaction Capability," which is in essence the same thing...

Wideman Comparative Glossary of Project Management Terms v3.1

Labels: , , ,

Saturday, October 01, 2005

Student Project Managers: Shell STEP

Student Project Managers: Shell STEP: Via Business Weekly: Students STEP into limelight

Nice writeup on Shell STEP program, which ignites the flame for future project managers ...

... "As part of the programme support process, students learn about the small business sector and have the opportunity to develop many core skills, such as time and project management, which significantly increases their employability. " ...

Labels: , ,

Saturday, September 24, 2005

Enterprise Portfolio Management Software Customers Prefer to Start Small

According to Computerworld, customers of project portfolio management software prefer to start small and gradually grow into the product. The key is to start with the basics, such as capturing the full inventory of projects and prioritizing accordingly, and then progress to more advanced features like portfolio balancing and charge-outs. See the full report below...

Portfolio management software users tout a la carte functionality - Computerworld

Labels: ,

Wednesday, September 21, 2005

Project Portfolio Management: PPM, a Michelin 3 Star Restaurant ...

Project Portfolio Management: PPM, a Michelin 3 Star Restaurant: Via Project Arena: Project Portfolio Management (PPM) Today: An Analogy for PPM

Great analogy for project portfolio management ...

... "The difference between running projects and project portfolio management is the difference between making a meal and running a restaurant. " ...


Michelin Restaurant Rating: The guide awards stars (1 to 3) to a small minority of restaurants of special gastronomical quality.

Labels: ,

Wednesday, September 07, 2005

Implementing Earned Value; Training and Scalability Are Key

Here's a lesson from NASA's Public Lessons Learned System (PLLS) from their pilot project to implement Earned Value Management at the NASA Kennedy Space Center in 2004.

Two key points were raised:

  • Make sure that sufficient training is provided to cover all facets and various scenarios
  • Make sure your EVM system is implemented in a way that doesn't slow down small projects and work requests (either have a light version of EVM or don't require it for projects under a certain size).

    For the full details, go to the NASA PLLS System below and search for '1409' (which will bring up lesson #1409)...

    NASA Public Lessons Learned System (PLLS) Database

Labels: , , , , , ,

Sunday, September 04, 2005

Project Management Case Study from PM Forum: A Call for Project Pilots

Here's a great case study from Hugh Woodward, managing editor at PM Forum.

First, it shows a typical example where a seemingly perfect project proposal had to be revised multiple times, under pressure to defer most of the capital spending to the following year. After several iterations of this, it was at a point where the plan was no longer feasible. Then, these delays were compounded by changes in the organization's financial circumstances, which led to the project being put on hold.

While the project was on hold, the technical developers experimented with different solutions and found even better ways of accomplishing the goal. In fact, the original project as proposed would have failed, even if it came in on time and on budget. The goals wouldn't have been met. Eventually, the project was restarted when the company's finances picked up, and this time it was a resounding success.

There are two lessons from this:

1) There is definitely a risk to project delays, as we all suspected. In this case, the delays led to an unexpected benefit. but we can't always count on that.
2) It is extremely beneficial to do a pilot and start small, to be sure the project will meet its intended goals. After all, nothing is more important in project management than meeting the goal the project is intended to achieve.

Here's the full case study:

PMFORUM, Connecting the World of Project Management - Case Studies

Labels: ,

Thursday, September 01, 2005

OnDemand Portfolio Management Solution: SMB Market ...

Via 3 Olive Solutions: on-demand project portfolio management solution ...

... "3 Olive Solutions develops Portfolio Intelligence™, the popular on-demand project portfolio management solution. Portfolio Intelligence™ is the solution of choice for mid-sized and small organizations or departments of larger companies such as the project management office (PMO) due to its affordability, quick implementations and easy-to-use methodology. Portfolio Intelligence™ gives executives and managers oversight for groupings of work efforts with its organization, control and decision support capabilities that result in increased business value from projects, better resource utilizations, and lower costs. " ...


Three Olive Solutions, LLC was founded with the mission of developing software solutions that help executives and managers be more effective leaders within their organizations. 3 Olive’s initial application, Portfolio Intelligence™, is an ondemand project portfolio management solution that is ideal for small and mid-sized organizations or departments within larger companies such as the project management office (PMO). Portfolio Intelligence™ is an affordable and easy-to-implement solution that enables executives and managers to organize, control and make better decisions on their work efforts resulting in higher business value, better resource utilizations, and lower costs.

Labels: , , , , , , , ,

Tuesday, August 30, 2005

OpenSource Projects: Organizing For Success

OpenSource Projects: Organizing For Success: Via Eclipse Corner: Eclipse is an open source community whose projects are focused on providing an extensible development platform and application frameworks for building software ...

Here is an interesting example of a project charter, organizational model, and project framework for an open-source project, staffed by a consortium of aligned enterprises ...

... "The Eclipse Project (charter) is managed by a small group known as the Eclipse Project Management Committee (PMC). The work of the Project is organized into subprojects. Each subproject has a leader who has overall responsibility for its success. Large subprojects are further divided into component teams, each of who has a leader that is responsible for its overall success." ...


Eclipse is an open platform for tool integration built by an open community of tool providers. Operating under an open source paradigm, with a common public license that provides royalty free source code and world wide redistribution rights, the eclipse platform provides tool developers with ultimate flexibility and control over their software technology.

Labels: ,