Flashback: A Year Ago This Week on Tyner Blain [2006-05-12]

car mirror

A look back at the best from a year ago.

Foundation Series: Continuous Integration

classroom

Continuous Integration is the software development and quality process where all team members merge their code and verifies it frequently – at least daily. This verification project includes both an automated build process and automated testing. The main benefits of continuous integration come from risk-reduction and cost-reduction.

Ten Essential Practices of Continuous Integration

testing mascot

Martin Fowler has identified the key process elements of making Continuous Integration work. You could even argue that they are the elements that define Continuous Integration (done correctly). We include his list and our thoughts below:

Requirements Documents – One Man’s Trash

crumpled paper

…Is another man’s treasure. There are many different ways to document requirements when developing software. And there is a proliferation of requirements documents – MRD, PRD, SRS, FRS and design documents. Everyone has a perspective on what each document represents, and each person on the team has a unique perspective on what questions the document answers.

Post to Twitter Post to Facebook

This article was published on Saturday, May 12th, 2007 at 8:00 pm and is filed under Flashback.
You can leave a comment on this post

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>