CRISP



Brad Appleton provided this as a reader submission. Thanks Brad!

Mike Clark gave a 2004 presentation on Pragmatic Project Automation that included a description of what he called the "CRISP" criteria for build. There is a similar description in the 2007 presentation “All Builds are Good”, and a more detailed description in this 2007 CT-SPIN presentation on project automation:

Complete:
• Build from scratch and independently without human intervention.

Repeatable:
• Must be able to create exactly the same build at a later time.
• Store build scripts in source control.

Informative:
• "Detector of unexpected changes".
• Provide information on why a build failed.

Scheduled:
• Let the builds run automatically.

Portable:
• Build should be runnable from any system (same platform), not just that of the developer.
• For cross-platform software, it should build on all platforms.

7 comments:

  1. Jeff LangrApril 3, 2009 at 5:04 PM

    Tim you rock, that's responsive!

    ReplyDelete
  2. AgileotterApril 3, 2009 at 10:27 PM

    But Brad A basically handed it to us ready to go, so really *he* rocks.

    But I might rock a little sometimes, too. ;-)

    ReplyDelete
  3. Dave AronsonApril 4, 2009 at 11:59 AM

    Re "Detector of unexpected changes", that's why, whenever possible, I include a fast subset of the tests in builds. Usually the build target is not the executable, but a "this has been tested since last build" flag-file, that "depends" on the executable and is "touched" after a successful build-and-test.

    ReplyDelete
  4. Brad AppletonApril 8, 2009 at 2:05 AM

    Thanks Tim! (BTW - any chance you'd consider changing the hyperlink for my name to point to my blog (http://blog.bradapp.net/) instead of my homepage? (the latter is sorely in need of updating :-)

    Thanks!

    ReplyDelete
  5. Brad AppletonApril 8, 2009 at 3:40 AM

    As long as I'm on a "rockin" roll, I'll suggest a few other things regarding Agile CM that might be flashcard worthy. One of them mayt overlap with CRISP, so I'm not sure if it ought to be added, but at least one of the following three should be card-worthy:

    • Four Rules for Simple Codelines

    • Five R's of Agile SCM Baselines

    • 5 C's of Agile SCM Codelines

    Personally, I think the first of those three is the most "fully baked"

    ReplyDelete
  6. AgileotterApril 8, 2009 at 7:01 AM

    What would I not do for my fellow alum? Your link is changed. I had started some agile version control content, but then I felt that it wasn't quite good enough and my opinions changed somewhat after initial writing. Lets collaborate on a few of thos. I'll read these and lets see how small and simple we can make them.

    Thanks for submissions to the deck.

    ReplyDelete
  7. Urs EnzlerApril 10, 2009 at 9:15 AM

    CRISP is a must-have if you use continuous integration.
    Nice to have a crispy acronym for that ;-)

    ReplyDelete

Note: Only a member of this blog may post a comment.

Subscribe to: Post Comments (Atom)