Showing posts with label opinion. Show all posts
Showing posts with label opinion. Show all posts

Sunday, 28 February 2016

The Culture Change of DevOps and Your Career

DevOps has been viewed primarily as adopting tools. Actually the major shift in DevOps is a cultural shift that is supported by processes and tools. Many voices in the technology community are now focused on the cultural change of DevOps. What are the implications for companies and those in development and operations focused roles?
Christian Posta makes clear the shift associated with DevOps in his article – DevOps and the Myth of Efficiency.
“DevOps, Microservices, Cloud, etc are all about making organizations more effective. It’s laying the groundwork to treat our organizations as complex systems, not machines. This approach lends itself to really understanding the value of feedback, failure, learning, autonomy, and emergent behavior which are critical for any complex system to exhibit to evolve and stay relevant in a complex, not merely complicated, world.”
A recent SD Times article interviews two evangelists for Red Hat: Markus Eisele, a developer advocate based in Germany, near Munich, and Burr Sutter, product management director for developer products based in Raleigh, NC, to get their perspectives on how enterprise DevOps can best gain traction. Posta and Burr had this to say on the culture change required for DevOps:
“Sutter: The No. 1 mistake I see IT organizations, shops and developers make is often they’re looking for a tool to come in and solve their problems. There are tools that help, but in general it’s about cultural change, workflow and process change.
Eisele: Enterprises in general don’t actually see what it means to do DevOps. To them it’s a solvable problem by tool. We have seen independent software development teams and internal IT organizations working together in waterfall-driven processes for years. When people jumped into agile, they said, “Let’s see if we can get the stakeholders closer to each other,” but that never included operations. The whole problem goes all the way up the organizational chain. Getting those cross-business-unit methodologies to work together is not solvable by a tool. And when vendors say, “We are going to sell you containers and microservices so you can achieve Continuous Delivery,” the part they don’t mention is the cultural change.”
A Tech Beacon article discusses the opinions of Gene Kim on the topic. Kim is a co-author of the best-selling book The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win, the former CTO of Tripwire and one of the organizers of the annual DevOps Enterprise Summit. In the article Kim states:
“The original idea was simply to de-silo dev and ops to overcome the bottlenecks in the software development and deployment process, mostly on the ops side. Today, with the evolution of DevOps, the goal is supporting a continuous delivery pipeline. Operations has been adopting so many of the techniques used by developers to support more agile and responsive processes that we’re seeing a kind of “dev-ification of ops.”
The “dev-ification” of ops and “ops-ification” of dev as Kim talks about later in the article leads to considerations for those working in development and operations roles today. In order to be well positioned for this culture change it stands to reason that some additional skills will be needed.
In a recent ebook UpGuard – a Mountainview California based DevOps and CyberSecurity company – gives ideas of how developers, operations and others can prepare their careers for DevOps. The eBook titled “The DevOps Career Guide” quotes research from Jobsignal.io, that indicates that DevOps salaries average more than $10,000 per year more than traditional developer roles. In the San Francisco Bay Area early stage startups pay upward of $150,000.

The UpGuard ebook goes on to state:
“Culture first, tools second. This is the order of precedent that most DevOps practitioners encourage, albeit– the tools help to shape the culture. Because Agile and lean are close cousins to DevOps, many of the highly valued personality traits integral to them are also highly valued to DevOps shops. Communication skills and empathy are perhaps the two most important skills– this allows team members to be responsive to the needs of the product offering, the customer, other stakeholders– and perhaps most importantly, other team members. The best tooling in the world will not go far without the proper cross-team communication skills and collaboration strategies.”
“A typical DevOps-enabled organization might expect proficiency with CM tools like Chef, Puppet, or Ansible– as well as other automation and orchestration platforms like Jenkins and Travis CI. As DevOps is spiritually a grassroots movement, command of popular open source tools is a highly prized skill set in the DevOps arena. Containerization technologies such as Docker and CoreOS’ Rocket are also essential tools in the DevOps toolchain.”
On potential interview questions the UpGuard ebook recommends:
“Be prepared to discuss topics around scope maintenance, workflow streamlining, setting objectives amongst team members, and resolving conflicts, among others. Again– at the end of the day, technical skills are only part of the equation when it comes to DevOps. A skilled DevOps practitioner is able to use technical skills and tools to augment and promoter tighter teamwork and positive behavior for building optimal products and services.”
Of course just as DevOps is first a culture change, there is also a very relevant aspect based on tools. Today we looked at some of the voices emphasizing the importance of the culture change in DevOps. We also looked at some relevant career considerations for individuals desiring to position themselves well for DevOps. Next time in the DevOps series we will take a look at the DevOps toolchain and some of the most relevant current technologies.

Saturday, 16 January 2016

Scaled Agile Framework 4.0 - A Practitioner's Perspective

This week we take a look at the new version of SAFe 4.0. I will give a practitioner's perspective on the changes and updates, covering interesting and noteworthy areas. SAFe 4.0 represents a significant update and is beneficial to learn about if you are or plan on scaling Agile.


Friday, 30 January 2015

An Optimistic View of Agile Adoption in Asia

To address the potential for Agile adoption in Asia I will look through the lens of multiple Agile methods. The methods considered will include Scrum, Kanban, XP, SAFe, and other Agile Scaling approaches. Asia is a very diverse region, and has to be looked at from many angles to get a picture of the potential for Agile adoption. With this in mind let’s take a look at Agile adoption in Asia.

