Comments on: Make a place for good things to happen http://leansoftwareengineering.com/2009/06/03/make-a-place-for-good-things-to-happen/ Essays on the Continuous Delivery of High Quality Information Systems Mon, 22 Feb 2010 09:08:24 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: links for 2009-06-06 « Dan Creswell’s Linkblog http://leansoftwareengineering.com/2009/06/03/make-a-place-for-good-things-to-happen/comment-page-1/#comment-5512 links for 2009-06-06 « Dan Creswell’s Linkblog Sat, 06 Jun 2009 12:08:35 +0000 http://leansoftwareengineering.com/?p=1394#comment-5512 [...] Make a place for good things to happen (tags: lean agile) [...] [...] Make a place for good things to happen (tags: lean agile) [...]

]]> By: Corey Ladas http://leansoftwareengineering.com/2009/06/03/make-a-place-for-good-things-to-happen/comment-page-1/#comment-5480 Corey Ladas Thu, 04 Jun 2009 15:11:02 +0000 http://leansoftwareengineering.com/?p=1394#comment-5480 Those are some terrific examples of useful checklists, and you beat me to the punch! Lists of 'common problems' and 'root causes' was exactly where I was going with that topic. Those are some terrific examples of useful checklists, and you beat me to the punch! Lists of ‘common problems’ and ‘root causes’ was exactly where I was going with that topic.

]]> By: Benjamin Mitchell http://leansoftwareengineering.com/2009/06/03/make-a-place-for-good-things-to-happen/comment-page-1/#comment-5477 Benjamin Mitchell Thu, 04 Jun 2009 13:37:20 +0000 http://leansoftwareengineering.com/?p=1394#comment-5477 It's great to hear someone else talking about checklists. I think they are a key part of the reducing variation and improving system performance. We have a checklist to our Kanban board under the final, "Ready for Release" column, which is a checklist of all of the non-scripted dependencies we might have on any particular release. We review this with the whole team (including Support) at the Standup the night before we branch the code for a Staging release and then again the night before our release to Production. We're also improving checklists in the following areas: - List of common issues (application functionality or scenarios) that have meant issues have been returned from development upstream to analysis. - List of common problems spotted in code reviews as part of the exit criteria for the Development Underway stage of our process. - List of root causes of defects raised It’s great to hear someone else talking about checklists. I think they are a key part of the reducing variation and improving system performance.

We have a checklist to our Kanban board under the final, “Ready for Release” column, which is a checklist of all of the non-scripted dependencies we might have on any particular release. We review this with the whole team (including Support) at the Standup the night before we branch the code for a Staging release and then again the night before our release to Production.

We’re also improving checklists in the following areas:
- List of common issues (application functionality or scenarios) that have meant issues have been returned from development upstream to analysis.
- List of common problems spotted in code reviews as part of the exit criteria for the Development Underway stage of our process.
- List of root causes of defects raised

]]>