May 15, 2005
It wasn’t enough is enough.
Had the meeting on Friday about the resource conflict. It was a good meeting, although I had a couple of revelations during the meeting. The resource hadn’t done an enough is enough in the team meeting as I had assumed. What actually had happened was this.
At the beginning of the month, I had scheduled a quick 30-minute daily build meeting between all building resources. The meeting was to create a time to chat for all builders, discuss issues and get quick status with where the project was and if the team needed anything. We meet daily, all via a conference line. This was people can also try something quick on the computer if needed.
I had made it my mission to type up minutes and distribute the minutes to the group and management daily. I tried to have someone else type up the minutes, but we don’t have that type of resource spread, or I don’t have enough pull with the secretarial staff. The minutes detail discussions, decisions, and next steps. They also plainly stated what was done and what was missed.
The problem is that this resource was overscheduled, and well the director finally realized it. I had asked for a full-time resource. I only got one dedicated 25% of her time. The resource silently worked a lot of voluntary overtime to get things to where they needed to be. So the director’s solution was to yank the resource for the other project, and offered no alternatives. Every minute that resource spends or doesn’t spend on this project directly either shortens it or elongates the project. The resource is working the critical path.
The other problem was with the design, even though the interface group approved the interface design. Now apparently, they need some training in how to do real-time hl7 charges to a file within Open Link.
My main problem with this situation, is that I was offered no alternatives and the situation wasn’t set up to be a negotiation. It was leave me scenario, and now I’m trying to brainstorm as to alternatives so the project once again isn’t held up. When the resource risk hits, it sure expands the project timeline.
Finally passed the test
Managing in light of McGregor's Theory X and Theory Y
CMMI
Kicking HIT Leadership Up a Notch
That's just some mumbo jumbo project management BS
Outcomes - The tactic to get to the strategy
Nurse Call, VOIP, and Wi-Fi: Its just cool when things come together!
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
August 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
November 2005
October 2005
September 2005
August 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
Joel on Software
David Ross
Edward Prevost
Martin Fowler
The Health Care Blog
The Tales of Hoffman
The Business Word
Medical Rants
Christina's Considerations
Paul Levy
HIS Talk
Appropriate IT
Candid CIO
RSS feed




