Wednesday, October 28, 2009

Compuware - The Definitive Guide to APM

This is an web book from RealTime publishers nexus.realtimepublishers.com Currently, only half of the chapters are delivered, so here is what it is!

The Good: Emphasis on the process gap and organization maturity as the real barriers to APM success. It includes small vignettes of IT life at the start of each chapter, to highlight to IT situation and challenges. They even define the "M" of APM as Management, not Monitoring. They avoid the word "Dashboards" in favor of visualizations (cool: brings reports back to the table) and mention "application lifecycle" a few times, like "APM optimizes the application lifecycle". And, my favorite: "measuring performance is a proxy for understanding business performance".

The Bad: It purports to "take you through an entire implementation" but doesn't offer any depth. It is more of an extended whitepaper. It does cover the lifecycle of the motivation, decisions and implementation of an APM solution but as a conversation of what could be done. They only acknowledge stakeholders as SysAdmins, Developers and End-users (the guy using the browser)

The revelation for me was that they dredged up a Gartner Maturity Model from 2003 that had some interesting contrasts with the model we derived from our internal analysis of implementation failures and successes. Gartner identified management maturity as "Chaotic, Reactive, Proactive, Service and Value". Our model allowed for "Reactive, Directed, Proactive, Service-Driven and Value-Driven", with Reactive further divided as Reactive-Negotiated and Reactive-Alerting. I don't get too much access to Gartner stuff but here is how I represented Management Maturity:

This is from the first ICMM positioning around 2005. I don't recall why I decreased the size of each box, from left to right. I think I was trying to emphasize efficiency or proportion of IT organizations that might be found practicing at that level.

"Directed" is using APM metrics to influence the application lifecycle, focusing on QA practices.

"Service-driven" - everybody has this goal, we only tried to put teeth into it by associating it the definition of best practices.

I really liked this slide but it is not the emphasis we have today. We focus more on "visibility" because it provides a more "joining" context among the various tools that are available and their contributions, rather a focus on a particular technology and excluding all others. We also highlight the impact that visibility has on the existing processes in an organization and how this helps us assess their maturity and make meaningful recommendations for remediation.

Management Maturity and the processes that go along with it are the foundation of the Compuware APM message. That's not so bad. But then they fall into some unusal partitioning of APM in order to highlight their transaction monitoring technology. So I conclude that while they are saying the right things they regrettably recast APM as something that their technology delivers - and you only need to look at transactions.

Process re-engineering is actually pretty difficult and for well-established and reasonably successful, Reactive-Management organizations, this message is just way too hollow. These prospects know a lot about processes and may even know where they have gaps. What they need instead is a plan to help them evolve the organization, consistent with APM. What can they do now, and tomorrow, (and without purchasing new technology) that will get them on track to APM? What will derail their efforts? How will they know they have improved the situation? When will investment help accelerate their drive to APM?

Like Neo (Matrix) - Stuck on the subway platform

Still waiting on the proposal acceptance. Editing assistance contract, version two, is off to legal. Some business challenges and a bit of reorganization have pulled attention away from the project. Thankfully, the marketing folks tripped over an APM book project from Compuware so now they are beating the drum to help get the oars moving on this boat!

I've started outlining sections on Triage and Maturity Models. These are both pretty big topics and left out of the initial outline but it might be useful to have them ready in case the 'editing' decimates the current block of content.

Currently, I'm at 30k words or 60% of my initial target but really didn't make much progress in October. All the ducks are lined up, in terms of the process obligations. It feels like my flight home is cancelled and I'm waiting for a schedule update - no meeting at risk - just my own time!

Saturday, October 3, 2009

One Writer, Dozens of Editors

Not quite back from vacation I foolishly moved my crackberry from stun, to loud, and shortly thereafter received an invite to join an unscheduled (for me) conference call with the internal publishing group. I was a couple minutes late to the call but quickly learned that there is a lump of process to follow, none of which I had been aware of earlier. Yikes!

I'm about 50% complete with the first draft, of which such status I share when asked. I never expected to hear "Stop right now! You can't start writing until your outline is approved!" She was serious! Apparently, they expect he process to be followed and there was some concern that I would be wasting time writing now, when the outline my very well be changed.

