Sprints Purpose: More cross-team collaboration, catching engineering concerns/explorations needed earlier in process
Time duration: 1 week
Potential Test features:
- Video quizzes for rewards
- Profile to Nav + Live on All shows
If small size:
If med-large: engineering necessary earlier.
Figure out plan/meeting requirements
- Mini shareouts daily
- Cons: too many meetings?
- Slack reviews–give your feedback on this by X time.
- Pros: Threaded discussions
Tasks:
- Open question: How do we work in exec review (Product/Engineering)? - Adam Grandy
- Review rough outline below - Adam Grandy
- Confirm buy-in from Engineering Executive Team - Peter Gluck, Roland Tokumi
Rough Outline of 1 Week Sprint
| Day 1 | Day 2-2.5 | Day 3 | Day 4 | Day 5 |
|---|---|---|---|---|
Representatives all in a room for X hours Sprint Goal User Stories End of Day Slack update with Sprint Info Open Questions:
| Representatives - Sketching/Ideation together Design Exploration (can be break-out?) EOD Slack Update (Storyboards/Sketches/Whiteboard)
| More design exploration Morning: Formal share-out with broader group with rough designs Afternoon: Refine EOD Slack update | Have until 10am to get in feedback More Refining Prototype (Invision or if possible, Des Dev) (assumption no access to kids and we can't use usertesting.com) EOD Slack update | Exec/Spec review Debrief and revisions |