I'm currently involved in larger development projects, and our task and workflow organization has become chaotic. With multiple teams transferring code, tracking bugs, and planning sprints, our communication is scattered across emails, Slack channels, and various documents. I've experimented with tools like Trello, but they don't meet our needs for deeper integrations, like linking code repositories to tasks or automating status updates across boards. We're considering workflow automation tools to minimize repetitive manual updates and keep everyone aligned. What tools or setups do you recommend for maintaining structure while accommodating a team of over 20 people?
5 Answers
Ever thought that maybe the issue could be trying to enforce agile workflows when waterfall phases might work better for how your teams hand off code?
I totally understand the chaos! Relying solely on emails, Slack, and docs doesn't scale beyond small teams. We've had success using a traceability layer that connects tickets, code, and specifications all in one spot. Tools like Jama Software can reduce confusion and help structure cross-team workflows without hindering development.
Got it! A traceability layer sounds like a smart move to enhance structure.
I've seen Linear work well for integrations, but I've noticed that even with great tools, teams sometimes fail because they lack a clear understanding of their workflow. Maybe take a week to actually document your process first before jumping into new tools!
That makes sense! Any pointers on how to keep track of those handoffs and informal steps without stalling ongoing projects?
Sometimes, the real issue with scattered emails and Slack messages indicates a need for clearer communication protocols rather than just searching for better software.
It sounds like you might need to draw a line between your build and run processes. Using tools like Trello or Linear for builds is fine, but you'll need good process management in your run phase. A service desk can help manage the chaos while allowing people to stick with their current tools like Slack and GitHub.
Interesting point! How do you envision the service desk providing real-time updates from tools like GitHub or Linear without introducing delays?
We haven't fully explored that, but it could definitely help smooth over the handoffs while keeping some level of agility.