Archive for the ‘Evidence’ Category

Process In the Fabric

Monday, November 21st, 2011

Say you’re in a truly disciplined, lean and agile operation and your processes are so deeply ingrained in what you do that putting your finger on tangible evidence is a challenge, and not for lack of process.  Just lack of being able to step back far enough from the canvas to see the whole picture.  What do you when it comes to demonstrating your practices for a CMMI appraisal, for example?

Well… the best advice I can give companies in such situations is to work early and closely with a consultant and/or lead appraiser to elicit the best evidence for the appraisal long before the appraisal event itself is planned or carried out.  It’s important to be clear about what the evidence is, and, you want the appraiser and the appraisal team on board with how the evidence will “show up”.  This is not something you want to surprise anyone with come appraisal time.

Working early and closely with a lead appraiser will not only help everyone understand the context, and not only will it provide an opportunity to strengthen practices and identify operational risks, but it will give you a good idea about whether or not the lead appraiser has the wherewithal to think broadly about practices and to assemble the contextual picture for how practices would “show up” in the context of your operation.

Sadly, not all appraisers have this skill set.  In fact, in my experience, the great majority do not have the skills to make contextually relevant model interpretation such that actual, naturally-occurring evidence from an operation can take its most natural form and still be recognized as implementation of CMMI practices.  In my experience, most lead appraisers expect evidence to come in very specific shapes, sizes, and colors and they don’t recognize the evidence when it doesn’t meet their pre-conceived notions of what particular evidence should look like. 

That being said, this does not give carte blanche for not having evidence.  I’m not saying that the evidence isn’t there, I’m just saying that the evidence may not be what’s traditionally thought-of as evidence from larger or more traditional development operations.

Process evidence from operations whose processes are deeply ingrained can often show up as very clear, obvious artifacts.  Especially from traditional development operations.  However, in small, lean, and agile operations, the evidence can be much less obvious.  It is a special skill set to be able to recognize the outputs of such operations as evidence of CMMI practices and organizations are served well to work with the lead appraiser early to determine whether or not their operation produces evidence as well as whether or not the appraiser can see more broadly than the evidence they’re used to seeing from traditional operations.

Since few organizations know how to pick a lead appraiser, perhaps this “litmus test” for a lead appraiser can serve to help them through the process.  The alternative could be a disastrous paper-chase to create evidence on top of the evidence that’s already there.

SEPG North America – Day 2

Wednesday, March 24th, 2010

Sorry, folks, no fun (or not-so-fun as you may prefer) video today.  Not even any pictures I took at SEPG.  In fact, as far as today went, I don’t have much to report from the sessions.

Again, I missed the plenary session.  This time on account of a phone meeting with a client in another time zone.  So, my first session to attend was the other of my two collaborative efforts with Judah Mogilensky on SCAMPI Evidence from Agile Projects. As anything with Judah in it, it went rather nicely.  Many generous bits of feedback.  I felt really good about my role, and Judah was his usual incomparable self.

My friend and colleague, Eileen Forrester of the SEI was kind enough to give me some supremely powerful feedback.  I am, and will be, grateful for it.  I was then roped into shop talk about CMMI for Services in advance of the 2nd half of the orientation workshop I’m helping her with.  Thus, my missing out on my buddy, Jeff Dalton’s, excellent (so I’m told from many reports) job with Encapsulated Process Objects.

One point made to me later by another of the few “agile-friendly” lead appraisers, Neil Potter, about a bit of content in the presentation does require some follow-up.  In the presentation we short-cutted the details on a discussion regarding the potential design aspects of test-driven development with an engineering design.  I should say that TDD is NOT the same as a design, but that depending on how TDD is planned and performed, it can include design-like attributes which could accomplish design expectations in the engineering process areas of CMMI-DEV.  So don’t anyone out there go around blabbing some “Hillel said TDD is Design!” crap.  Mm’K?

After lunch, my job was to keep people from falling asleep with a session on Love and Marriage: CMMI and Agile Need Each Other.  From the response, I think it went went rather well.  I, personally, was quite pleased with how it came off from a “talk per slide” metric.  A good friend, Tami Zemel, later admitted that she “takes back” her earlier criticism of Monday’s presentation.  She said it had too many words and didn’t believe me when I told her why.  She complemented not only the picture-centricity of today’s pitch but also the delivery, style, and content.  That was very generous, thank you.

From then to the end of the day, I spent scheming, strategizing, shmoozing, and networking with too many people to mention.  (No offense.)  A client who came to the conference (who never holds back and only inflates the truth when it’s funny to do so) got very serious when a prospect I’d recently met off-the-cuff asked whether he’d recommend me.  I won’t repeat his answer because it really was just crazy nice.  Today’s interesting photo is in his honor.  (And also because my boys love transportation.)

The last “session” was a Peer 2 Peer double-header on the topic I mentioned on Monday which I co-created with Michele Moss.  She and I are also on the SEPG Conference Program Committee.  We used the feedback and other data from the Peer 2 Peer as input to a retrospective on this year’s conference, which will be used for strategies for next year’s conference in Portland, OR.

You can also read an entry I gave to the SEI for their official blog about my impressions of this year’s conference-goers.

Dinner conversation back at the hotel with Michele was back on the subject of our Peer 2 Peer session.  Net result: We single-handedly wrote the 1-3-5 year plan for all SEPG’s.  Or at least we think so.  ;-)