Welcome!

Microservices Expo Authors: Elizabeth White, Pat Romanski, Liz McMillan, Carmen Gonzalez, JP Morgenthal

Related Topics: Microservices Expo, Java IoT, Microsoft Cloud, Linux Containers, Containers Expo Blog, Agile Computing

Microservices Expo: Article

Fanning the Flames of Agile

The brilliance of agile is that it is easy to understand

Knowledge creation is a major source of value creation. And great companies -and their employees - know that continuous learning is a key to generating knowledge, and thus value. The agile mindset, particularly in development, is gaining popularity, with credit to a suite of powerful ideas and practices commonly known as the agile methodology - defined by Wikipedia as "software development methods based on iterative and incremental development."

Agile on Paper
In February 2001, a group of 17 software developers wrote the Agile Manifesto, the Magna Carta of the agile movement. At just 68 words, it was elegant, but at that point just words on paper. Early attempts to apply it came by adapting existing techniques such as lean manufacturing (adapted from Toyota's methodologies), Crystal, Scrum and XP (Extreme Programming). Admittedly, we were still learning. Buying into "agile" signaled your ideals were more lofty than grounded. Agile supporters were revolutionary, but agile was not.

Later that year, Ken Schwaber and Mike Beedle, two of the manifesto's signatories, published the watershed Agile Software Development With SCRUM. The authors noted how the Agile Manifesto could map to tangible business practices and showcased how they actually applied it. They described agile in a real-world setting, and the world hasn't been the same since. They moved SCRUM from abstract rugby imagery to concrete possibility.

We learned that agile is an approach for value generation - an approach for moving ideas from an early ideal to sustainable, real-world changes.

Most of all, we learned that agile concepts are valid.

Agile in Practice
Concepts are one thing, but successful application is quite another.

Let's look at the company where I work. SAS is the world's largest privately held software company, and we have been proponents of the agile mindset since the company's inception in 1976. SAS invests 25 percent of revenues back into R&D and regards itself as a learning company. We learn by listening; we learn by doing.

SAS first evaluated agile Scrum in 2007. Teams heard of early wins and wanted to apply agile in their own areas. Since then, SAS has formally trained thousands of personnel and invested in an infrastructure for its R&D portfolio. At SAS, agile is applied across the enterprise. It's used to manage small projects and very large projects encompassing hundreds of staff members. It's also used to bring a common approach to how SAS manages its products.

Agile is empirical - that is, we apply, learn and adapt. It is true for applying any one specific agile practice, and it is true for applying agile at scale over years. This leads to some questions: What did we learn? How did we adapt? Moreover, what cultural norms did we lean on to help garner such a strong embrace of agile and its benefits? Knowing the answers to these questions could help accelerate your own success story.

We Learned One Size Does Not Fit All
Agile books and blogs make it all sound so clean: Do A, then B, then C. Further, with so much positive press on agile development, it is tempting for any firm's executive or business controls team to mandate a one-size-fits-all approach.

Instead of mandating the same approach for everyone, we fostered a grass-roots movement. Concurrently, we used a senior executive as an advocate and recruited an operational agile champion to drive the rollout. It is important for the executive team to understand and expect agile from its teams, but not from a single template.

We adapted by creating the flexible SAS Agile Framework. It includes three integral parts: setup (training and coaching), defined practices, and an agile team self-assessment survey. The framework is helping us meet demands and energize teams with the freedom to envision and realize exciting opportunities.

Agile is applied differently in R&D, Pubs, IT, Professional Services, and other divisions in SAS. Practices are configured in the best way for the teams and markets they serve.

We Learned to Nurture the Movement
Bottom line: We watched and we listened. We nurtured our cultural norm of not accepting the status quo, and to keep a skeptical eye. More specifically, we worked hard to make sure teams weren't buying in just because of the buzz. It was important that they understood the business drivers of agile, planned time for training and startup, and applied the right agile practices in the right way for their project.

Just as with every team member, every team is different. When a team member became critical of certain agile practices for a team, we listened closely.

A Journey, Not a Destination
View agile as a journey: It takes a moment to learn, but a lifetime to master. Teams typically invest in group training, and then a small pilot. Agile is not unlike other practices where at first it's awkward, challenging and even slightly less productive. However, as a team becomes more comfortable, you'll typically hear people say they would never go back. We're all motivated by accomplishments, and agile creates the thriving state of productivity and morale we need to achieve them.

We Adapted Our Software Development Life Cycle (SDLC)
SAS is like other software development firms where the existence of an overarching software development life cycle is important. At SAS, agile holds ours together. It serves as the glue between all groups and ensures that products flow along an orderly and controlled path. Five years into agile at scale, we re-evaluated the process, then made it less linear and extended it to overlap even more than it already did. We halved the lifecycle size. We reduced the number of management checkpoints and cut back the number of required artifacts. Yet because of how agile overlays the entire process, it resulted in a better way for R&D.

We Adapted by Investing in Agile Coaches
Coaching can make a big difference, and not only in sports.

A common question asked with enterprises new to agile is: Who should play the role of the Scrum master? At SAS, this role fell to our project managers. We were fortunate. Publicly held firms find this challenging because of the required mechanisms and extra control systems their project managers must handle. Although SAS is a $3 billion dollar company, we're private and can operate unencumbered.

In our journey we noticed that teams fared better when they engaged with experienced agile veterans - they got up to speed faster. We looked closer and found by internal survey data that coaching has a positive correlation on all of intended benefits of Scrum. We now have a large team of trained coaches engaged with their own teams and others as well.

We Adapted by Tirelessly Encouraging Transparency
We also applied the agile philosophy of transparency about larger project risks and mitigations to being frank and open with individual team members. This helped create healthy, self-directed work teams.

For example, our teams openly discuss the agile self-assessment surveys. Teams independently record and then jointly discuss summary and detailed data scores and write-in comments. The discussion is useful for identifying two to three action items, but even more useful for helping teams build trust and maturity.

A word of caution, however: Be careful when looking at agile metadata between teams. Teams perform at different rates, have different compositions, and come to know requirements estimates (story points) differently. Asking a team why its numbers are different from another's can threaten its freedom and inadvertently move them to game. Can we benefit from enterprisewide analysis? Yes, if we thoroughly describe to teams the intention of such an analysis and why it's being done. It helps drive corporate training and updates upper management on progress, for instance.

We Adapted by Bringing a New Meaning to the Term ‘Flexible'
At SAS, we were able to establish a different type of relationship with our product owners, development and test teams, and support teams. We moved from setting long-range targets with multiple commitments and promises to shorter-range iterative targets. Demos now occur routinely, and that in turn builds confidence with all project stakeholders.

Benefits, Compounded
Practices yield benefits. Better practices yield better benefits.

In the internal survey mentioned earlier, we noticed something profound. Teams that tended to adopt agile practices with a higher degree of maturity tended to have better results overall. Intuitively, one might suspect this to be true - and the data objectively proved it. That evidence makes it even easier for staff members at all levels to commit.

SAS is an agile company. Our customers and workforce are increasingly receptive to the large-scale implementation of agile Scrum. It's now a part of our daily fiber and undoubtedly will continue to be part of our ongoing success.

The brilliance of agile is that it is easy to understand. The danger of agile is that it is easy to understand, and can be underestimated. Be mindful of what it takes to employ it well to yield the most benefit. Engage. Find a cohort, a validation pilot, a way to connect. Most of all, enjoy the journey.

More Stories By Tim Arthur

Tim Arthur, MSMOT, PMP, CSM, draws from the experience of very small to very large private and public projects managed under various models. He’s been with SAS for 15 years. Prior to that he led mission-critical 24/7 global software systems with IBM for 17 years. As the SAS Agile Champion he’s helped train and coach over 3,000 people on teams of all sizes, worldwide.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
For organizations that have amassed large sums of software complexity, taking a microservices approach is the first step toward DevOps and continuous improvement / development. Integrating system-level analysis with microservices makes it easier to change and add functionality to applications at any time without the increase of risk. Before you start big transformation projects or a cloud migration, make sure these changes won’t take down your entire organization.
Updating DevOps to the latest production data slows down your development cycle. Probably it is due to slow, inefficient conventional storage and associated copy data management practices. In his session at @DevOpsSummit at 20th Cloud Expo, Dhiraj Sehgal, in Product and Solution at Tintri, will talk about DevOps and cloud-focused storage to update hundreds of child VMs (different flavors) with updates from a master VM in minutes, saving hours or even days in each development cycle. He will also...
Thanks to Docker, it becomes very easy to leverage containers to build, ship, and run any Linux application on any kind of infrastructure. Docker is particularly helpful for microservice architectures because their successful implementation relies on a fast, efficient deployment mechanism – which is precisely one of the features of Docker. Microservice architectures are therefore becoming more popular, and are increasingly seen as an interesting option even for smaller projects, instead of being...
In his session at 20th Cloud Expo, Mike Johnston, an infrastructure engineer at Supergiant.io, will discuss how to use Kubernetes to setup 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....
SYS-CON Events announced today that CA Technologies has been named “Platinum Sponsor” of SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY, and the 21st International Cloud Expo®, which will take place October 31-November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. CA Technologies helps customers succeed in a future where every business – from apparel to energy – is being rewritten by software. From ...
SYS-CON Events announced today that Fusion, a leading provider of cloud services, will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. Fusion, a leading provider of integrated cloud solutions to small, medium and large businesses, is the industry’s single source for the cloud. Fusion’s advanced, proprietary cloud service platform enables the integration of leading edge solutions in the cloud, including cloud...
SYS-CON Events announced today that Outlyer, a monitoring service for DevOps and operations teams, has been named “Bronze Sponsor” of SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. Outlyer is a monitoring service for DevOps and Operations teams running Cloud, SaaS, Microservices and IoT deployments. Designed for today's dynamic environments that need beyond cloud-scale monitoring, we make monitoring effortless so you...
Cloud Expo, Inc. has announced today that Andi Mann and Aruna Ravichandran have been named Co-Chairs of @DevOpsSummit at Cloud Expo 2017. The @DevOpsSummit at Cloud Expo New York will take place on June 6-8, 2017, at the Javits Center in New York City, New York, and @DevOpsSummit at Cloud Expo Silicon Valley will take place Oct. 31-Nov. 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
With 10 simultaneous tracks, keynotes, general sessions and targeted breakout classes, Cloud Expo and @ThingsExpo are two of the most important technology events of the year. Since its launch over eight years ago, Cloud Expo and @ThingsExpo have presented a rock star faculty as well as showcased hundreds of sponsors and exhibitors! In this blog post, I provide 7 tips on how, as part of our world-class faculty, you can deliver one of the most popular sessions at our events. But before reading the...
TechTarget storage websites are the best online information resource for news, tips and expert advice for the storage, backup and disaster recovery markets. By creating abundant, high-quality editorial content across more than 140 highly targeted technology-specific websites, TechTarget attracts and nurtures communities of technology buyers researching their companies' information technology needs. By understanding these buyers' content consumption behaviors, TechTarget creates the purchase inte...
With major technology companies and startups seriously embracing Cloud strategies, now is the perfect time to attend @CloudExpo | @ThingsExpo, June 6-8, 2017, at the Javits Center in New York City, NY and October 31 - November 2, 2017, Santa Clara Convention Center, CA. Learn what is going on, contribute to the discussions, and ensure that your enterprise is on the right path to Digital Transformation.
@DevOpsSummit at Cloud taking place June 6-8, 2017, at Javits Center, New York City, is co-located with the 20th 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 no time to wait for long developm...
Microservices (μServices) are a fascinating evolution of the Distributed Object Computing (DOC) paradigm. Initial design of DOC attempted to solve the problem of simplifying developing complex distributed applications by applying object-oriented design principles to disparate components operating across networked infrastructure. In this model, DOC “hid” the complexity of making this work from the developer regardless of the deployment architecture through the use of complex frameworks, such as C...
In today's enterprise, digital transformation represents organizational change even more so than technology change, as customer preferences and behavior drive end-to-end transformation across lines of business as well as IT. To capitalize on the ubiquitous disruption driving this transformation, companies must be able to innovate at an increasingly rapid pace. Traditional approaches for driving innovation are now woefully inadequate for keeping up with the breadth of disruption and change facing...
When building large, cloud-based applications that operate at a high scale, it’s important to maintain a high availability and resilience to failures. In order to do that, you must be tolerant of failures, even in light of failures in other areas of your application. “Fly two mistakes high” is an old adage in the radio control airplane hobby. It means, fly high enough so that if you make a mistake, you can continue flying with room to still make mistakes. In his session at 18th Cloud Expo, Lee A...
As we enter the final week before the 19th International Cloud Expo | @ThingsExpo in Santa Clara, CA, it's time for me to reflect on six big topics that will be important during the show. Hybrid Cloud: This general-purpose term seems to provide a comfort zone for many enterprise IT managers. It sounds reassuring to be able to work with one of the major public-cloud providers like AWS or Microsoft Azure while still maintaining an on-site presence.
As software becomes more and more complex, we, as software developers, have been splitting up our code into smaller and smaller components. This is also true for the environment in which we run our code: going from bare metal, to VMs to the modern-day Cloud Native world of containers, schedulers and micro services. While we have figured out how to run containerized applications in the cloud using schedulers, we've yet to come up with a good solution to bridge the gap between getting your contain...
Thanks to Docker and the DevOps revolution, microservices have emerged as the new way to build and deploy applications — and there are plenty of great reasons to embrace the microservices trend. If you are going to adopt microservices, you also have to understand that microservice architectures have many moving parts. When it comes to incident management, this presents an important difference between microservices and monolithic architectures. More moving parts mean more complexity to monitor an...
"Plutora provides release and testing environment capabilities to the enterprise," explained Dalibor Siroky, Director and Co-founder of Plutora, in this SYS-CON.tv interview at @DevOpsSummit, held June 9-11, 2015, at the Javits Center in New York City.
You often hear the two titles of "DevOps" and "Immutable Infrastructure" used independently. In his session at DevOps Summit, John Willis, Technical Evangelist for Docker, covered the union between the two topics and why this is important. He provided an overview of Immutable Infrastructure then showed how an Immutable Continuous Delivery pipeline can be applied as a best practice for "DevOps." He ended the session with some interesting case study examples.