This week’s Quick Links (first in a while)
Johanna Rothman asks: Why Does an Agile Coach Need to Know a Specific Programming Language? where she asks about a Job Ad that asked for an Agile Coach who knows C++. While I agree that not all Agile Coaches need to be technical, alot of my work is to coach team members on technical skills i.e. TDD, Unit Testing, OOP, etc. In those cases my understanding of C/C++/C#/Java/… is critical. However I do agree that in general an Agile Coach doesn’t need to be uber-technical.
Speaking of technical Jeff Langr and Tim Ottinger give us Test Abstraction: Eight Techniques to Improve Your Tests. I especially like “Bloated Construction” because I frequently see test methods with so much test setup that it obscures the actual test.
Steve Denning offers Measuring What Matters: From Outputs to Outcomes: Part 3 – music to my ears. Too many organizations look inward to measure. Steve has written a series on measurement (see also: Part 4: Measuring The World’s Most Neglected Competitive Weapon: Time).
In An Agile Pace Tim Ottinger shows why constant overtime harms your project. As I said in the comments: “As a soon as I saw this I started looking for a reference that I still can’t find. The reference suggested that we’re only productive at “cognitive tasks” for about 26 hrs a week. Sadly no luck so far.”