Skip to content

Vision Feedback

Jim Brucker edited this page Feb 11, 2015 · 13 revisions

Feedback on Vision & Mock-up

2Big2Slim

  • Vision does not follow the template.
  • Vision is incomplete: lacks background, list of stakeholders, opportunity, and vision of solution.
  • "How will it be used?" (don't use Q&A style) should be Major Features.
  • Poor layout. Don't use ad hoc Q&A style headings, e.g. "What is it ?" (and don't put space before "?"). Use section headings as in template, or something equivalent.
  • No link to Mock-up in Vision.
  • Vision is
  • Mock-up is OK, but does not show submittal steps. There should be feedback and confirmation during submittal.

JDED

  • No link to Vision on project site.
  • No link to mock-up on project site.

MAXININONTNACHY

  • Team name is too long.
  • Vision doesn't follow template: Background, Vision, Scope, Business Case.
  • Don't use Q&A style headings. Use descriptive names.
  • Vision contains some detailed requirements (which are wrong) instead of describing major features and purpose.
  • Mockup is very incomplete.

Maepo

  • Vision doesn't follow the template. Vision is very incomplete.
  • Don't use ad hoc Q&A style headings.
  • Has some background, description of need, and requirements. But parts are WRONG! ExceedCamp never used Google Forms (which is stated multiple times in Vision), QR code was not Aj. Panpiti's requirement.
  • Wrong features: Web app can't work offline, "trackable data" and "server constraint" are vague, "not as reliable as Google Forms" is arbitrary speculation (how do you know?).
  • Mock-up using http://moqups.com is interesting, but mock-up lacks explanation and screens seem arbitrary. Some of them are not important to the application. I doubt we will use mobile interface to create teams.

Team Saint

  • Vision doesn't follow template.
  • Don't use Q&A style with ad hoc headings. Use standard headings.
  • Content is too terse and imprecise. What does "Who?" mean?
  • Vision states some minor or detailed requirements instead of broader requirements.
  • Same "Google Forms" error as Maepo's vision. ExceedCamp did not use Google Forms.
  • Mock-up is poor. I wouldn't know how to vote if presented with those screens.

TheFrank

  • Vision doesn't follow template.
  • Vision is incomplete.
  • Don't use ad hoc Q&A style headings. Use heading as in template or equivalent.
  • English errors (several). Space after comma, never a space before comma.
  • Wording of features is too vague: "users can rate and vote the application". What application? What's the difference between "rate" and "vote"?
  • "Every thing can be change by admin". Really? EVERYTHING? (Not: "Every thing")

TeamGG

  • Please list team members on first page (README.md).
  • "Overall Description" section of SRS is not a substitution for Vision statement. The purpose of the Vision is to provide an overall picture of the context, the problem, the proposed solution, and business case (why is it worth doing).
  • No mockup.

Intro to Play Framework

ExceedVoting - assignment for 16-23 April.

Clone this wiki locally