Open designswinger opened 8 years ago
Capturing Non-Dev tasks (design, service design blueprinting / user journeys, marketing templates, etc) "I still suggest capturing non-dev tasks on the Issue tracker on GitHub. Labels can be created for types, e.g.. marketing, design, wireframing etc. Kim & Mariza have added wireframes & designs to the Issue section and i think it works well - multiple benefits…keeps the project transparent and active, all project Task tracking in one place wit the project, tech & non-tech can comment & get involved from an earlier stage (less surprises & confusion"
...@eddiejaoude
...teams will need help roadmapping their tech needs as product dev is new to them...
Sure :+1:
Milestone | Use standard milestones to show progress of the project |
---|---|
Labels | use the correct labels (add accordingly but should be standard) - eg. type: documentation , type: wireframe , priority: high |
@eddiejaoude @atmostat I think the teams will need help roadmapping their tech needs as product dev is new to them, so accelerator organizers can work with them on is looking at their current work plan and pulling out “micro services” that can be added to GitHub that we can direct people to. (pretty simple things like Translation, SEO, etc).