Software projects are not a pain because your colleagues decided to go with MS SQL Server, instead of Postgres (Sorry, @Joe Celko) or because you used Wicket instead of the latest Haskell web framework or Ruby instead of Java. That thinking is backwards - tools are just a means to an end. Your line-of-business customer really does not care what technology you are using, at all.
The problems almost always start with requirements. Too vague. Too broad. Ever-Changing. Hidden. Underestimated. Overestimated. Sounds familiar?
No matter your coding skills, you cannot fix basic requirement problems with code, programming languages or frameworks. You have to learn how to work those requirements. Clarify them, deconstruct them, make them real crispy. THEN you continue with estimation and planning. THEN you start to code, test and ship.
It might be that you think you are too smart too fiddle with customer problems, instead of challenging coding problems. "Where can we make use of that sexy NodeJS??!? Don't we have people whose sole job it is to deal with requirements, my business analyst, for example?".
If you are thinking like that, you do not see the importance of proper requirements in every single step of software development. Your vision is clouded.
Imagine you would not have to strangle your boss anymore.
Imagine you know all the warning signs when a requirement is too vague to be implemented. You know how to push back and get more information, instead of blindly starting to code - code that you have to throw away again after some weeks.
Imagine your estimations get so accurate and your communication so good that the only one doing his last death march is the headless chicken? (hope that made sense! ;) )
Sounds too good to be true?
This book is not a hastily put together document. It is rich in detail and examples. It is designed to let you learn. And to implement. Instead of being just another theory information dump. Here is what you will take away from this book:
Videos (Premium only)
Audio Interviews (Premium only)
That mostly depends on your budget. Obviously the premium package is the best. I truly wish I would have had those screencasts at the beginning of my career.
But the book itself, with its examples will still completely change your work with requirements.
No. You can literally put the book wherever you want.
You can also buy digital editions of this book at Pragmatic Programmers. Print versions are not available at the moment, unfortunately.
Go to marcobehler.com, read the homepage and check out our blog.
If you didn't learn anything from this book and hated it, I really don't want your money. Just reply to your purchase receipt email within 30 days and I will issue a refund. It is my 30 days, 100% Money-Back guarantee. And yes, everyone says that, but I will give you the money back with a smile.
The download is instant. After you purchased the book, you will be sent an email with the download link to the book and any accompanying material.
If there are any payment related problems, give me a shout at firstname.lastname@example.org.