One of my favorite project manager (Vicki Boswell is her name) in my first company, once emailed me on a project post mortem that said something like: "Vasan, it is surprising how we have have felt about the project in same ways at different times." I was working from bangalore, while she was managing project from San Diego (I miss this place). I had mentioned the frustrating times, the enjoyable times, the lesson learned at different stages in project. The specifics differ from developer view and manager view. But the net enthusiasm was the same.
Many causes, affect this heart and mind frame of teams in both sides. Few instances when
- A project is dragged on for long, due to shift in commitments.
- When more than 3 solution options are considered and stay on for an extensive period of time.
- When feedback comes at a late stage that circles back the team few steps back.
- When "escalations" are used in bad sense of word.
- There is a lack of clarity on overall purpose or objective. In my first company the first question senior management ask any resource is "What is the order value of the project and what are you doing about it?" I find it a powerful thriving question to bring bond with business, project and bottom line.
- There is lack of a strong voice in the project from either side.
- There are no night outs and no fight outs. Every thing going on smooth makes me paranoid. We know something is failing when there is no noise from a running engine. Atleast a good "hum" is required to ensure that all is well.
- The project is allowed to drift to satisfaction of multiple people. Developers take their pick to work for day. Architects document functionalities to bring their "uniqueness" and stretch the limits of technology. This is no democracy. Drift hampers jiveness in team.