Posts

Software contracts that define all software requirements up-front make your project half-way to failure. The software company will try to do exactly what is in it, and the client will try to believe that none of those requirements will change. And at certain part of the project both will realize they were wrong. Let’s face it. Software requirements always change. But it doesn’t mean that people got they wrong, it means that after seeing a piece of working software people learn more about it and they will always have a lot of new ideas to improve it....

Today a lot of people wants to become agile. Well, not agile in the sense of mentally or physically quick, but Agile (yes, with capital “A”) as written in the Agile Manifesto. Why? Because it seems like a better way of doing things. This way involves: Empower people Deliver business value Get the client involved Embrace changes Is the word “agile” good enough to represent all this? I don’t know....