An Architects Perspective on IT Programme Management

I have managed a lot of IT Infrastructure projects in my time, and a couple of smaller programmes.  I have also keenly observed the management of several large programmes as a Chief Architect.  This article is written from this perspective.

 

Some initial observations:

 

  1. IT Infrastructure Projects generally fail from at least one perspective and often more
  2. IT Infrastructure projects look superficially simple
  3. The programmes have been overly influenced by the personality and skills of the Programme Director

 

The following are a set of Article Titles that I intend to write over the next year or so; they give you a good idea of the issues I think are important:

 

  1. What does he do? The importance of top down Journal keeping to programme communication, coordination and team spirit
  2. The need for a balanced management team instead of Super Men
  3. Management information is a team resource
  4. The customer is not the same as the client
  5. Objectives and Requirements, why they are different and both important
  6. The importance of programme maturity reviews
  7. Conceptual integrity and how easy it is to loose it
  8. The lost art of estimating – take different perspectives
  9. How to plan a programme, top down meets bottom up and debates
  10. Why has my green programme suddenly gone red, (see next topic)
  11. How to milestone a programme
  12. Avoiding death by meetings
  13. The importance of “assumed responsibility” to successful scope management
  14. The importance of “eating your own dog food” and “daily builds”
  15. Achieving autonomous – coordinated – motivated teams
  16. Making the most of a co-located team
  17. Mitigating the risks of a virtual team
  18. Risks, Issues and Change a collective responsibility
  19. Key programme documents and processes
  20. Dangerous metrics and incentives
  21. Understanding the relationship between DCO,TCO and TVO
  22. The “red team”, or what to do when it all goes wrong

Steve Richards

I'm retired from work as a business and IT strategist. now I'm travelling, hiking, cycling, swimming, reading, gardening, learning, writing this blog and generally enjoying good times with friends and family

3 Responses

  1. Anonymous says:

    I think you need to focus on few ‘differentiating’ articles:

    – Needs vs. requirements vs. in-scope deliverables.

    – Quantifiable value delivered vs. cost of deliverables.

    – Top-down design vs. bottom-up implementation planning.

    I look forward to reading AND USING your ideas.

  2. Anonymous says:

    Feel free to contribute some articles along these lines, although I think these are good topics worthy of my own effort as well. Others have provided other ideas and are going to contribute. You never know we might build an alternative body of knowledge 🙂

  3. Anonymous says:

    A friend of mine wants me to add:

    – Don’t assume people understand or do basic project management

    – Manage the message

Leave a Reply

Your email address will not be published. Required fields are marked *