The Hard-Nosed Project Manager

Agile Kool-Aid

At lunch time I listened to the PMI Agile CoP “Confessions and Coaching for Leading Agile Projects” webinar.  Once again I fail to see the difference between a project manager, a scrum master, and in this case an Agile coach.  Someone is drinking his own Kool-Aid.  I won't be claiming the PDU; this lasted about 30 minutes...

I had a colleague who is not a PM listen in with me for a while.  I kept my mouth shut and his comment was “What’s the difference between that and what we already do?”  I guess that says it all.

 

Although I am interested in Agile because I love project management, it sounds like another fad or even a sect.  The more I listen to these webinars the more I think that I will not shell my hard earned money for a scrum master course; I feel that most are just a money grab.

 

What do you think?  As always comments are welcome.

 

Connect with me on LinkedIn.  I am a LinkedIn Open Networker (LION); you can use “Friend” to add me to your network, please mention the blog in your request.

Crystal clear communications

Blast (pun intended) from the past…

FOO (Forward Observation Officer): Reference the left corner of Small Wood, left 150 mils, range 3500 meters, the target.

OP (Observation Post) Tech: Seen! Reference the target, left 350 mils, range 4000 meters, T-Junction.

FOO: Agreed!

What does this conversation between an Artillery (Red over Blue!!!) FOO and his OP Tech have to do with project management?  Well, nothing and everything.  Everything, because the subject of this post is crystal clear communications.

How do you expect to get things done if needs (requirements), priorities, etc. are not communicated clearly?  Having well written SMART requirements is one thing; having them understood is another.

To insure common understanding you need to insist that what you communicate to a team member be read back to you in his or her own words.  If you truly recognize you communication at the end of the read back you can safely assume that common understanding has been reached.  A few words of caution:

• You have to do this each and every time.

• You have to do this with everyone regardless of whether they are new or you’ve known them forever.

• If you do cannot equate the read back with your initial communication start again and again until a common understanding is reached.

• In this type of exchange every participant is equal; it is not about imposing your will, it is about communicating clearly.

Communicating is 90%+ of a project manager’s activities; what will happen if you are sloppy 90%+ of the time?

What do you think?  As always questions and comments are welcome.

Connect with me on LinkedIn.  I am a LinkedIn Open Networker (LION); you can use “Friend” to add me to your network, please mention the blog in your request.

PMP or CSM?

Here you go; a little TLA (Three Letter Acronym) salad on this sunny Saturday morning.  This serving may me a little spicy for some…

I landed on this PMI Community - Post that compares Project Management Professional (PMP) and Certified Scrum Master (CSM) roles.  To me they aren’t the same and I agree with the writer of the article.  What she calls a CSM we call a technical lead.  And to us, the technical lead is as important as the project manager, the quality manager, or any other team member.  Different but equal.

What do you think?  As always questions and comments are welcome.

Connect with me on LinkedIn.  I am a LinkeIn Open Networker (LION); you can use “Friend” to add me to your network, please mention the blog in your request.