The Critical Path Week Ending February 28

Due to working crazy off hours in preparation for my v1.0 launch, I not only forgot to do a week in review on the 20th, I also missed meeting my writing commitment on the 24th and 25th.  Whatever the excuses, I was feeling a little burned out.  I have to remember this is a marathon and not a sprint.  Writing a daily blog takes a lot of discipline.  Though I have so much to say, it can escape me if I don't get the idea captured quickly.  Wow, it's hard to believe it's almost March.  At least there should be viewer posts about snow removal.

2/26/2010

Putting Things In Perspective

I had mild chest and shoulder pains this morning. I am in the ER waiting to see the doctor. I’ll let you know the outcome and my status shortly...

2/23/2010

Satisfying Needed Scope Versus Wants

There are many templates and means to ensure your project meets the requirements.  But I can’t stress enough how important it is to ensure you’re working to satisfy the requirements (or scope) first...

2/22/2010

The Hateful Cycle of Apathy Hits a Nerve

Have you ever stuck your neck out and get no support?  Did the trust among that team start to break down? I’ve seen it happen first hand and Geoff Crane wrote an awesome post over at Papercut Edge about it...

2/21/2010

How To Prevent Your Project From Hemorrhaging

This post is in response to a post written by Jennifer Bedell on the PMStudent blog about goldplating. Goldplating is very common in application development and can be very expensive...

2/20/2010

How Owners Managers and Leaders Differ

I was asked a very interesting question today, requiring me to stop and think. How do I believe being an entrepreneur and a business owner differ? It’s a very good question because...

2/19/2010

What You Need Is Some Kaizen

While sitting in a governance meeting the other day, I heard how (before I joined the team) a vendor brought in some high paid six sigma black belts to...

2/18/2010

How to Thank a Managed Camel

I was informed I am the winner of the very first Freedom of Speech February (FOSF) giveaway from How to Manage a Camel.  My comments last week on a blog post by Gary Holmes earned me a free copy of the Method123 Project Management Methodology (MPMM™) Professional from their partners at Method123...

2/17/2010

Creeping Ever So Closer To Closure

As my startup project is creeping ever so closer to its closure and the actual launch of the product happens, I’m feverishly completing activities late into the night.  It’s not easy working crazy hours to get this done.  My family goes to bed, I drink a pot of coffee, and get to work...

2/16/2010

Interesting PMI Perspective On Claiming PDUs

...Based on the telephone conversation I had, if you’ve worked as a PM for at least 6 months, you can claim 5 PDUs.  Otherwise, if you are able to say you spend more than 1,500 hours per calendar year in that roll, you also qualify to claim the 5 PDUs...

2/15/2010

Getting Exactly What You Want

I just wrapped up a week long logo design project at 99Designs, with an intellectual property transfer agreement.  Flash back to August 2009, when I was watching Episode 13 of This Week in Startups...

Putting Things In Perspective

The last few weeks I've been focusing on numerous things.  I've been working 3-4 hours a night, preparing to launch a product to the Project Management community.  I've been writing at least one blog post every day.  I engage my client for at least 8 hours a day.  Lastly, I've been reading a lot more blogs, in the hope to understand the perspective of others.  That's just the work list!  Time I get to spend with family is limited to a brief few hours a night and on the weekends.  I thought I had figured it out.  Sleep less, drink more coffee, work harder, engage more. Don't get me wrong, I'm not complaining.  I love this roller-coaster I'm currently on.  Yesterday the roller-coaster stopped, at least momentarily.  I received an email from my work counterpart yesterday morning.

I had mild chest and shoulder pains this morning. I am in the ER waiting to see the doctor. I'll let you know the outcome and my status shortly.

I can't remember a time when I stopped and just thought what would happen if we lost her.  I'm not saying that in a selfish way, in relation to the program.  She's what Seth Godin would define as a linchpin.  Though yes, she is a very passionate and intelligent leader. I mean personally.  This is someone's daughter,  someone's wife, and many a someone's friend.

