I have been asked to help a company review a software project that has been very very painful, putting a lot of strain on the client relationship as well as between individuals as well as teams in the company.
Both based on research I have undertaken previously as well as various blogs I've read on the topic I intend to undertake various stakeholder interviews, attend the project sunset meeting and a sprint retrospective.
I have started conducting causal analysis focussing on:
- Specification: Quality/ambiguity, scope creep, documentation.
- Communication: How were individual issues communicated? how well were the project teams included in the planning process? How did the distributed team (5 office locations - 12 people) affect communications.
- Resourcing and Planning: How well was the project planned in advance, how well were estimates met? Were people available when they were meant to be on the project? Did skills of the people match requirements?
- Causes of Rework: How well were the individual team members qualified for the tasks they had to repeat? How long did it take for completed tasks to be tested and errors to be identified?
- Complexity: How complex were the tasks? Eg. was there a need to include an architect to help a developer plan the design?
When conducting a project review are there any additional areas that you think I should be considering? Can you share best practice for soliciting information and communicating my findings in a practical and constructive way?