Agile and Lean are continuously being experimented with. You can implement agile with ChatOps, use Lean in your UX, and more!
- During this course, you've learned Agile and Lean techniques that will help you through your DevOps journey. Agile and Lean have had a profound impact on DevOps culture, but there are plenty of other avenues where they've made an impact as well. Let's take a look. - The first topic to consider is ChatOps. ChatOps is a rapidly growing approach to communication that helps teams collaborate and manage aspects of their infrastructure code and organizational functions from the comfort of a chat client. - From a high level team members type commands that a chat bot is configured to execute through custom scripts and plugins.
These commands can range from code deployments, security event responses, or system and team member notifications. The entire team now has the opportunity to collaborate in real time as the commands are executed. - [Ernest] Common examples of chat bots the team use today are Hubot, Lita, and Err. A great resource to read more about ChatOps is "Managing Operations in Group Chat," by Jason Hand. - There's plenty of DevOps activities you can automate to make your teams more agile with ChatOps.
You can start simple by integrating your commits, test results, and merge requests into a chat room in your existing chat infrastructure. Then you can grow this out to run smoke tests on demand, get status information on your servers, you know, maybe from your monitoring tools, fresh log data, or even run deployments right from your chat system. - This helps implement both the close communication that Agile depends on and as a great example of human friendly automation from the Lean principle of jidoka. - Another area that's recently begun to update Lean is Lean user experience, also known as Lean UX.
- Lean UX focuses more on the experience under design, rather than the necessary deliverables as in traditional UX design. Like other Lean and Agile principles, it requires greater levels of collaboration with the entire team. - Major objective in Lean UX, is to focus on obtaining user feedback as early as possible, so that better decisions can be made. The nature of Agile development is to work in rapid iterative cycles and Lean UX uses these cycles to ensure that the data generated, can be used in each iteration.
- [Ernest] Much like Agile development, Lean UX also has a manifesto that prioritizes the following items. - [Peco] Early customer validation over releasing products that have an unknown user value. - [Ernest] Collaborative design over designing on an island. - [Peco] Solving real user problems over designing for the next cool feature. - [Ernest] Measuring KPIs over undefined success metrics. - [Peco] Applying appropriate tools over following some arbitrary rigid plan.
- [Ernest] And finally, nimble design over heavy wireframes, comps, or specs. - [Peco] By prioritizing prototyping, user feedback, and validation, Lean UX shifts the emphasis to creating value for end users. It stresses on creating a hypothesis followed by a rough prototype and validating internally and then test externally with a few customers. - [Ernest] Once the test cycle's complete, it's important to take that learning, refine the hypothesis, and iterate on the cycle again. - Lean UX stops individual designers from spending a long time on a specific design without any feedback.
You know, much like how product managers weren't able to get any insight into development during a waterfall process. It makes the whole team more agile, efficient, and solving problems that end users are facing. - [Ernest] Seeing the benefits of shifting towards a customer centric approach with Lean UX, there's been a dramatic shift towards using similar principles in other areas of the organization as well. - And one final advanced topic, be Lean and Agile about your DevOps implementation. Especially around your tool chain and process.
- That's right. I have a friend who did a lot of DevOps consulting, and he did a lot of ripping out of overly complicated DevOps tool sets. Crazy chef or puppet implementations, overly complex build systems and so on. They went in with good intentions, but by not keeping the Lean and Agile principles in mind, they ended up in overly complex software gridlock. - No one likes gridlock. - Yeah, this isn't Washington DC. - Sick burn. It's easy to get carried away with all the tools and things you can do.
Even your Agile or Lean workflow in your ticketing system can be made cumbersome with too many workflow steps, too many calls on your CamBam board, et cetera. - Remember, even adding good things you don't need is waste. Slowing down the team because you're integrating 10 different technologies together in your build pipeline because it's cool, is waste. Adding a dozen workflow steps to your JIRA ticket flow when four is all you need, is waste. - We won't cover it in this course, but the principles of Lean, have been applied to Lean Enterprise, Lean customer development, and analytics as well.
- While there are specific methodologies to follow in each of these areas, it's important to remember that the Lean values and principles still remain the same. - Stay tuned to our next video, where we'll arm you with some next steps on your Lean, Agile, and DevOps journey.
- What is agile?
- What is lean?
- Measuring success
- Learning and adapting
- Building a culture of metrics
- Continuous learning
- Advanced concepts