RELATED IDEAS
Basic Approval Steps In Feature Workflow
We all want to to be following an Agile process and Aha! in conjunction with JIRA allow us to do this. However, we need to do Agile with an element of control around key stage gates of the lifecycle of a Feature since we have to maintain our ISO certification and we need to pass audits from certain key customers in certain markets - Pharma and Defence are prime examples - these want to see control in place at key stage gates.
We have the following steps in our Feature Workflow:
Systems Engineering->Engineering Backlog->Release Backlog
We need to sign-off the transition from Systems Engineering to Engineering Backlog between the primary stakeholders of PM, Development & Architecture - this represents a Draft requirement in our SDLC and we need to sign-off the transition from Engineering Backlog to Release Backlog with a wider set of stakeholders such as QA as this represents a fully defined, estimated and resourced feature Committed to be delivered in the release.
We currently use a sign-off block in the Feature description combined with the addition of the comments "Approved for Engineering Backlog" , "Approved for Release Backlog" from the required signatures at these two stage gates.
It would be great if some kind of simple (optional) approval process like this could be configured within the Feature Workflow.
-
ADMIN RESPONSEJan 22, 2020
Just launched!
You can now ask colleagues to sign off on plans directly in Aha! — assign approval tasks and set due dates as part of your status workflow.
Learn more in our blog post and support article.
5
MERGED
Provide ability to require certain activities as part of a status and pre-req before moving onto next Status.
We would like to require certain activities during a specific status and as part of our workflow. Only once these activities are complete, can the product owner move on to the next step. This would be helpful with any custom workflow (idea, releas...
0
Shipped
3
MERGED
6
MERGED
Create/assign a to-do automatically based on a status change
In order to have enforced approval process, it would be great to have a to-do created and assigned to a user when the status is changed to an approval status. We want to add approval steps to workflows to prevent features from being added to a rel...
0
Shipped
4
MERGED
Prevent a change in idea status or promotion to feature until a specific condition is met
Before an idea can be promoted to a new status or feature, we would like to capture that a specific person is aware of the request and in agreement with it (we don't need this specific person to actually log into Aha and indicate approval, we just...
0
Shipped
© 2024 Aha! Labs Inc.•All rights reserved
I don't think you follow my requirement. I want to be able to control moving from one state to another based on a configured list of stakeholders having pressed the Approved button or something similar.
In many organizations that also follow forms of Agile development, stakeholder or executive approval is necessary at various key stages in the project process especially at the Vision stage. An approval process could follow the principle that Notebook creators can assign approvers when one is published and if rules are specified: Unanimous or Majority, the approval criteria could be recorded in the system.
Ideally, variance from this approved vision should be visible in each child element; features, requirements etc. in order that progress towards the vision can be easily seen.