During my years as a consultant and owning my own design firm I noticed that many projects failed to deliver on time and/or on budget. Mostly this has nothing to do with the client or the consultant as it is a process problem.
This book is an attempt to describe a process that I believe works for large and complex IT projects as this is where I have my experience. This is also where I see that other ways of working fail most.
The result as I see it is that projects become more costly and that the people in the project will need to work more than necessary causing stress and sickness in projects that are either too rigid or to lose and a middle ground is needed.
In this book I will describe the problem as I see it with the various Agile and Waterfall methodologies. I will describe the process that I use in my projects with the ideas behind each phase. The aim is to give you an understanding of how this process works and why so you can use it, in full or parts of it, in your own projects.
Before you start implementing what you find in this book however I want you to take this to heart: This is not a bible or a one size fit all solution that will solve all your problems. Implementing a work process or methodology is not something to take lightly because it has real life implication on people's health. This is why you should base the way you work on the people, not the process or methodology that happen to be cool at the moment.
If you see that the people need something else than what is being described here, then you should make the change for them. If you keep the basic need in the chain intact, then you can make changes without disrupting things in other parts of it. People a far more important in any situation so make sure you have their best in mind when you implement work processes and methodologies.
Recommended Comments
There are no comments to display.
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now