I’ve been on the road meeting and talking to Serena customers. It’s always great to get first-hand feedback from actual users of our solutions. What’s even better is when you find out how we’ve helped a customer solve some major application development challenges. I recently visited one of the largest healthcare companies in the United States. Their business is to work with their customer base of corporations, consumers, pharmacists and nurses and help them manage billions of prescriptions, medical claims and clinical visits each year. You can only imagine how robust
In my last post I started to look at the “how” of orchestrating application delivery, specifically macro and micro processes. Here, I’ll continue on with tools, integrations, interfaces and reports.
As we have seen, every application development group has a huge extant investment in technologies to support their efforts. Ripping them out and replacing them with something generic, but integrated, is not the answer.
We need to step up our requirements in the identification and selection of tools for application development. In fact, I
Serena was a sponsor of the Gartner Application Architecture, Development, and Integration conference this last fall in Los Angeles. While we were there, we took the opportunity to survey the conference attendees, and hundreds enthusiastically joined in. The promise of an iPad drawing may have been involved, but I think that the attendees were more motivated by taking the temperature of the industry.
What were the top Application Delivery Priorities?
This is a change from what I have been hearing the last few years, when reducing costs was the #1 priority. More IT and AD professionals identify
We reviewed the first common myth in the development community. Here’s a look at the second one and a possible solution.
One-size-fits-all fits me
So enter the one-size-fits-all (OSFA), one-stop-shop, everything-you-wanted-all-in-one-place tools. These tools try to provide an end-to-end solution that does facilitate the support of the whole lifecycle. The problem is that these tools come from vendors who have to reach a mass audience and so they develop very generic solutions that are entirely agnostic as to your role in the SDLC, your organization’s domain or methodology, best practices, policies and procedures. The big selling point for them is often their
So we have seen that the CIO is starved of data. But let’s take a closer look at what is going on in the development community by looking at two common myths:
Best-in-class is best
Each part of the Software Development Lifecycle (SDLC) is a silo. No matter your role, whether an architect, designer, developer, tester, release engineer or whatever you are blessed with incredibly good technology tools to support your ability to conceive and deliver your part of the
So, here the irony: the person with the word “Information” in their job title. The CIO, has no information about how their business is running.
Yes, I know they think they have information, but the reality is they have opinion masquerading as pretty Gantt charts fooling them into thinking they have data about the state of their business. If we continue to think that going to status meetings is the way to get status we will continue to struggle to run IT and we will never deliver the kind of