|By Tim Arthur||
|June 17, 2014 12:45 PM EDT||
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.
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.
As Enterprise business moves from Monoliths to Microservices, adoption and successful implementations of Microservices become more evident. The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Documenting hurdles and problems for the use of Microservices will help consultants, architects and specialists to avoid repeating the same mistakes and learn how and when to use (or not use) Microservices at the enterprise level. The circumstance w...
Feb. 27, 2017 06:45 PM EST Reads: 1,941
SYS-CON Events announced today that Catchpoint Systems, Inc., a provider of innovative web and infrastructure monitoring solutions, has been named “Silver Sponsor” of SYS-CON's DevOps Summit at 18th Cloud Expo New York, which will take place June 7-9, 2016, at the Javits Center in New York City, NY. Catchpoint is a leading Digital Performance Analytics company that provides unparalleled insight into customer-critical services to help consistently deliver an amazing customer experience. Designed ...
Feb. 27, 2017 05:45 PM EST Reads: 591
@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...
Feb. 27, 2017 12:45 PM EST Reads: 2,122
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...
Feb. 27, 2017 11:45 AM EST Reads: 2,547
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.
Feb. 27, 2017 11:30 AM EST Reads: 2,562
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 ...
Feb. 27, 2017 11:15 AM EST Reads: 2,866
DevOps and microservices are permeating software engineering teams broadly, whether these teams are in pure software shops but happen to run a business, such Uber and Airbnb, or in companies that rely heavily on software to run more traditional business, such as financial firms or high-end manufacturers. Microservices and DevOps have created software development and therefore business speed and agility benefits, but they have also created problems; specifically, they have created software securi...
Feb. 27, 2017 11:00 AM EST Reads: 4,276
The emerging Internet of Everything creates tremendous new opportunities for customer engagement and business model innovation. However, enterprises must overcome a number of critical challenges to bring these new solutions to market. In his session at @ThingsExpo, Michael Martin, CTO/CIO at nfrastructure, outlined these key challenges and recommended approaches for overcoming them to achieve speed and agility in the design, development and implementation of Internet of Everything solutions with...
Feb. 27, 2017 10:00 AM EST Reads: 8,043
DevOps is often described as a combination of technology and culture. Without both, DevOps isn't complete. However, applying the culture to outdated technology is a recipe for disaster; as response times grow and connections between teams are delayed by technology, the culture will die. A Nutanix Enterprise Cloud has many benefits that provide the needed base for a true DevOps paradigm. In his general session at 20th Cloud Expo, Chris Brown, a Solutions Marketing Manager at Nutanix, will explore...
Feb. 27, 2017 09:45 AM EST Reads: 1,908
This week's news brings us further reminders that if you're betting on cloud, you're headed in the right direction. The cloud is growing seven times faster than the rest of IT, according to IDC, with a 25% spending increase just from 2016 to 2017. SaaS still leads the pack, with an estimated two-thirds of public cloud spending going that way. Large enterprises, with more than 1,000 employees, are predicted to account for more than half of cloud spending and have the fastest annual growth rate.
Feb. 27, 2017 09:30 AM EST Reads: 1,254
All clouds are not equal. To succeed in a DevOps context, organizations should plan to develop/deploy apps across a choice of on-premise and public clouds simultaneously depending on the business needs. This is where the concept of the Lean Cloud comes in - resting on the idea that you often need to relocate your app modules over their life cycles for both innovation and operational efficiency in the cloud. In his session at @DevOpsSummit at19th Cloud Expo, Valentin (Val) Bercovici, CTO of Soli...
Feb. 27, 2017 09:15 AM EST Reads: 1,540
Microservices are a very exciting architectural approach that many organizations are looking to as a way to accelerate innovation. Microservices promise to allow teams to move away from monolithic "ball of mud" systems, but the reality is that, in the vast majority of organizations, different projects and technologies will continue to be developed at different speeds. How to handle the dependencies between these disparate systems with different iteration cycles? Consider the "canoncial problem" ...
Feb. 27, 2017 06:00 AM EST Reads: 6,207
After more than five years of DevOps, definitions are evolving, boundaries are expanding, ‘unicorns’ are no longer rare, enterprises are on board, and pundits are moving on. Can we now look at an evolution of DevOps? Should we? Is the foundation of DevOps ‘done’, or is there still too much left to do? What is mature, and what is still missing? What does the next 5 years of DevOps look like? In this Power Panel at DevOps Summit, moderated by DevOps Summit Conference Chair Andi Mann, panelists l...
Feb. 27, 2017 05:00 AM EST Reads: 7,468
When building DevOps or continuous delivery practices you can learn a great deal from others. What choices did they make, what practices did they put in place, and how did they connect the dots? At Sonatype, we pulled together a set of 21 reference architectures for folks building continuous delivery and DevOps practices using Docker. Why? After 3,000 DevOps professionals attended our webinar on "Continuous Integration using Docker" discussing just one reference architecture example, we recogn...
Feb. 27, 2017 04:00 AM EST Reads: 2,838
Hardware virtualization and cloud computing allowed us to increase resource utilization and increase our flexibility to respond to business demand. Docker Containers are the next quantum leap - Are they?! Databases always represented an additional set of challenges unique to running workloads requiring a maximum of I/O, network, CPU resources combined with data locality.
Feb. 27, 2017 03:00 AM EST Reads: 2,388
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...
Feb. 27, 2017 02:00 AM EST Reads: 1,896
In recent years, containers have taken the world by storm. Companies of all sizes and industries have realized the massive benefits of containers, such as unprecedented mobility, higher hardware utilization, and increased flexibility and agility; however, many containers today are non-persistent. Containers without persistence miss out on many benefits, and in many cases simply pass the responsibility of persistence onto other infrastructure, adding additional complexity.
Feb. 27, 2017 01:15 AM EST Reads: 1,771
Docker containers have brought great opportunities to shorten the deployment process through continuous integration and the delivery of applications and microservices. This applies equally to enterprise data centers as well as the cloud. In his session at 20th Cloud Expo, Jari Kolehmainen, founder and CTO of Kontena, will discuss solutions and benefits of a deeply integrated deployment pipeline using technologies such as container management platforms, Docker containers, and the drone.io Cl tool...
Feb. 26, 2017 10:45 PM EST Reads: 2,471
The rise of containers and microservices has skyrocketed the rate at which new applications are moved into production environments today. While developers have been deploying containers to speed up the development processes for some time, there still remain challenges with running microservices efficiently. Most existing IT monitoring tools don’t actually maintain visibility into the containers that make up microservices. As those container applications move into production, some IT operations t...
Feb. 26, 2017 10:15 PM EST Reads: 1,535
In 2014, Amazon announced a new form of compute called Lambda. We didn't know it at the time, but this represented a fundamental shift in what we expect from cloud computing. Now, all of the major cloud computing vendors want to take part in this disruptive technology. In his session at 20th Cloud Expo, John Jelinek IV, a web developer at Linux Academy, will discuss why major players like AWS, Microsoft Azure, IBM Bluemix, and Google Cloud Platform are all trying to sidestep VMs and containers...
Feb. 26, 2017 05:30 PM EST Reads: 2,380