I’m a new tech lead with front-end and back-end devs. Without Agile sprints or user stories, how do you track collaborative work in Jira for features needing multiple contributions?
As a tech lead who’s been in your shoes, I can share what worked for me. Instead of Agile sprints, we used a modified Kanban approach in Jira. We created epics for major features and broke them down into smaller tasks. Each task was assigned to the relevant developer(s) with clear acceptance criteria.
We used custom fields to track which part of the stack each task related to (front-end, back-end, full-stack). This helped visualize the workload across teams. We also set up a ‘Blocked’ status and encouraged devs to flag dependencies early.
Regular stand-ups (3 times a week) helped keep everyone aligned without the overhead of daily scrums. We used Jira’s reporting features to track cycle time and identify bottlenecks.
The key was flexibility and constant communication. It took some trial and error, but we found a rhythm that worked for our specialized team structure. Remember, tools like Jira should serve your process, not dictate it.
From my experience, one effective approach is to create a custom workflow in Jira that reflects your team’s actual development process. Start by mapping out the stages your work typically goes through, from initial concept to final deployment. Then, set up corresponding columns in Jira.
For collaborative tasks, I’ve found it useful to create parent issues that encompass the entire feature, with subtasks for specific components. This allows you to track overall progress while still assigning individual responsibilities. Use labels or custom fields to denote which part of the stack each task relates to.
To manage dependencies, consider implementing a ‘waiting’ status and encouraging developers to link related issues. This helps visualize the flow of work across different specializations. Regular check-ins (perhaps twice a week) can help address any blockages or coordination needs without being too disruptive.
Remember, the goal is to enhance visibility and communication, not to add unnecessary bureaucracy. Adjust your system as you go based on team feedback and changing project needs.