Welcome!

Microservices Expo Authors: Liz McMillan, Pat Romanski, Stackify Blog, Jason Bloomberg, Elizabeth White

Related Topics: SDN Journal, Microservices Expo, Microsoft Cloud, Containers Expo Blog, Agile Computing, @CloudExpo, @BigDataExpo

SDN Journal: Blog Feed Post

Agility Is Not a Methodology

There is a reason why absolutists always fail in technology

Lori and I were discussing the entire topic of agility the other day, she looking at it from the SDN prospective, and I from the evolutionary perspective for development. While I know there has been a metric ton of writing about the topic, since I’ve used agile development, and find it to be useful, but didn’t become a fanatic on my first agile project, I thought some perspective might be in order.

There is a reason why absolutists always fail in technology. Not just because high-tech is always changing – which makes absolutism fleeting at best  - but because the part that determines whether computer scientists get to be absolutists on topics as varied as “object purism”, “No [fill in mobile device since first Palm] on my network”, or “We’re an X shop” is not at all scientific. Nor is making absolute statements, unless you’re discussing a proven fact.

Money and by extension people’s productivity determine what kind of shop you are, what you use or don’t use, what standards are set in stone and what are not. And sometimes the market. I used to work with a network manager that told me “We’re a Nortel shop, we’ll never use anything else.” Uhhmmm… Wonder how that’s working out for him.

And over the last several years, agile/lean development has that air of “My OS is better than yours!” to it. In these back-and-forth discussions, I have tried to maintain perspective, no matter what topic is polarizing my fellow geeks this year. What you like is irrelevant. Use the right tool for the job. Sometimes, that’s not your favorite, because frankly, there are no silver bullets.

Don’t get me wrong, I firmly believe the evolution of agile is what finally broke the “Mythical Man Month” mentality that had ruled over and held back IT as badly as Hume has decimated philosophy with regards to actual science. I hate that they let Hume hold them up while science continues to forge new ground and face issues that philosophers could help with, and I hated that IT shops believed there was no faster way to get code out the door once the team was bigger than one person.

Agile improved developer productivity through a variety of methods, but I feel the biggest was focusing on one thing at a time and reducing non-coding activities. All in all it is a great improvement.

But our field of endeavor tends toward zealotry, and the agile pundits out there sound alarmingly like the cloud pundits or any of the other absolutists we’ve burned through in the past 20 years or so “all other things are obsolete, we have our flavor of agile now!”. I’ll agree that agile methods are right for a huge percentage of IT projects, I just won’t agree they are for all IT projects.

The thing is, there are cases – more than one might think – where agile isn’t the best solution. The larger the code base, the larger the team, the more distributed the team, the less and less it a project is suited to agile methods. Oh, like so many methodologies, you can force-fit it, but I’m talking about best solution, not possible solution. And the more documentation required, well, agile teams don’t tend to excel in that department, viewing a document as a waste when you could be writing code. And that doesn’t even touch on the array of things like “don’t generalize for re-use, you can’t predict the future” slamming into “We are building a corporate repository…”

But the thing is, like all such methodologies, it does introduce some great tools to be put to use even on projects that don’t lend themselves to its overall methodology. And some that hold it back even when the methodology is the right one. Sponsors vary in actual support from “assigned to me, whatever” to “we really need this, what can I do to help get it right?” And that is just the nature of any methodology that requires sponsors for each project. Just as drafted militaries tend to be lower quality than volunteer ones, the sponsor process includes both good and bad.

From the good bits, breaking the problem down as small as possible is a great way to achieve focus, just  beware of blinders. The future is coming, and sometimes you can reasonably predict it. Others may need to re-use some of the source – assuming the team didn’t write it so specific as to be useless, and where documentation is concerned, the team needs to focus on new developers a couple years from now, when the SMEs won’t necessarily be available, not the minimum to communicate today.

But the most agile thing that comes out of agile? Business management is now aware that development can be faster than (maximum estimate X 2, measured in the next highest unit of measure). Agile projects are sometimes late, just as any other, but they are generally tracked better by the nature of labor division, so expectations are managed better. And upper management can now drive the mentality that will make IT more responsive.

And in the end, that’s the point. If senior management says “agility is our goal”, and is willing to put the money and effort behind it, the fact that some projects are better suited to other, more overarching methodologies doesn’t matter, but saying “We need tool X and it will make us more agile, here’s how” will get budget, improving overall IT responsiveness.

Most of us don’t get to choose the methodology (or lack thereof) in use for our team/group/department, but we do get to point out when the One True Methodology mentality is a weight and not helping. Do so. Strive, as most of us do, to do what is right for the organization, not what is the tool of today.

And embrace the bits that help no matter what. Focus on small problems, don’t over-document (but don’t under-document either, there will be others behind you that need to get up to speed), and unit/functional test at that one-business-problem level.

In the end, I titled this blog “Agile is not a development methodology”, simply because it is a mindset. A mindset that starts at the top, and prioritizes getting the business what they need in the fastest manner possible while still meeting requirements. You know, what we should have been (and many of us were) doing long before agile came along.

Read the original blog entry...

More Stories By Don MacVittie

Don MacVittie is founder of Ingrained Technology, A technical advocacy and software development consultancy. He has experience in application development, architecture, infrastructure, technical writing,DevOps, and IT management. MacVittie holds a B.S. in Computer Science from Northern Michigan University, and an M.S. in Computer Science from Nova Southeastern University.

