Member-only story
Software development teams use ticketing systems to manage work requests, such as Jira, Asana, etc. They use source code management tools to manage the application’s source code, such as Github, Gitlab, etc.
The modern development teams usually practice code review to improve code quality and reduce the bus factor. Upon the code completion, they open a pull request and invite team members to give feedback.
You, as a manager or a team lead, it is challenging to track team performance when you don’t see the connections between tickets and pull requests.
For starters, the number of completed tickets is your team performance metric. However, in practice, a complex ticket requires a few steps to complete. Those sub-steps are converted into subtasks in the ticket and a couple of pull requests. This kind of complexity is hidden within the development workflow.
To unearth the complexity, you should be thinking about the development workflow in the system.
Development Workflow is a System
This system diagram illustrates the development workflow across the two platforms. Let me walk you through:
- Ticket is the inventory of the in-progress tickets in the ticketing system, which included the various development…
