Skip to main content

Projects - Why are they so hard?

Project Planning and executing.  Why is it so difficult? 

To answer this question I went back to my Project Management Body of Knowledge (PMBOK) from the Project Management Institute and looked at the process group interaction diagram.  Wow!  If anyone looked at this they would immediately get discouraged.  
Have we made it unnecessarily complicated?  

This week I have been re-reading the updated edition of David Allen's "Getting Things Done".  It is a fantastic book and I would commend it to anyone.  

David Allen’s natural planning model is fairly simple.  It contains 5 steps.  
  1. Define purpose and principles 
  2. Outcome visioning
  3. Brainstorming 
  4. Organizing
  5. Identifying next actions
As I reviewed it again, I started thinking about my own project model.  It took me a few minutes to think through it and capture the essence of it, but here it is, along with a bit of explanation about each step.  

My Simplified Project Model (Answer the questions and then get to work.) 

  1. Why are we doing this? 
    • Is this project congruent/aligned with our team/family/individual purpose/mission? 
    • If we do this project will it get us closer to that purpose/support our mission?
  2. What does the outcome look like? 
    • Identify the measures of success
    • Clearly define what it looks like and what "done" means
  3. How will we get there? 
    • Develop major steps
    • What does the "doing" look like?"
  4. What are the next actions?  
    • Don't spend a lot of time defining all of the actions. At this point, major buckets of work that have not been broken down into specific tasks are good enough. 
    • Get a few of the next actions defined and then move on to the next step.  
  5. Act.  
    • The hardest part of this process is moving out of the planning and into the doing.  Take a step into the darkness of the ambiguity of ill-defined problems and start working. 
    • Set yourself up a regular iterative cycle of 
      • Identifying next actions
      • Planning and assigning the next actions 
      • Executing the work
      • Regularly reviewing/evaluating progress   

Comments

Popular posts from this blog

Marking Scriptures in Gospel Library

The other day as I was reading my scriptures and using a few of the available colors to do some highlights when I realized that I wasn't fully utilizing the entire pallet of colors. In the Gospel Library app there are 10 colors available.  Each of these colors can be used in the underline, highlight, or text color mode.  I asked extended family what they do and one of my niece's responded with this color code: Red- doctrine Orange- clarifications or explanations of doctrine Yellow- commandments and specific instructions Purple- promised blessings and how to attain them Grey- power phrases Blue- favorites Dark blue- ones with a deeper meaning (I always attach a note with a dark blue)  Pink- examples of Gods love/charity Brown-specific for our day Green - Not used This "Come, Follow Me" color code seems to be all over Pinterest.  I'm not sure where it came from, but it is based on the 12 colors in a small box of crayons. Here is a color coding

Bajio, Cafe Rio, or Costa Vida?

It is time for the showdown.  Which one is best: Bajio, Cafe Rio, or Costa Vida?  Or is it (as was my opinion) that they are all exactly the same? I decided to do a taste test.  Six people participated.  Three were salad testers and three were burrito testers.  None of the people who participated have any food judging experience although a couple of them have competed in cooking contests and have a couple of first place finishes to their name.   Each couple went to a different restaurant and picked up a Sweet Pork Salad and an Steak Burrito to go.  We ordered each salad with black beans and their creamy green dressing (whatever they happened to call it).  The steak burritos were ordered enchilada style with black beans. Then we all met at a central location and judged each dish on the following: Value Score = Weight (oz)/Cost($) Overall Appeal (visual appeal, aroma, garnish) Recipe (Cooking, ingredient combination, too moist or dry) Taste (Flavor combination, Seasoning, Texture

No, I am not a vegan

Why I'm not a vegan (or a vegetarian for that matter).  After my previous post about the Word of Wisdom , I felt I should write an additional post covering this topic.  First, the word "vegetarian" means nothing.  There are so many levels, tangents, and offshoots of vegetarianism that applying the label to yourself or anyone only causes confusion.   Some vegetarians eat dairy, some don't.  Some eat fish, some don't.  Some eat eggs, some don't.  Some are weekday vegetarians, and some only honor meatless Monday.  And the list goes on and on.  Labeling yourself as a vegetarian is simply a label that brings on a confusing discussion.  So, I don't use it.   I'm not a vegan either.  You see, vegans typically fall into three categories: - They are in it for their own good health - They are doing it to be kind to animals, promote animal rights, avoid animal cruelty, etc.  - They are doing it do save the planet The trouble with many vegans