Asia is not monolithic
It is important to remember that Asia is not monolithic or homogeneous. China is different from ASEAN, India, Japan, and Korea. Countries in ASEAN differ, Singapore is not the same culturally as Thailand or Indonesia. To look at Asia as one monolithic place is not an accurate or informed view.
If we take some examples: Singapore is actively moving towards Agile methods and new technology in its “Smart Nation Initiative”. Thailand has a very active Agile community and many companies have already adopted the use of Agile methods.
China has massive companies and IT departments in the thousands of people. While this can be a challenge for launching a Scrum team, Agile Scaling methods like SAFe have the potential to do very well in the China market. I liken the “leapfrog” potential in the China market to what occurred in Africa in the adoption of cellular technologies and “leapfrogging” over land lines.
Malaysia and Indonesia have been slower in movement towards Agile methods. Korea and Japan have very strong and unique cultures that make it difficult for outsiders to introduce new methods, but the potential for Agile still exists in these markets as well. Japan is the home and originating point of Lean (the Toyota Production System) after all, which is a key foundation for Agile methods.
In South Asia India has been working with Agile methods for years and outsourcing for US and European companies. Many Indian companies establish dedicated teams for Agile methods and adopt Agile methods quite successfully. Sri Lanka is also coming onto the world scene since its internal environment has stabilized and there too some early Agile adoption is taking place. I encountered several companies from Sri Lanka that were very familiar with and / or using Agile methods at the 2014 Gartner Gold Coast IT Symposium in Australia.

Education system in Asia
A criticism of the education system in Asia is that it focuses too much on grades and rank. The argument is that this means there is a lack of creativity which is needed for business agility, Design Thinking, and creative solutions.
My wife a teacher by training in the US came to Singapore on a Fulbright Fellowship to study the education System. One of her findings was that even though in past generations the education system was very focused on grades and rank, that there is more of a move now towards creative thinking and creative problem solving in the schools.
In fact innovation in Asia overall is on the increase. In 2014, China actually accounted for some 32.1% of worldwide patent filings. This can be taken as an indication of innovation and creativity, which is required to create new patents. Shenzhen in southern China is a good example of a Chinese modern hub of innovation.
The overall trend in Asia is toward greater creativity and innovation. This also follows from ancient culture and history in Asia. In China much innovation originated including: gun powder, the compass, paper, and golf among many.

Outsourcing – Reducing Costs
There have been some interesting points made on this topic in an article I recently read. It is interesting to note that in the US outsourcing and cost reduction are a constant focus in companies and IT (which is often viewed as a cost center). In particular a point was made around a low cost Scrum / Agile adoption mentality in Asia. Another point was made around “Agile Project Management” methods being taught as a low cost low effort way to try and adopt Agile.
I think it is valuable to address these points. From experience in the US market I know that it is true that low cost, low effort transitions to Agile are often attempted by simply training Project Managers and developers on Scrum, and changing little else in the organization.   However, I want to point out that Scrum actually includes a project management framework (managing risks, updating on progress, etc…). This is important because it points to the alignment of managing projects and using Agile methods, these two are not contradictory but rather an evolution of methods.
When done properly it is quite possible to help those who have been traditional project managers to work in the context of an Agile organization, and in fact in many cases this is very necessary. For example in the SAFe framework for scaling Agile the role of the Release Train Engineer (RTE – Uber ScrumMaster) can often be effectively played by someone with traditional project management experience (skills like seeing dependencies, and coordinating large groups). The approach to leading becomes a servant leadership approach.   But, the skills obtained in a project management context are still valuable.

Culture
I have seen many comments that suggest that culture in Asia is not compatible with Scrum and Agile. A focus on what is best for the community over the individual is a feature of Chinese culture. This focus on community lends itself to the team aspects of Agile. As I have mentioned in prior blog posts on my Blog AuspiciousAgile.com the community aspects and focus common to many Asian cultures lend themselves very well to the team focus and empowered teams of Agile and Scrum.

Hierarchy
A common observation is that the hierarchy that exists in much of Asian culture is a challenge to Agile adoption. I think this is a valid point. However, I think this is a challenge but not an insurmountable one.
Let’s take the US where Agile adoption is high and steadily increasing as an example. In the US individualism does not align with the team focus of Agile. Many developers and others are focused on what is best for them before they are concerned about what is good for the team. But Agile is still workable in the US. Organizations are able to overcome this challenge in the US and successfully adopt Agile.   Similarly Asia’s social hierarchy does not lend itself to Agile’s servant leadership model, but it is not insurmountable.
In a “Leading SAFe” class that I was teaching recently one participant commented that they have experienced many very successful Agile adoptions in Asia. The comment was that success really depended more on the individual organization than it did on only the broader cultural factors. While I don’t want to downplay broader cultural forces, I think that organizational culture and values can still provide for successful Agile adoption in most countries in Asia.

In Summary 
While there are challenges to adoption of Agile in Asia, I do not see any of them as insurmountable.   Similarly in the US there were cultural aspects (individualism) that are not necessarily aligned with Agile adoption. However, in spite of these cultural challenges Agile adoption has still moved forward in the US. I see no reason that the cultural challenges to the adoption of Agile methods in Asia can not also be overcome.