teams

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.

You've heard of a minimum viable product, which has only enough features to create a working model and provide feedback for further development. If you want to get started on a new project quickly, Allan Kelly suggests assembling a minimum viable team—only a few people, with only the necessary skills. They begin work right away, with a small budget and tight feedback loops, driving down risk.

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.

Experimentation is a great way to unleash creativity, continuously improve, and see what works and what doesn't. When a team was tossing around the idea of doing daily retrospectives, agile coach Ben Kopel decided to guide them through some iterations on the process. Here, he talks about what the team did and what they gained from both the retrospectives and the quick feedback from experimenting.