Agile release planning, Agile narratives

I seem to have acquired a reputation for being the continuous integration troubleshooter.

I’m starting to think continuous integration is the second “forgotten practice” from the first XP book (remember “system metaphor”?). Sure, everyone talks about it and everyone’s doing it, but a lot of places I’ve seen aren’t really getting it right. And why is that? I think because those two innocuous words sweep a considerable number of issues under the carpet.

Books

Summaries of the books that should be on your bookshelf.

34 signs that continuous integration isn't working

  1. When a newcomer arrives on the team it takes weeks of copying files off other people’s computers to get something to build.
  2. Everyone has a different set of projects checked out on their PC.
  3. You don’t have a master build script that builds everything on any PC.

… etc.

6 tips for avoiding antiwork

Antiwork is work that has negative value. After you’ve done some anti-work you are worse off than when you started. Usually you or someone else will have to put in extra work in order to recover lost ground. Antiwork has the same relationship to work that antimatter has to matter - it cancels it out. So how do we avoid it?

What is increased capability?

How do you know you’re getting increased IT capability? Some examples.

Why things happen

A brief list of the reasons why things happen in organizations, including unexpected things.

Syndicate content