You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently using the GitHub issues here, but that might not be the best way of managing this.
Secondly, we can take a look at Notion. Unsure how their pricing would work for us (think we have to pay per user, which is not gonna work for a truly open and inclusive process), but need to take a deeper look.
The tool needs to at least support (ad-hoc or natively):
Creating/closing tasks that should be done
Assigning people to tasks
Facilitate discussions around specific tasks
Ideally have a way of setting up dependencies between tasks
The text was updated successfully, but these errors were encountered:
Create initial discussion to scope what problem needs solving, and include what it's not gonna solve (small steps, focus on iterations)
Once problem scope has been locked down, figure out requirements to get there
If the problem scope is very large, break down the scope into many pieces and repeat from step 1 with all of the pieces
Task now open for someone to start working on. Lock the task for that person/group
Once open for review, people can leave feedback
Iterate until we're happy with it
Implement the design into the production resource
And once done, close the task as finished
Any opinions on this? We could implement this flow in most tools I think, only difference would be in how "locked down" the flow is, which probably at this stage is not as important as that we actually get into the flow.
Currently using the GitHub issues here, but that might not be the best way of managing this.
Secondly, we can take a look at Notion. Unsure how their pricing would work for us (think we have to pay per user, which is not gonna work for a truly open and inclusive process), but need to take a deeper look.
The tool needs to at least support (ad-hoc or natively):
The text was updated successfully, but these errors were encountered: