so i finally was able to get off the client with the bad client PM. i spent a couple of weeks off with my family, which is always appreciated. also, i had heard that the client PM had finally resigned. ;)
anyway, i'm in north carolina for the next several weeks with an old client doing a new project around identity federation.
they were a difficult client when i was here last, but that was almost a year and a half ago. they did mean well, but their execution was not the best. . .
driving up from the appalachians (where i'm staying, the client is in BFE, north carolina), i was again taken by the beauty of the drive. lots of trees and soft mountains. very nice.
we'll see how this engagement goes. nice folks and all. nice bbq as well. that is one of the good things about being on the road, you get to try many regional specialties, especially if you're foody like me.
Showing posts with label consulting. Show all posts
Showing posts with label consulting. Show all posts
Monday, August 27, 2007
Monday, July 23, 2007
3 reason consulting project managers are important
in my experience most clients try to cut out hours from a project team any way they can. it's reasonable for them to try to get the most work for the least amount of money.
however, clients often cut out the project manager from the consulting project team. the rationale is that since they already have a client-side project manager for the program, why do they need a project manager from the consulting organization?
there are 3 reasons:
1. experience with the technology. the consulting PM has done a number of engagements that you are paying for. they have the experience to know what to expect and plan for. would you have a PM that only has experience with SAP integrations to PM a web application server consolidation? of course not. this leads to number 2.
however, clients often cut out the project manager from the consulting project team. the rationale is that since they already have a client-side project manager for the program, why do they need a project manager from the consulting organization?
there are 3 reasons:
1. experience with the technology. the consulting PM has done a number of engagements that you are paying for. they have the experience to know what to expect and plan for. would you have a PM that only has experience with SAP integrations to PM a web application server consolidation? of course not. this leads to number 2.
2. "soft" skills. the consulting PM often has worked with the consulting team before. this familiarity often pays off for the client in either tasks being completed early due to project team synergies, or it allows for potential problems to be identified early and reported to the consulting PM by the consulting team simply because the consulting PM is not the "client".
3. the consulting PM is not the client. one cannot underestimate this. because the consulting PM is not part of the client organization, they can be objective and be counted on to call out personnel or other problems to the client PM organization. they are their for the project sponsors success. the reason the consulting PMs want the client sponsor to succeed is because this leads to more projects for the consulting organization. this is also the difference between consulting and resource augmentation.
if you ever find yourself being the client of a consulting organization, it is best to keep the consulting team humming along under the methodology that they are most comfortable with. this includes use of their consulting PM. it may cost a bit more up front, but it's worth it to raise chances of the project being successful. and really, this can only help you, the client sponsor.
Tuesday, July 17, 2007
inaugural post
so this is my first post blogging about a specific topic: consulting.
i'm not talking about "resource augmentation", though i'll probably post about that, i'm talking about full blown capital "C" consulting.
what does Consulting mean? that is one of the topics i'll explore over the life of this blog.
i'm starting this at a weird time, actually. my initial thought was to have a place to describe and record my days on the road. sort of a place where i can vent about work and the difficulties of being on the road. but, oddly, i'm starting this blog while being on a local project.
that's right. local.
my client is all of 4.3 miles from my home door-to-door. any readers who happen to stumble to this page may now disregard everything i post about being "on the road" because i'm currenty within spitting distance of my house.
but enough about me and more about me and my "street" cred.
i've been a consultant for about 7 years now. i've spent some of that time as a contractor, but most of it as a "big 5. . .4. . .(n-1)" style consultant. i'm, mostly, a technology consultant. i do identity management (and i may elaborate on my actual work from time to time) architecture and strategy.
i'm also a family man. i'm a father of 3 and have a lovely wife. obviously when you're on the road for 42 weeks a year there are challenges to being a dad and a husband. that's another set of topics to discuss.
i'm a bit of a novice blogger and a not-so-great writer. so please excuse the occasional lapses in grammar and spelling.
i'm not talking about "resource augmentation", though i'll probably post about that, i'm talking about full blown capital "C" consulting.
what does Consulting mean? that is one of the topics i'll explore over the life of this blog.
i'm starting this at a weird time, actually. my initial thought was to have a place to describe and record my days on the road. sort of a place where i can vent about work and the difficulties of being on the road. but, oddly, i'm starting this blog while being on a local project.
that's right. local.
my client is all of 4.3 miles from my home door-to-door. any readers who happen to stumble to this page may now disregard everything i post about being "on the road" because i'm currenty within spitting distance of my house.
but enough about me and more about me and my "street" cred.
i've been a consultant for about 7 years now. i've spent some of that time as a contractor, but most of it as a "big 5. . .4. . .(n-1)" style consultant. i'm, mostly, a technology consultant. i do identity management (and i may elaborate on my actual work from time to time) architecture and strategy.
i'm also a family man. i'm a father of 3 and have a lovely wife. obviously when you're on the road for 42 weeks a year there are challenges to being a dad and a husband. that's another set of topics to discuss.
i'm a bit of a novice blogger and a not-so-great writer. so please excuse the occasional lapses in grammar and spelling.
Labels:
consulting,
first post,
home,
resource augmentation,
travel
Subscribe to:
Posts (Atom)