Going into Chapter 5, the only thing I can recall is the same topic the other author discussed in Clean Coder was pretty much the same thing. This chapters covered the confidence and necessity to say No during a project when you need to even though it may upset your client. There is a thing called dead-lines which have to be accounted for and these dates tend to cause the most stress in development where in some cases the deadline may or may not extend. There comes a time where your employer want you to add more to the plate even though there is already enough to deal with let a lone there is the fact that unexpected events happen during development which can not stop the deadline from happening. The chapter describes how to professionally say you can not do something as well as give a good reason why to. After all, it may make you a hero.
Interesting enough, this topic instantly reminded me of the Clean Coder book which talk about the same topic and pretty much has similar advice. That is actually a good thing knowing that something you read is reliable especially if different people go by it. I love its mentioned you should provide options if there is bad news. It sounds like you want to make the best out of what you got and not just not wanting to do work.
Chapter 6 covers what is also another aspect in development which is knowing that even though you have something that is functional and working, is does not mean it is the end of the project, the finish line is far from over and the team only hit a milestone. There comes the whole fact of maintenance and on-going support that the software will require after launch. You need to have updates to fix bugs and hopefully add new features, let alone if the developers know how to do so professionally. Speaking of bugs, testing your software profusely is another key part after launch as there are bound to be user reports of certain areas not working, you may never know.
As I like to put it. The end is not the end and even though your software is out in the wild (congrats by the way you do deserve some champagne) you have to give the impression that you care about the product and tell users you are still there for them when they need help using what you created No it doesn’t have to be forever, but a garden does need to be looked after.

From the blog CS@Worcester – Dan's Tech Rant by danbarbara and used with permission of the author. All other rights reserved by the author.