I don't see this as much of a concern. Frankly, I would prefer to cut-n-paste from too much material, rather than come up short and have to write new material from scratch. The whole purpose of this projects was to re-purpose the work I had already done, in presentation and white paper form, and bring it all together into a single, cohesive book experience. So I'm wondering what the editors will come up with, to strengthen or reduce the outline. So far, some internal reviewers of the outline have simply determined that "It looks good. Get-er done!". My simple goal is to not be the bottleneck in this part of the process - the writing. Whatever it takes to get it into book form - I don't have any control over that. But metering the pace of writing - that doesn't seem very sportsmanlike.

But it was concluded that I needed to prepare and submit a book proposal, which would include a detailed outline, resume, and a whole lot of other stuff that the marketing folks will need when this project goes to press. And it needed to be done ASAP. So I got it together, updated my resume (which I hadn't done for over six years) and pushed out the goods Monday night.

Silence.

So far.

On the contractor front, that seems to be going well. I've chatted with my so-to-be-anointed collaborator/editor/I've_done_books-before dude. We have the first draft of their services proposal. I have that into our internal team for review and comment. The 'hot potatoes' are off in other hands. And I keep chugging along.

Part of the book proposal application was a couple of questions along the due diligence theme. Has someone else covered this topic? What publications have a similar theme? What makes your book different.

I took a moment to pause and reflect. This could be a useful bit of exercise. I've always popped off a google search, from time to time, to see if anyone has done something significant for APM and never came back with much. But them I was a little bit more biased towards performance of distributed architectures and not simply Application Performance Management.

After a concentrated effort, I starting finding a few leads. I had a moment of panic - "Crap! Has someone beat me to the punch?" But on further review, a couple of good ideas but not at all the message I'm planning to drop on the Industry. So what am I finding? I'll lay that out over the next couple blog entries.

Tuesday, September 22, 2009

Funding is confirmed

Off on vacation I received an email that funding was to be approved. I'll get the details when I get back to work next week. I immediately sent off a notice to the editor candidate as we still have to do a final interview. I think everything will be fine but you just can't know until share the plan, goals and concerns.

Saw some corporate messaging around PCMM - People Capability and Maturity Model, as part of an HR initiative. Maybe influenced by the earlier ICMM - Instrumentation Capability and Maturity Model... but that might be too bold an assertion. Still nice to see some parallel efforts to document the skills, process and competencies appropriate for a body of experiences.

Before vacation, I got pulled into a firefight of a stability/scalability issue. No QA testing was possible, so we went into production with a default configuration. With the holiday weekend, we got 5 days of data before the issue was reproduced. This is an excellent scenario as the application team was unaware that monitoring was deployed so far in advance, so they immediately suggested that "probably the monitoring was the culprit...". The bridge call got quiet quick when they learned that we had been running without incident for 5 days already. Then the monitoring team dug right into the heart of the matter - the load had tripled. Was this something that was tested? More silence on the call. Simply put, the app cannot scale to the load that was delivered.

We also had a CritSit team from another major vendor who were proposing getting some instrumentation in place, checking logs, etc. - they would need about a week. While that monologue unfolded, the monitoring team generated a report with the bulk of that info and circulated via email. The critsit team scurried to open up that pdf, we reviewed it a bit and then they realized that we had already everything they were proposing. "So can we all agree to start looking for the bottleneck?" For me, that means time to come off site. The job is done and vacation awaits!

At the onset of this engagement, there was considerable pressure to deploy all kinds of functionality. Sales is anxious to sell something - which is always the case and wants to use the firefight to showcase the product. But this is extraordinarily risky without some time (a few hours) to test those configurations in the client environment. So you go with the smallest configuration that offers reasonable visibility - I'm only interested in getting visibility into the nature of the performance problem. In this case, we could only manage some manual exercise of the application while the testing environment itself was having problems. We got about 500 metrics, which is much lower than expected for this kind of application but enough to verify that major entry points were being seen and transaction travces had good visibility. On initial deployment to production, this increased to 2500 metrics. But this was also too low as the bulk of usage had already transpired for the operational day. After 24 hours we had increased to about 5000 metrics and this remained consistent over the next few days.

When the problem is not easily reproduced, and QA is not useful, you need to focus on helping the monitoring team to understand what 'normal' is for the application. We I first look at an application, I have a lot of experience to bring to bear for similar apps. So I have an idea of what is correct and what is problematic. This becomes more accurate, as operational visibility accrues. I'll build the initial report based on my findings from the QA exercise but I'll shortly have the monitoring team do the mechanics of generation. For the first day, we will have them transfer the metrics repository, so I can (working remotely) generate the report AND confirm that we are getting the major points of interest. I then give them the report template (part of a management module - jar file) and have them generate the report. Transferring the metrics archive (via ftp) can take 30-60 minutes and a little work. Generating the report takes a couple minutes, and can be sent via email. As we transfer responsibility, the workload actually decreases. So push back is never a problem here.

We will go through the report each day, illustrating how to present the information in a neutral fashion, indicating the what appears normal, or abnormal. After 2-3 sessions, the monitoring team will begin to review the report on the bridge call. I'm just there for air cover. The goal is to get everyone looking at the same information (the report) and understanding 'normal'. When the event is encountered again, the practice of the report review directly contrasts the 'incident' with 'normal'.

Very often the bridge call is little more than a shouting match. Participants have access to their own data and information about the nature of the incident and "orally" share this on the bridge. There is a lot of subjective reasoning that goes on that can be a distraction and ultimately counterproductive. Everybody wants to add value but but the conclusions are not always consistent. Being able to quickly share the baseline of application performance simply puts everyone on the same page. It also addresses a major gap with bridge calls - no access to historical information. Simply having a 24 hour report, every day, is enough to change this shortcoming. Initially you will have to spend a bit of time educating the team in how to interpret the metrics, explain some language and terms - but most teams come up to speed quickly.

Of course you might think that getting everyone access to the workstation displays of performance information would be even better. However, most organizations are simply not yet sharing information, even a simple baseline performance report. You have to establish this process and skill level first before you introduce the richness of the workstation display. Otherwise, the team will get distracted, confused, or frustrated - and they will never even get to the baseline information.

Tuesday, September 1, 2009

Awaiting Funding

The last month was a bit tedious but I was earlier invited to propose a book outline that covers all of my exploits and learning while assisting clients in their realization of application performance management. This blog will cover those developments leading to the publication of the book and the feedback on the book once it gets released to the public at large. I am optimistic that this will happen, even as a small issue of funding remains in limbo.

I have been at this crossroads a few times before. While IT organizations, in general, would benefit from a thorough discussion of this topic, product management is not fully on board. A good part of this is because the techniques are largely vendor-neutral. This is important because the marketplace has matured and only a few players remain. Of those players, only one is in growth mode and continuing investment. It is believed, by some, that releasing these best practices and understanding of the marketplace will give these ailing competitors a second chance. My view is that by educating our potential customers, and helping them utilize their existing investments (even with competing tools) that we will increase their pace of adoption and they will naturally choose to partner with the stronger player. Fortunately, sales already knows that this approach will accelerate adoption, and thus license revenue. Getting these techniques in book form simply scales the number of interactions we can support. Who will win out?

The book will be based on my library of presentations and discussion papers which, to date, has been limited to client engagements and internal training. Public notice of this body of work is limited to a single event, in November 2007, where a reporter wrote an unauthorized story about a presentation by one of my clients where they discussed how they had establish a Performance Center of Excellence and was practicing true, proactive management of their application lifecycle. That's a lot of buzz words but given that it was done largely with their own staff, and had already demonstrated value, it came as a bit of a shock, compared to the much longer periods that such IT initiatives need in order to show some success. There were some services, of course. I led that initiative and a number of other similar programs, in what we call the "Mentoring Model". I've seen things...

Anyway, this single event launch a number of sales initiatives, based on the concept of quickly building client teams and following our APM Best Practices, to dramatically increase the pace of adoption of APM Tools, and the value realized when employing these tools. This resulted in a remarkable quantity of deals, each in excess of $10M in new product revenue. None of these deals had services attached to them, which is both annoying (I'm in professional services) and illuminating. We will still do some services with these clients but it will be of very high value and limited duration. Not at all like the large staffing and long duration of traditional IT initiatives.

What is this APM marketplace? Why does it warrent such investment? What kind of value does it return? How do you get started? What are these APM best practices? How do you build your own team? These are all topics which the book will present and discuss. It is a topic that I believe the world needs to know about. But I am largely constrained by the proprietary and confidential nature of my work - so my employers' commissioning of this book is an essential piece of the puzzle.

Historically, in my career in the commercial software business, I have been at this precipice three times already, in having a large body of internal-only materials, and a marketplace starving for guidance, direction and illumination. Is this fourth time the charm? One of my mentors had suggested, a few years back, that no one can fail when they listen to the customer and find a way to give them what they need. I've got it all together this time. I've kept the faith. But I really need to see it happen... once!

Now if I can only get the funding to bring it to light.