I don't think my vantage point has changed.  I'm still as stubborn as I was 2 days ago.  I'm just as determined to sleep less, drink more coffee, work harder and engage more.  But, it really did make me take pause, put things in perspective, and appreciate the people I interact with.

Your life is like a project.  It is a temporary endeavor.

Satisfying Needed Scope Versus Wants

traceability

What is the definition of Requirements Traceability Matrix? It's a table that links requirements to their origin and traces them throughout the project life cycle.  Not everyone uses them. There are many templates and means to ensure your project meets the requirements.  But I can't stress enough how important it is to ensure you're working to satisfy the requirements (or scope) first.  I reviewed a vendor's progress report today and realized the very last task they had on their activity list was requirement mapping.  When asked why it was the last item on their list, their response was the activity wasn't on the critical path.  So, how on Earth were they going to know they were done, if they didn't map the requirements first?  Here they are, at the end of a development cycle, and we're being told the requirement mapping activity is just basically a clerical process. Imagine the frustration I suffered, knowing all too well they may have missed something.  Imagine how expensive it could be, to fix at the end versus the beginning of the development cycle?  I'm not saying the vendor didn't do a lot of work or deliver a lot of product.  Unfortunately, they spent way too much time satisfying the daily wants of a stakeholder and took their focus off the needs of satisfying project requirements in the process.

What do you think?  I'm a being too much of a control freak?

The Hateful Cycle of Apathy Hits a Nerve

Have you ever stuck your neck out and get no support?  Did the trust among that team start to break down? I've seen it happen first hand and Geoff Crane wrote an awesome post over at Papercut Edge about it.  He called it the too-common cycle of apathy. The post hit a nerve with me. At my previous engagement, the Engineering Department was used to being railroaded by management. Promises were always made on their behalf and they found themselves working long hours and weekends. If they didn't make the goals, those who made the promises would never take ownership. If goals were miraculously accomplished, the same person(s) would jump into the spotlight. After I was brought on board, I didn't have a problem looking a Director or CIO right in the eye and telling them I disagreed with them. Sometimes they backed down and sometimes they didn't. But everyone at that company knew I was honest and would speak up if I didn't agree with something. Everyone knew I was looking out for my people, my department, and my company. I believe positive change rolls up hill, just as sh*t rolls down.  Though I'm no longer with that team, I have no regrets for backing them up and providing support when they needed it most. Those who bullied so many are no longer there either.  Though there was an attempt to silence my voice by decapitating my team, others in the organization saw through the ruse.

I think sticking your neck out is worth the risk. If I think you're right, I'll support you.  By doing that, I build trust with my teams. With trust, my teams will do anything for me. With that, anything is possible. What can I say, everyone is happy but the party you had to confront in the first place. Yep, it's certainly worth it.

Thank you Geoff for getting me fired up.  Now go check out his site!

image courtesy of Papercut Edge

How Owners Managers and Leaders Differ

I was asked a very interesting question today, requiring me to stop and think. How do I believe being an entrepreneur and a business owner differ? It's a very good question because if you don't know either an entrepreneur or business owner, I don't know how any textbook answer would satisfy. From my perspective, a business owner's identity is merely the act of having and controlling property.  They could potentially inherit the family business, therefore becoming a business owner.  They could be very excited or could care less, looking for an exit strategy.

Entrepreneurs, on the other hand are passionate, committed, skilled, creators of value.  They create because they have a fire in their belly.  As an entrepreneur, they can't help themselves.  It's in their DNA.  They are so laser focused on what they are trying to create, people can either think they are crazy or brilliant.  But, with that charisma, people will be inspired and follow.

These contrasts aren't too far off from Project Managers and Project Leaders. PMI defines a Project Manager (PMBoK Page 444) as the person assigned by the performing organization to achieve the project objectives. As I wrote in a previous post, there are several contrasts between a manager and a leader (Bennis & Goldsmith 1997)

• Managers administer; leaders innovate.
• Managers ask how and when; leaders ask what and why.
• Managers focus on systems; leaders focus on people.
• Managers do things right; leaders do the right things.
• Managers maintain; leaders develop.
• Managers rely on control; leaders inspire trust.
• Managers have short-term perspective; leaders have long-term perspective.
• Managers accept the status-quo; leaders challenge the status-quo.
• Managers have an eye on the bottom line; leaders have an eye on the horizon.
• Managers imitate; leaders originate.
• Managers emulate the classic good soldier; leaders are their own person.
• Managers copy; leaders show originality.

