Do you have corridor conversations?

Last updated by Tiago Araújo [SSW] about 2 months ago.See history

The hallway is your friend. It's a place where you can gather a lot of information informally.

Formal meetings can have a "Us vs Them" feel - While the information collected and the conclusions of the Spec Review are presented formally at the end of the Review, it is important that the consultants convey key points to the client as they emerge through the course of the Review. The formal presentation is not the time to be presenting new information to the client.

ProjectManagement Suprise
Figure: Use corridor conversations to prevent nasty surprises

Addressing key potential sticking points of budget and technology informally during the course of the Spec Review relieves the potential for unwelcome surprises during the Spec Review presentation. Canvassing the issues beforehand in casual 'corridor conversations' clears the decks for an agreement, rather than increasing the risk of heated discussions if you surprise a client at a formal meeting.

Some other topics that should have corridor conversations are:

  • Estimated Cost and Time
  • Key Technologies
  • Key Infrastructure

For example, ask the client "...building the cube will add around 2 months of development time, shall we leave this out of the current scope, or do you want it in?"

Ensure that any discoveries or decisions are properly documented.

We open source. Powered by GitHub