-
Notifications
You must be signed in to change notification settings - Fork 16
Sprint 2 July 12, 2017
Cydney Luong edited this page May 8, 2018
·
1 revision
On July 12th, the TalentMAP team met to perform a retrospective of the sprint. The team first reviewed I Wish... items from the previous week, and moved on to dot voting. Each team was dot-voted on using the process of every participant having 6 votes, where the first vote is 3 dots, second vote is 2 dots, and third vote is 1 dot. The themes are ordered based on the number of votes they
- Building prototype (speed, cohesion, unification, code completed in a timely manner) - 17
- control over hosting environment -
- ITCCB status - Action Item - Set up a meeting with ISSO
- research design needs to be on GitHub
- research + design - set some aside some design time in the next sprint
- onboarding process - point of contact is Edwin
- clarify of completed work - non-technical language
- placeholder data - be vigilant and keep tabs on items
- who can add issues on GitHub
- posting data/ in the wiki
- branding (sad face) - handle in sprint
- technical language - use more plain language
- Branding kicking off with design work
- Finding was to include user research into stories
- Usability testing
- Mock-ups
- Stagger front end and back end tasks across sprints
- Start regular meeting about DoS hosting environment
- In-person meetings with ITCCB
- Hosting + security uncertainty at DoS
- Obtain status about onboarding
- Provide status updates in plain language
- Design Principles
- Content Styleguide
- Design Styleguide
- Design Sprint Workflow
- Information Architecture
- User Profiles
- Branding
- Research Strategy
- Bidder User Research
- Career Development Officer User Research
- Assignment Officer User Research
- Homepage and Filter Tests