Project Management

Project Management 2.0

by
New technologies, concepts, and Web 2.0 tools are popping up everywhere. How can you use them to help your project team collaborate, communicate - or just give your project an extra boost? [Contact Dave]

About this Blog

RSS

Recent Posts

Are You Prepping For The PMP 24/7?

Are You Just Too Darn Busy?

Eliciting Requirements... Creatively!

What To Expect When Your Stakeholders Are Expecting

8 More Templates to Save You Time

Categories

Advice, Certification, Collaboration Tools, Decision Making, Estimating, Interviews, Learning, Management Approaches, New Templates, Personal Productivity, PM Software, PPM Software, Presentation Tools, Reporting Tools, Requirements Management, Research, Risk Management, Scheduling Software, Security, shameless self promotion, Techie Tools, Time Killers, Time Tracking Software, Training, Virtual Team Tools, Web-based Tools, workshops

Date

Is the Triple Constraint the WRONG way to Define Success?

linkedin twitter facebook Request to reuse this  
Situation: You want to take a broader view of managing projects.

My new favorite author spoke at our local PMI chapter meeting last night.  Aaron Shenhar's book, Reinventing Project Management gives you a LOT of food for thought, but I think that one of his points is truly a breakthrough concept in our field.  It cuts to the core of why there is so much controversy around PMBOK-based approaches and Agile approaches.  In his presentation, given mostly to PMPs mind you, he says, "PMI has given us a great foundation.  However, it's time to leave that foundation and go to the next level."

During his talk, he described a number of reasons why the standard approach to projects must change.  A lot of it sounded rather "Agile" in nature.  For instance, he talked about the Triple Constraint theory as being a key impediment to successfully delivering projects - because it incorrectly defines the success criteria.    He said, success should not be defined just in terms of Scope, Cost, and Time - which are strictly efficiency-based.  The focus should be more on business results and customer satisfaction.

His definition of success is broken down into the following categories:
- Efficiency (criteria similar to the triple constraint)
- Customer (criteria = customer satisfiers)
- Team
(criteria = customer satisfiers)
- Business Needs (criteria = things like ROI, strategic fit, and competitive advantage)
- Future Needs (criteria = future value, like in the case of new technology where much of the value is yet to be defined)

His theory (he describes it as 'project manager as mini-CEO') is "If you approach projects with this broader set of success criteria, you will be a better project manager, because the results will be better."  It's hard to argue with that. 

It feels to me like he is calling for us to combine what PMI is starting to address separately as leadership skills with the PM approach in general.

How do you define project success?  If the Triple Constraint good the way it is or should some of these higher level issues always be considered when managing projects?
Posted on: May 21, 2008 01:52 PM | Permalink | Comments (41)

Scrappy Project Management

linkedin twitter facebook Request to reuse this  
Situation: You're tired of guiding new PMs with templates.

Kim Wiefling is a scrappy project manager - no doubt about it.  Whether you're listening to a voice mail from her, reading an email she sent, or browsing through her book.  She's the kind of person that calls it like it is - and that's what I like about her book, Scrappy Project Management.

It's not about templates or process (not that I have anything against those).  Each chapter focuses on a rookie mistake that every new PM makes before they have enough experience to set them straight.  Here's a list of the chapter titles:
  1. Customer, what customer?
  2. If you don't know where you're going, any road will do.
  3. Communication, we've got real work to do!
  4. Hey, it wasn't me, it was the "others".
  5. Why plan, let's just get moving.
  6. Risk? What could possibly go wrong?
  7. Priority?  Everything is #1!
  8. Change?  What do you mean things have changed?
  9. Assumption is a mother.
  10. So, what were you expecting?
  11. Lessons not learned.
  12. Sure we appreciate you - didn't you get your paycheck?
These are mistakes we all made early in our careers - and continue to watch others make every day.  Trying to correct them is tough - like trying to give your kid the benefit of your experience.  However, if you see someone struggling with any one of these things - it might be a great time to hand them this book (properly marked) and walk away. 

I know, I know - but it's worth a shot...
Posted on: May 12, 2008 05:17 PM | Permalink | Comments (1)

What Really Makes You a Leader?

Categories: Web-based Tools, Research

linkedin twitter facebook Request to reuse this  
Situation: You're in a mood to Show off your leadership skills...


There are LOTS of great discussions happening right now in the new Leadership GIG.  As a part of that, I thought it would be interesting to get your opinion on what is the most important predictor of leadership potential.  If you have a moment now, just click on the graphic below to tell everyone what you think.

 
Posted on: May 12, 2008 11:42 AM | Permalink | Comments (6)

Straw Polls on gantthead

linkedin twitter facebook Request to reuse this  
Situation: Staying "off the poll" is the least of your worries.

Ever wonder what people think about a given PM topic?  Now you can create a poll and find out!   Of if you are just in a mood to express your opinion take an open poll and let everyone know you you feel. 

Here's a great example of a poll in progress:

Q: When you are trying to create incentives to promote teamwork, what is the most important question you could ask yourself?

I like to think people will use these for settling heated project management disputes, research for articles, and just to have fun.  Remember, participating in polls increases your headcount - so vote early and vote often!
Posted on: May 05, 2008 07:56 PM | Permalink | Comments (0)

Questions - Defining Project Scope

Categories: Advice

linkedin twitter facebook Request to reuse this  

Situation: You want to ask the right questions when defining your project scope.Last week I posted a set of questions from Project HEADWAY related to selecting and enrolling a sponsor.  Here is a similar question set from the Plan stage of the process, Define Project Scope.  What do you think?  Are these the right questions to ask yourself and others during this task?

To determine the scope of the project, ask yourself the following questions:

  • What is out of scope on the project? What work won’t you do?
  • What is in scope? What work will the project do?
  • Do you know the boundaries of the project?  Into what areas will you not venture?
  • Have the requirements for the project and the product been clearly defined?
  • Do you know which stakeholder requirements will not be delivered on by the project?
  • Do you know how you will document the project scope?
  • On a 1-10 scale, do you know how set in the stone the scope of the project is with 1 being not at all and 10 being carved in stone? 

Ask your sponsor or a trusted colleague the same questions.  Also, consider asking them:

  • Based on what you know about the project to date, what do you think it is going to do?
  • What do you want this project to do?
  • What should the project not do?
Posted on: April 24, 2008 01:18 PM | Permalink | Comments (8)
ADVERTISEMENTS

"Life is but a walking shadow, a poor player that struts and frets his hour upon the stage and then is heard of no more. It is a tale told by an idiot, full of sound and fury, signifying nothing."

- William Shakespeare

ADVERTISEMENT

Sponsors