So, what are you?  Are you happy? Why?

(image by apogeehps.com)

---

What You Need Is Some Kaizen

While sitting in a governance meeting the other day, I heard how (before I joined the team) a vendor brought in some high paid six sigma black belts to try to bring the vendor governance workflow in line with my client's governance workflow.  My client wasn't sure what they got out of the deal, but if you have a black belt in something, it should be good...right?  Because this venture proved fruitless, the vendor announced, "what you need is kaizen!"  That may be what they said, but it's not what my client heard. This was paraphrased by one of my client's team.  In trying to understand what she was saying, we had a quick back and forth that went a little something like this:

The vendor said there was something that would fix everything. Cry Pan or Pie Pan or something like that.I looked at her and asked, do you mean "kaizen"?Her eyes got really big and she then started to matter-of-factly point at me. That's it! That's it! Now, what does it mean?I said it just means improvement or refinement.She looked disappointed. That's it?Yep, that's it.

Now, I know it's not that simple.  There are no silver bullets.  I do believe in using refactoring or refinement to get you where you need to be, but that's going to be another post.  This post is more of a shame on you post.  Anyone out there who uses a new term, particularly one in a foreign language without explaining it first, shame on you!  Anyone out there who proposes there are silver bullets in project management, shame on you! And, anyone out there who proposes there are silver bullets in project management, uses a new term to label it, AND charges a lot of money for it, shame on you!

I strongly believe approaches like Agile, Kanban, and others bring a lot of potential value to programs.  Customers don't need snake-oil nor do they need silver bullets.  What we have here is, a failure to communicate.

I was thinking, maybe I should start a practice and say it will solve all your problems.  I can call it Verbesserung.

Any takers?

How to Thank a Managed Camel

My post today is an easy one.  I was informed I am the winner of the very first Freedom of Speech February (FOSF) giveaway from How to Manage a Camel.  My comments last week on a blog post by Gary Holmes earned me a free copy of the Method123 Project Management Methodology (MPMM™) Professional from their partners at Method123. All I did was pass praise in my comments on a Holmes post regarding common courtesy and the little things candidates should do beyond merely sending in a CV.

Reading his post inspired me to write a post of my own, THE most important thing is the customer.  I sometimes get a little worked up over the need (not the want) for common courtesy or being polite.  What else is free to you but can carry so much value to others?

So, thank you to the team over at Arras People and How to Manage a Camel.  You provide wonderful insights on your blog and I enjoy reading it while having my first cup of coffee every morning.

My advise to people out there is to get involved in the conversation.  Your thoughts and opinions are important and they should be heard (or read). I didn't post a comment because I thought I could win a contest.  I did it because I thought Gary wrote a great piece and he should be recognized for it.

If there is one thing you do today, recognize someone for the work they do.  You never know how you may be rewarded for that selfless act.

Creeping Ever So Closer To Closure

As my startup project is creeping ever so closer to its closure and the actual launch of the product happens, I'm feverishly completing activities late into the night.  It's not easy working crazy hours to get this done.  My family goes to bed, I drink a pot of coffee, and get to work.  An entrepreneur (Jason Calacanis) once said starting is easy; finishing is hard.

He wasn't kidding!  As a project manager, managing my own project for a product related to project management, you can see there is a little irony.  But, I really think this is going to help a lot of people and it will be worth all of the sleepless nights.

Today's activities included

1. Initial rebrand of the HueCubed twitter page
2. Initial load of the new HueCubed logo to the website
3. Set up the blog component
4. Post 1 free question and answer (with the plan to do it daily)
5. Load 10 questions and answers into the database

Mission accomplished.  I completed the 5 activities and am ready to call it a day (night).  Though we're not quite ready to launch, please feel free to follow me or subscribe via the RSS feed.

Thank you all; and to all a good night.