Roadmap review and retrospective 2019: DevOps Enterprise

2019: DevOps Enterprise

Organization

  • Team organization, communication and collaboration
  • Community build and growth
  • Scale knowledge
  • DevOps maturity

Work Management

  • Workflow visibility

DevOpsDays Portugal

  • Organize the DevOpsDays first edition in Portugal

Reading

  • Read at least 6 books

The 2019 year was dedicated to DevOps Enterprise. I was really keen to know if challenges described in books like The Phoenix Project were true. Guess what!? They are.

Organization

  • Team organization, communication and collaboration
    • A team is probably the most dynamic element in an enterprise. They have different sizes, configurations, purposes and interactions.
    • That’s why team communication and collaboration in enterprise is such big topic. The biggest challenges are located in the team boundaries, aka interactions. This boundaries tend be unclear due to organization dynamic of change at teams level. This also explains why is hard to find information, because information moves with people, so in order to get information you have to find the right people.
  • Community build and growth
    • People with that face the same problems or challenges tend to group. In a enterprise context we just need to manage this natural human behavior by promoting and giving a structure so more groups / communities may appear.
  • Scale knowledge
    • One of the ways to address this challenge is to build communities.
    • The goal is take the knowledge of one individual and share it with the team. Take the team knowledge and bring it to the community level and department level. From the department level to the business unit level. And finally from business unit level to the organization level.
  • DevOps maturity
    • Maturity in this context should be understood as baseline definition. Teams were taught to define their baseline and their DevOps roadmap.
    • Additionally, teams were taught to define the governance process in order to manage team progress towards the goals defined in the roadmap.

Work Management

  • Workflow visibility
    • The goal was to focus the team (and the organization) on managing work instead of managing people.
    • So, in order to manage work the team needs to make work visible. For this the team needs to know the nature of their work demand. In other words, what kind of work the team do: business requests, team improvements, unplanned work, maintenance…
    • By making the work visible, the team is able to improve the flow.
    • Because the human brain works better with visuals we should use visual systems like Scrum / Kanban boards to make the work and flow visible.
    • A useful tip: the work units (epics, user stories, tasks, sub-tasks, …) should be clear to the team. In other words, the way how the team structure the work should be understood by all team members.
    • You can find more inspirational information in the book Making Work Visible: Exposing Time Theft to Optimize Work & flow.

DevOpsDays Portugal

  • Organize the DevOpsDays first edition in Portugal

Reading

  • Read at least 6 books
    • I really need to improve my reading performance because I only have read 2 books.

Leave a reply:

Your email address will not be published.

Site Footer