39 -- Planning Check-In

[al-the-x]

• Standup Meeting (~15m)
• Three Little Things (~30m)
• Progress Review (~1h)
  • [x] Jessy Riordan (@JessyRiordan)
  • [x] Sean Joyal (@sjoyal)
  • [x] Michael Staehling (@MStaehling)
  • [x] Jorge Hernandez (@jorgehjr84)
  • [x] Phillip Creglow (@pcreglow)
  • [x] Melissa Rodríguez (@melrodbos)
  • [x] Nick Pope (@pope410211)
  • [x] Kim Mattiko (@kmattiko)
  • [x] Michael Pascuzzi (@gatorpazz)
  • [x] Ben Griffith (@Epicurean306)

[al-the-x]

@JessyRiordan

• What if I haven't added an image yet?
• What if I don't have any Products added yet?
• What does it look like on desktop? Tablet?
• What is your MVP? Group those stories vs Stretch Goals...
• Great use of checklists in Planning issue!
• Split up BIG stories into smaller stories
• Add estimates with labels: S, M, L, XL
• Indicate MVP, Stretch, and Someday goals with labels?

[al-the-x]

@sjoyal

• Good job brain dumping into the wiki!
• Good release plan; convert to Milestones
• Missing "so that" clauses
• Break down the BIG stories, add invisible stories
• Nice level of detail on the feature issues, perhaps better in the wiki though?
• Nice mockups and Skitch diagrams

[al-the-x]

@MStaehling

• User Stories: A Smurf can smurf so that Smurfs can smurf
• Group by MVP / Stretch / Someday goals
• Difficulty estimates will help with MVP
• Split "edit/delete" into separate stories
• How do we login? Missing from sketch?
• Maybe mockup UI with Markdown / MFg HTML?

[al-the-x]

@jorgehjr84

• Little too heavy on the implementation details: modal vs submit view, caret and gear buttons
• Organize into stories with details instead of nested lists
• User Story: A Smurf can smurf so that Smurfs can smurf
• Is login optional? I think not...

[al-the-x]

@pcreglow

• Too much "I can see..."; what can I do?
• Pull map / route data from RunKeeper or similar service?
• Links to issues or milestones?
• Great questions under each story; answers?
• What data about a route is available? Are there multiple routes?

[al-the-x]

@melrodbos

• Great description of the problem domain and proposed solution!
• Great job recording your brainstorming session!
• Your "...can view the home page..." stories can be shared as "Anyone can view..."
• Need to focus on one group of features for MVP: maintenance requests, payments, communication
• Good looking mockups, maybe some sample data populated instead of big grey boxes?
• Link to reference implementations and Skitch the interfaces

[al-the-x]

@pope410211

• Group stories by MVP / Stretch / Someday
• Pick one term -- User or Gamer -- and Use and Capitalize consistently
• How about those deadlines?
• STEP AWAY FROM THE SHINY!
• Designers are dangerous...

[al-the-x]

@kmattiko

• Personas are awesome! Great work on stories!
• Drag and drop file uploads can be tricky...
• Write down your extra ideas, even if they never happen.
• Keep the "Gimme distance..." feature
• Use all the data you're collecting, eg "Who are you movi on from?"

[al-the-x]

@gatorpazz

• "A future user" is a little odd; "a guest" instead?
• Make searching for a book a part of adding a book for validation purposes, like checking for an address with Google Maps
• Login with Google instead of creating a (secure) username and password?
• Missing stories and screens:
  • Details for a book
  • Adding a book
  • Editing book details (change ISBN for another edition)
• Missing details on stories: need more checkboxes!

[al-the-x]

@Epicurean306

• Too much implementation jargon (Firebase); focus on what I can do.
• Mockups too high-fidelity, focused too much on implementation details.
• Okay to make a short name to refer to really long stories, but promote the real text to a heading
• Indicate MVP / Stretch / Someday goals in your issues: labels?
• Reduce the verbosity of your stories: "news keyword topics" to "Articles"
• Split up BIG stories: use of "and" / "or" is a clear indicator