The Regenerate Web

facilitating the regeneration of software teams

User login

Syndicate

Syndicate content

Services


Add to Technorati Favorites

Project

- delivery (3)
- duration (1)
- effort (3)
- estimation (4)
- metrics (1)
- Planning (1)
- PMI (1)
 - PMBOK
- task (2)
- velocity (6)

Management

- Boss (1)
- consensus (1)
- influence (1)
- leader (5)
- meetings (1)
- Motivation (1)

Browse archives

« July 2008  
Su Mo Tu We Th Fr Sa
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31    

Analysis

- modeling (3)
- requirements (3)
- research
- Analysis (1)

Who's online

There are currently 0 users and 0 guests online.

Priorities

|

Priorities - a cautionary tale

Earlier this month was the first time in twenty years that I have not gone to work late on the first day of my kid's school.  Don't get me wrong, I still have kids in school, it is just that due to a conflict between other work and personal schedules, I needed to schedule a critical meeting at work this morning.  

In my family, we have a tradition, that on the first day of school, my wife and I drive or walk the kids to school or load them on the bus, and spend some time together over breakfast remembering the summer, and thinking about how they have grown, or any school concerns we have.  Usually my wife is concerned about being alone more.  Over the years it has been a precious tradition, and my wife and I have come to rely on it.  My kids have too.  That day my 8th grader was unhappy that I was not going to be there to see him off to school.  

I was scheduled to be off work the following day, as I was building a storage shed in my backyard.  Since I arranged for a friend to come and help me with that, I had already ordered the lumber and torn down the old shed, when this meeting came up, I didn't want to try to reschedule the shed project.  

My attitude that morning was one of resentment.  I had very little confidence that this meeting would accomplish it's objective.  We had a specific technology problem that we had been postponing solving for 6 months.  Several times people had offered suggestions and attempted to build consensus around a solution and it had not happened.  I was one of those and I got beaten and bruised for my effort.  Our project was critically late, and at risk of failing it's political viability date.  That is the date at which if we haven't delivered, it is not politically viable to be affiliated with the project.  

Before the meeting I said this prayer:
Dear God, I pray specifically for this meeting, its outcome, and its potential to become a ruck.  I ask that you would intervene and allow participants to behave rationally, and that consensus would emerge.  I also pray that a plan for action around implementing the solution would also emerge that allows us to deliver before our project ceases to be politically viable.  
In spite of my poor attitude, the meeting did go well and we did reach consensus.

So why is this about priorities?  Because I had a personal conflict of priorities around this meeting.  This meeting became critical, because of our lack of priority around resolving this issue, which has now become the critical path of our project.  As a manager, I recognize that part of my job is to make sure that I (or someone I assign) control the critical path of each project by making sure that all the appropriate decisions get made before they hit the critical path.  While there are always things that happen that are beyond our control that change the critical path - resource issues, and external forces that are unforseen, but the vast majority of things are well within our control, if we just would exercise that control.