@MicroservicesExpo Stories
Enterprise architects are increasingly adopting multi-cloud strategies as they seek to utilize existing data center assets, leverage the advantages of cloud computing and avoid cloud vendor lock-in. This requires a globally aware traffic management strategy that can monitor infrastructure health across data centers and end-user experience globally, while responding to control changes and system specification at the speed of today’s DevOps teams. In his session at 20th Cloud Expo, Josh Gray, Chie...
All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, discussed how to use Kubernetes to set up a SaaS infrastructure for your business. Mike Johnston is an infrastructure engineer at Supergiant.io with over 12 years of experience designing, deploying, and maintaining server and workstation infrastructure at all scales. He has experience with brick and mortar data centers as well as cloud providers like Digital Ocean, Amazon Web Services, and Rackspace. H...
Docker is sweeping across startups and enterprises alike, changing the way we build and ship applications. It's the most prominent and widely known software container platform, and it's particularly useful for eliminating common challenges when collaborating on code (like the "it works on my machine" phenomenon that most devs know all too well). With Docker, you can run and manage apps side-by-side - in isolated containers - resulting in better compute density. It's something that many developer...
We define Hybrid IT as a management approach in which organizations create a workload-centric and value-driven integrated technology stack that may include legacy infrastructure, web-scale architectures, private cloud implementations along with public cloud platforms ranging from Infrastructure-as-a-Service to Software-as-a-Service.
When you focus on a journey from up-close, you look at your own technical and cultural history and how you changed it for the benefit of the customer. This was our starting point: too many integration issues, 13 SWP days and very long cycles. It was evident that in this fast-paced industry we could no longer afford this reality. We needed something that would take us beyond reducing the development lifecycles, CI and Agile methodologies. We made a fundamental difference, even changed our culture...
As many know, the first generation of Cloud Management Platform (CMP) solutions were designed for managing virtual infrastructure (IaaS) and traditional applications. But that’s no longer enough to satisfy evolving and complex business requirements. In his session at 21st Cloud Expo, Scott Davis, Embotics CTO, will explore how next-generation CMPs ensure organizations can manage cloud-native and microservice-based application architectures, while also facilitating agile DevOps methodology. He wi...
These days, change is the only constant. In order to adapt and thrive in an ever-advancing and sometimes chaotic workforce, companies must leverage intelligent tools to streamline operations. While we're only at the dawn of machine intelligence, using a workflow manager will benefit your company in both the short and long term. Think: reduced errors, improved efficiency and more empowered employees-and that's just the start. Here are five other reasons workflow automation is leading a revolution...
As today's digital disruptions bounce and smash their way through conventional technologies and conventional wisdom alike, predicting their path is a multifaceted challenge. So many areas of technology advance on Moore's Law-like exponential curves that divining the future is fraught with danger. Such is the problem with artificial intelligence (AI), and its related concepts, including cognitive computing, machine learning, and deep learning.
We have Continuous Integration and we have Continuous Deployment, but what’s continuous across all of what we do is people. Even when tasks are automated, someone wrote the automation. So, Jayne Groll evangelizes about Continuous Everyone. Jayne is the CEO of the DevOps Institute and the author of Agile Service Management Guide. She talked about Continuous Everyone at the 2016 All Day DevOps conference. She describes it as "about people, culture, and collaboration mapped into your value streams....
In our first installment of this blog series, we went over the different types of applications migrated to the cloud and the benefits IT organizations hope to achieve by moving applications to the cloud. Unfortunately, IT can’t just press a button or even whip up a few lines of code to move applications to the cloud. Like any strategic move by IT, a cloud migration requires advanced planning.
Did you know that you can develop for mainframes in Java? Or that the testing and deployment can be automated across mobile to mainframe? In his session and demo at @DevOpsSummit at 21st Cloud Expo, Dana Boudreau, a Senior Director at CA Technologies, will discuss how increasingly teams are developing with agile methodologies, using modern development environments, and automating testing and deployments, mobile to mainframe.
“Why didn’t testing catch this” must become “How did this make it to testing?” Traditional quality teams are the crutch and excuse keeping organizations from making the necessary investment in people, process, and technology to accelerate test automation. Just like societies that did not build waterways because the labor to keep carrying the water was so cheap, we have created disincentives to automate. In her session at @DevOpsSummit at 20th Cloud Expo, Anne Hungate, President of Daring System...
As DevOps methodologies expand their reach across the enterprise, organizations face the daunting challenge of adapting related cloud strategies to ensure optimal alignment, from managing complexity to ensuring proper governance. How can culture, automation, legacy apps and even budget be reexamined to enable this ongoing shift within the modern software factory?
Most companies are adopting or evaluating container technology - Docker in particular - to speed up application deployment, drive down cost, ease management and make application delivery more flexible overall. As with most new architectures, this dream takes a lot of work to become a reality. Even when you do get your application componentized enough and packaged properly, there are still challenges for DevOps teams to making the shift to continuous delivery and achieving that reduction in cost ...
@DevOpsSummit at Cloud Expo taking place Oct 31 - Nov 2, 2017, at the Santa Clara Convention Center, Santa Clara, CA, is co-located with the 21st International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is ...
Docker is on a roll. In the last few years, this container management service has become immensely popular in development, especially given the great fit with agile-based projects and continuous delivery. In this article, I want to take a brief look at how you can use Docker to accelerate and streamline the software development lifecycle (SDLC) process.
Cloud adoption is often driven by a desire to increase efficiency, boost agility and save money. All too often, however, the reality involves unpredictable cost spikes and lack of oversight due to resource limitations. In his session at 20th Cloud Expo, Joe Kinsella, CTO and Founder of CloudHealth Technologies, tackled the question: “How do you build a fully optimized cloud?” He will examine: Why TCO is critical to achieving cloud success – and why attendees should be thinking holistically ab...
DevOps is good for organizations. According to the soon to be released State of DevOps Report high-performing IT organizations are 2X more likely to exceed profitability, market share, and productivity goals. But how do they do it? How do they use DevOps to drive value and differentiate their companies? We recently sat down with Nicole Forsgren, CEO and Chief Scientist at DORA (DevOps Research and Assessment) and lead investigator for the State of DevOps Report, to discuss the role of measure...
If you are part of the cloud development community, you certainly know about “serverless computing”, almost a misnomer. Because it implies there are no servers which is untrue. However the servers are hidden from the developers. This model eliminates operational complexity and increases developer productivity. We came from monolithic computing to client-server to services to microservices to serverless model. In other words, our systems have slowly “dissolved” from monolithic to function-by-func...