The first core value is to Improve beyond the limits of today’s processes. Whether a product or project, it makes sense that we have a goal in how we work that includes a measurable and definable plan to improve our way of working. While it takes some thoughtful consideration and planning to improve how we work, in Disciplined Agile we call this process goal Evolving our Way of Working or Evolving our WoW (for short) (Ambler, Lines, 2019).
Let us examine a bit more on the “why” before we discuss the “what”. The community of practice is a great forum to share learnings across the company. Sharing our learning is a great DevOps mindset goal and core value because:
- Every team is different, approaching how they work and what they solve differently. If the world was run by Automaton or robots, we all might work the same. However, as this is not the case and people are unique, how we configure things, where we work from and other variables add to the complexities of life, some of which are self-inflicted. Being unique gives our world colour and character. It is because of this that we need to tailor how we work to the team and since we never get this right the first time; we must continuously evolve how we work.
- We are always learning. As soon as our brains form, we are “wired” to learn. Life and work challenges may require new skills and approaches, so we need to be open to learning in order to solve these challenges.
- We must adapt and evolve. DevOps and Agile require teamwork, so why not join your team’s evolution or revolution.
- Everything around us is evolving; our environment,
- People need a place to work, whether virtually or physically, that accommodates and evolves with us.
- People need (and like) tools and tooling are necessary when making teams effective, including digital and physical toolsets.
- How we work and evolve is beyond the team and DevOps, so improve your processes beyond today and the team, really building on the DevOps mindset.
The goal, Evolving Your Wow, is a lengthy group of decisions and options, which can be found in the Choose your WoW book (Ambler, Lines, 2019). Choosing & evolving our WoW over time might look something like the process in Figure 45 in the book, and shown below:
How we get there depends on our ability to guide our individuals, teams and divisions. Without good guidance such as an Agile Coach with DevOps experience may impede or worse yet negatively impact the value, speed and acceptance of our approach. The subject of Guided Continuous Improvement is throughout our book and another specific topic I shall bring out in another blog.
Agent 77 at Tactec uses the following Decisions based on working with DevOps teams throughout any agile lifecycle they choose.
Decision | Some of the options |
---|---|
Organize Physical Environment | . Openwork area . Dedicated workroom . Agile Modelling Room |
Choose Communication Styles | . Face to Face . Video Conferencing |
Choose Collaboration Styles | · Regular Pairing · Meetings/working sessions |
Select Lifecycle | · Lean · Agile · Continuous Lean . Continuous Agile · SAFe · Exploratory · Scrum . Flex |
Visualize Existing Process | · Kanban board · Value Stream Map · Business Process Model |
Tailor Initial Process | · Process tailoring workshop · Adopt DAD / AoC suggestions |
Identify Potential Improvements | · Measure existing Wow · Retrospectives · Value Stream Mapping |
Reuse Known Strategies | · Ideas from the AoC, DA toolkit · Local core practices · “Good practices” |
Implement Potential Improvements | · Guided Continuous Improvement (coaching) · Controlled experiments · Measured improvement |
Capture your WoW | · Detailed Team Process · VSM · Working agreement (internal/external) |
Share your Improvements | · Open Spaces · Hackathons · Lean Coffee Sessions · CoP · Blogs . Guilds . Meetups / Webinars |
Organize Tool Environment | · Acceptance test/criteria · Code Analysis · Configuration Management · Continuous Deployment (deployment rings) · Continuous Integration · Dashboards · Wiki · Digital backlog · Task management |