RELATED IDEAS
A way to account for Engineering teams not aligned to Products
We have a a large and complex code base that requires our Engineering teams to be aligned with components, rather than products. With multiple products using multiple engineering resources, it makes release planning just short of a nightmare. Having a way to manage our products "normally" while still splitting up epics and features across several component teams would be helpful. Engineering likes to use Aha for capacity management, so they have their own 'products,' but this makes for a lot of manual synching between all the products.
© 2024 Aha! Labs Inc.•All rights reserved
Hi there, we have a similar problem, but the link you suggested doesn't seem to work for us. I'd appreciate some direction if this is something we can solve by way of configuration.
Context:
We have iOS, Android, and some micro service components in Jira that are all managed by one product manager. We sprint together and share a single Jira project. Before trying Aha, we've been able to share our Epics but in planning our projects migration we've realized that modeling our releases results in a lot of duplication (e.g. many copies of epics landing in Jira).
Is there a good playbook for a situation like this? I'm considering that instead of a release per iOS, Android, and Microservice?
Hi Kevin, thank you for your idea. There is a lot of flexibility in how you organize your products and a couple different approaches for this situation, depending on your specific workflow. One approach is outlined here. I have asked our Customer Success team to connect with you to provide additional guidance. Thanks!