Spliting into Projects

GilK

Hi,

Facts:

1. We have few groups at our company: HW, Embedded, Servers, Web, Mobile.
2. A product includes deliverables from all groups: hw- a device, embedded software - which runs on the device, a server to listen for the device, web and mobile applications to control the device via the server.
3. Each group has its own ALM, some are SCRUM some are not.
4. Each group include developers, testers, project managers (or product owner), team leaders (or scrum master).
5. There is one group, named integration, which responsible for testing the products (all the groups deliveries together).
6. There are few product managers that each one of them is responsible for a product or more (which is developed and tested by all the groups into a single product).
7. We have dozens of devices and dozens of R&D people!

Design:

I thought about the following JIRA design:

Each group will have their own JIRA project, hence, will have their own boards.

That way, each group, will manage their own tasks and bugs.

Problems:

Here come the integration team and the product managers:

The integration team tests a product, sometime they know where the bug belongs and sometime they guess or they are wrong.
The integration team should be able to open bug(s) to each one of the groups.
I think it is a bit clumzy for them to run between projects every time they encounter a bug. What do you think?
What is the best way for them to use JIRA?

Also, we have the product manager, which is responsible for defining features. When the PM defines a features it may be implemented in one group, two groups or more. How would they use the JIRA then?

Do you have any ideas?

Thanks,

Bob Swift

Consider having a project where incoming bugs and/or enhancement requests always go. They could come from internal or external sources. Use components to indicate multiple potential impact product areas. You need a process for analyzing the issues regularly and pushing them to all affected product areas. We do something like that, in our case, we use generic ids for Engineering (bugs) and Product Manager (enhancements) with various people responsible for handling them in a timely manner. Once it is determined what to do with the issue, issue is cloned to respective product area or requirements project. The original issue is eventually closed. We use custom clone operations (JIRA Clone-Plus plugin) to get the issue cloned with the right data and automatically create a link.