The hard part of successful DevOps isn’t implementing the technology; it's ensuring you have the right culture in your organization. You need to break down silos and align competing priorities and individual incentives to gain real benefits from DevOps. Move beyond thinking about technology alone and look at the people side of the equation. Here are seven ways to create a successful team that delivers the benefits of DevOps.
Ambiguity abounds about value streams, so it’s good to clarify what they are, why they matter, and how to exploit them. It's important to help employees understand the organization's definition of value, to provide visibility on how business value is created, and to focus on the fast flow of value through the value streams. If everyone understands which direction to row the boat, they can steer toward it together.
In order to adopt DevOps, organizations need to be able to embrace the openness it requires, encourage experimentation and innovation, and work across departmental silos. You may be ready to encourage collaboration and communication to reap the benefits, but what if your company culture isn't? Here's how you can influence your organizational dynamics to lay the groundwork for DevOps.
Implementing DevOps practices can significantly accelerate software releases while still assuring applications meet quality objectives. But DevOps can’t be bought, bolted on, or just declared. If you’re considering a move to a DevOps delivery model, here are six approaches for ensuring a successful DevOps adoption within an organization.
An organization shouldn’t spend all its time building its delivery muscle without simultaneously building its discovery muscle. In fact, successful software teams deliver great products because they invest in discovery. Learn how to expand your innovation and strengthen your discovery muscle.
Rather than rely on large handoffs between specialties, high-performing Scrum teams learn to do a little bit of everything all the time during a sprint. To do this effectively, teams must make three changes: shift from writing about requirements to talking about them, reduce the size of handoffs and make them more frequently, and pay more attention to the size of the product backlog items that they bring into their sprints.
Many new products being developed require the contribution of artists and other such "creatives," but artists often view the creative process as an organic thing that cannot be analyzed, dissected, or reduced to a set of defined practices without killing it. This article explores barriers such as these to the introduction of agile methods and how these barriers can be overcome.
Melissa Benua, director of engineering at mParticle, chats with TechWell community manager Owen Gotimer about the importance of whole team quality, how to get started using the test pyramid, and how developers can start writing testable code.
In this interview, visionary speaker Selena Delesie explains how successful teams embrace specific principles, including listening deeply, believing people truly matter, having an addiction to learning, serving others, flowing through change, moving through fear, and following joy.
In this interview, chief technology officer and cofounder of LeanDog, Jeff “Cheezy” Morgan, explains how continuous integration and agile are impacting not only technology groups, but the businesses that the people in the technology groups are helping to enable, support, and develop for.
In this interview, LogiGear's Hans Buwalda explains how better test design can lead to improved test automation and can make the difference between automation success and failure. He details why successful automated testing is a test design challenge, not a technical challenge.
The problem with many agile teams is that they simply never become a team. This often manifests itself as team members feeling unsafe or not quite trusting each other. This workshop will show you how the same techniques improv theater troupes use to improve collaboration, creativity, and communication can be used to help agile teams, too. The three-minute improv warm-up games Wayde Stallmann will lead you through in this session—including improv's famous "yes, and" technique—will help you learn to establish trust, improve collaboration, and learn how to provide a safe environment for your team to bond. You also will get a flier explaining the top twenty improv games, allowing you to leave with actionable material to use immediately upon returning to work so that you can help your team reach its full potential.
The key to creating high-performing teams is psychological safety—the ability to be vulnerable in front of others even when they hold diverse viewpoints, and the opportunity to take risks and trust that everything will be OK. However, creating this safety is easier said than done. Maaret Pyhäjärvi shares her story of working with software development and test teams to enable them to be awesome. She explains how to reinforce the positive while enabling great software product development by empowering others in your team. Maaret explores how to be brave when others are not, and how to care for and build safety for others. She describes being a catalyst for your team, emphasizing learning—always with safety as a prerequisite. Today, Maaret uses her position as a tester not only to test every part of the software but also to build the collaboration habits of the team, delivering actionable information to improve product quality.
Are you looking for new ways to invigorate your teams? Do retrospectives seem stale? Do story breakdown meetings feel flat? On the other hand, maybe your teams are humming and you’re looking for additional variety. The research is clear—movement matters, and play stimulates creativity.
Many organizations want to create systems delivered in a DevOps framework with diverse services implemented via API building blocks. Chris Haddad says that people, processes, and tools often hinder a team's ability to comply with security policies, streamline collaboration, and rapidly...