What is the challenge? |
Use Case/Scenario: We have a business problem where Aha Products are receiving both Ideas and Work requests and need to prioritize the potential resulting work effort. Business Problem we are trying to solve: When a Aha Product receives both Ideas and work request from other Aha Product then they have no way to prioritize both ideas and work requests in a single list view in order to determine prioritization regardless of the source? |
What is the impact? |
Manual Path to connect the resulting work back to the planning initiative: Today the manual steps that would need to take place include; A) Portfolio initiative with work request to B) Product Workspace which accepts as an Idea and then C) promotes idea to feature and then D) manually creates a ‘dependency of’ link back to the Portfolio Initiative. |
Describe your idea |
Potential Solution: Could we have the Product accept work requests as ideas, thus have a single list of ideas to prioritize? But then have a way to connect the ideas from the work requests pass the ‘dependency of’ relationship to the resulting feature?
|