An especially interesting dimension to GitOps is that you can extend the model to include ‘people management’ related activities, the collaboration, scheduling and project management surrounding the core operations automation.
In their blog The GitOps Pipeline, Weaveworks start to touch on this:
User friendly social features like user names, auth, permissions, teams, private and public repos and pull request collaboration. This makes Git more intelligible to humans and enables teamwork.
Three vendors are referenced to explain further: Zenhub, Aha.io and SonarCloud.
Each work “within” Github and augment its functionality with new features – For example SonarCloud decorates your pull requests, giving you the feedback you need, right in your GitHub repositories.
ZenHub is natively integrated into GitHub, using Issues and GitHub’s underlying data to keep project progress up-to-date and your software roadmap on track.
GitHub for People
Software teams do not exist in isolation, the code they deploy is consumed by business and end user customers; it is essential this whole system is considered.
It’s also been clearly identified that closer interaction between business users and developers during the full software engineering process is key to positive outcomes and success.
Harnessing ‘GitHub for People’ achieves this literally, merging the activities of marketing, product and technology teams into a single interface and set of workflows, and also extending the core use of the Github premise to this broader scope of work.
Requirements enter the developers realm as new Issues, where they can be progressed to a point of conclusion deployment to the GitOps environment. The collaboration features of the integrated Team Management apps cater for keeping every one ‘on the same page’ as it progresses through this cycle, which in turn can update their strategic product roadmaps.
Connecting Business and IT
Critically this establishes a formal two-way dynamic between ‘Business’ and ‘IT’, one that is enabled in real terms through the synthesis of these two main application sets – The strategy and planning of work, and the implementation and maintenance of it.
Apps like Aha.io cater for business users, in their case the ability to create large-scale strategy & product management roadmaps. This captures strategy at the highest organization level, then cascades it down into what are in essence Epics and Sprints, rolling up Requirements into Milestone delivery plans.
At this point the apps connect to exchange the main unit of work, the Github issue, and thus there is an end-to-end assignment of work linked to strategy, and back again. The Business team can break down their strategy into specific deliverables required, feeding the DevOps work stream in the form of user stories, with reporting on their progress fed back up the line via the same integration.
Establishing this ‘closed loop’ system the flow through it can be assigned measurement tags, leveraging factory line type optimization principles to find ways to expand and accelerate Deployment Throughput.