Recently, on a flight to Bangalore India and in the ensuing boredom I struck up a conversation with the passenger sitting next to me.
After a short chat it was clear we had something in common professionally. It turned out that “Mr X” was a senior software engineer for Honeywell and responsible for the developing of new fly-by-wire flight systems.
“Wow” how interesting! A branch of IT I knew little about, and an opportunity to learn something new.
I rarely mention by name organisations who I have done business with in the past. However, today I want to mention a little known IT consultancy called Avanade. It is a company born out of a unique partnership between Microsoft and Accenture and is a global IT player specialising in the Microsoft platform. It is not Avanade’s undoubted technological expertise which fascinates me, its the organisations ability to deliver outstanding profitability to its shareholders and world-class delivery capability to its customers.
The pursuit of excellence is a means to an end for Avanade.
Most project managers are aware of UML, even if they haven’t used it themselves.
However, having worked as a Business Analyst on a number of ‘UML projects’ I believe that many Project Managers don’t really know how to use UML requirements gathering techniques to maximise the chances of a successful project.
I am going to try to help you understand some of the pitfalls and issues that are all too often encountered when setting up a UML based IT project.