Surviving at the Software Industry. (1)

I liked the way the book "speaks" to me when I'm reading it, it feels like a guru giving you advices to succeed on the development of a project. Every software project that is considered low or medium size is achievable and optimizable.

The steps commanded by this guide are well explained and pretty basic. The first one is to recognize a software project’s essential survival needs, then it compared a project with a human and its needs illustrated by Maslow.

The author shows us how the needs of a software project look a lot like the human ones by adapting the Maslow’s Hierarchy onto Software needs.

We also learn about the Customer’s Bill of Rights, which are 7 actions that the customer has access to, such as objectives, time of development, features involved, change of requirements, project status, knowledge of risks, and ready access to deliverables.

On the other hand, he have the responsibilities of the Project Team’s bill of rights, these are the actions that everyone involved in the development of the project have to follow. To clarify priorities, to build and clarify the product definition, give the costumer ready access, etcetera.

What we learn today is that the 3 keys of success are communication, communication and communication. (Or at least for the success of the first step).

We shall continue with the second step soon! So I’ll keep you posted.