Join us for this live webinar — Mixed Methodologies Pt II: Building successful outcomes — on Thursday, June 11 at 10 a.m. Pacific, 1 p.m. Eastern. Register here for free. 

Say “Agile product development” around the office and you might hear a boo or a hiss. Agile has gotten a bad reputation over the years — and some big organizations stop using it before ever diving into the larger value features of Agile. I’m referring to things like continuous and agile deployment — concepts more apt to earn sneers and groans from those who view Agile as a path to sluggish productivity and shoddy apps.

On the ops side, many businesses just can’t front the organization and tools to make a continuous deployment work. There’s no buy-in and they just don’t get it. Instead, they cling to the traditional approaches like safe harbors that deliver predictable — but diminishing — value to the business.

It’s time to go hybrid.

In order to get leaders to to see the true benefit of agile deployment, we have to take control of the deployable application artifacts. We need to understand who created them, for what reason, from where they were derived, and how.

Take Netflix for example — the app’s prediction model for how and why you might want to watch a certain show doesn’t work all the time. In fact, sometimes it’s just plain wrong. This failure to accurately predict would have never made it out of a waterfall development model, and might still be stuck in the agile development with that single goal in mind. Does that mean the app is a failure? Thousands of customers would disagree. It gets the job done. Not perfectly but it serves the business model and the customer walks away happy.

Agile has more value in some aspects of the application development lifecycle than others.  While organizations are changing around the notion of Agile, it’s healthy to take a close look at what’s practical as to the successful design, development, and deployment of new or existing applications.

Most enterprises encounter minimal risk when building an Agile organization if planners use the proper business case and automation technologies. You need to at least define the value of these approaches and technologies.

Last month, we talked about how waterfall and Agile methodologies tend to be at opposing sides of the field. This month, we’re digging into a successful development culture that relies upon mixing Agile and traditional application development methodologies. We’re going to focus on outcomes, or what we know works.  Most importantly, we’ll also talk about what doesn’t work and the traps that should be avoided at all costs.

We’ll deal with the tough decisions that enterprise development project leaders and ISVs have to deal with today as they move to more “modern” approaches. What’s more, look at how the cloud, big data, and the Internet of Things are driving even more innovative thinking around development methods. If you’re moving to Agile, or even thinking about it, this is a must attend.

After this webinar, you’ll:

  • Discover what works when mixing traditional app dev techniques
  • Automate Agile principles while deploying new or existing apps
  • Learn how cloud and big data can complicate the Agile scenario
  • Avoid the pitfalls of bad development strategies

Join us on June 11th for this free VB webinar. You don’t want to miss this one.


David Linthicum – Senior Vice President; Cloud Technology Partners

Rich Morrow – Principal Engineer; quicloud

Nick McCleery – Agile project manager; Workfront


Wendy Schuchart, VB Insight analyst

This webinar is made possible with the support of Workfront.