1. Project Management
The characteristic of IT projects is that the client knows exactly how its future software will work... only once the project is ended.
It is therefore advisable to work by iteration, adjusting the project little by little when the customer understands more deeply his needs (RUP, Agile, Scrum, Lean ... all are Spirals methods).
However this method is not always possible. That's why in many cases the client must adopt a predictive approach. The challenge is then to precisely define the customer's needs early in the project.
Iterative Method like a Spiral
|
Predictive Method like a"V"
|
| The IT team belongs to the client's company |
The IT team is a outsourced supplier |
| The client does not know precisely what he wants |
The client knows very precisely what he wants |
| The project is not that critical |
The project is critical |
| Developers are seniors |
Developers are juniors |
| The team consists of maximum 10 developers |
The team consists of over 10 developers |
| The company has a malleable culture |
The Company has a rigid culture |
| Learn more about the Iterative Method in "Spiral" |
Learn more about the Predictive Method in"V" |
2. UML as a Translator tool
Communication between the (future) user and the IT team is a major challenge for any IT project, the first having a Business point of view, and the second having a technical point of view.
To overcome this difficulty, we use Unified Modeling Language (UML) as a translator tool.
Indeed UML represents processes and business objectives of the project through different graphs, making them much more understandable for both (future) users and IT Developers.See more over "UML as a Translator Tool"
|
