#22: Handling incomplete work

Better ROI from Software Development

In the last few episodes I've started a mini-series introducing some of the tools and practices that allow for the fast delivery of software and ultimately delivery of value to our customer.

In episode 18, I introduced Source Control, what it was, why your developers will be using it and the value it brings.

Following your development team saved their software code to the Source Control, I then introduced Continuous Integration in episode 19. I described how Continuous Integration allows us to find problems faster - allowing us to address them much more cost effectively and making Software Development much more productive.

In episode 20, I introduced Continuous Delivery. It builds on Continuous Integration and make the releasing of our of software as easy as a button press. Through automation we make our release process a repeatable, reliable, easy, non-event.

And then in the last episode I introduced Continuous Deployment which builds upon Continuous Delivery by removing the manual button press - automating the entire process from developer to customer many times a day.

In this, the final episode of this mini-series, I want to talk about how to handle incomplete work.