tP Week 3: KickofftP Week 5: Gather Requirements


tP Week 4: Set Direction

  1. Start weekly project meetings
  2. Start a collaborative document for project notes before the tutorial
  3. Decide on an overall project direction (user profile, value proposition) decide by tutorial, submit by: Sat, Sep 5th 23:59

Intro to tP Week 4

This week, the tP focus is on setting a project direction, i.e., deciding on the type of users your product will target, and the value it will provide for those users (what problem does it solve?).
Holding weekly project meetings and keeping notes of project details are two other things we'll start this week.

1 Start weekly project meetings

  • We recommend you start weekly project meetings now. You can use these meetings to do tP tasks, but also to help each other do iP tasks. On a related note, it is also acceptable to discuss the weekly Canvas quiz (if any) together with team members as you do the quiz, i.e., discuss and decide the answers collectively, but you should not give away your answers to someone who was not part of that discussion.

2 Start a collaborative document for project notes before the tutorial

  • Keep project notes in an easy-to-use collaborative doc (Recommended: use a Google Doc). This document will be checked by the instructors at various points.
    Remember to choose a tool that allows public view access, e.g., a Google Doc can be shared via a public link so that the document can be viewed by others. You'll be asked to submit this link to us next week.
    Make sure all your current and future project notes (if split into multiple documents) are reachable via links given in this document and are viewable by the public.

3 Decide on an overall project direction (user profile, value proposition) decide by tutorial, submit by: Sat, Sep 5th 23:59

  • Decide the target user profile and value proposition, as described in the panels below (tip: you can use your first project meeting for this):

As we are still in the early stages of identifying a problem to solve, do not think of the product (i.e., the solution) yet. That is, do not discuss the product features, UI, command format, implementation details, etc. unless they are pertinent to the user profile or the problem addressed.

You can use the button in a panel to open it as a new tab (it can be expanded in-place too). This feature is available only for panels containing another full page of the website (i.e., not available if the panel contains an extract of a page).

Admin tP: Overview

Admin tP: Expectations

Admin tP: Constraints

Pick a CLI-friendly product domain: Given Recommendation-CLI-First and Constraint-Typing-Preferred mentioned in the panels above, it makes sense to pick a product domain that is more suitable for CLI interactions, i.e., a product that deals with easy-to-type textual data, needs a small number of data fields, and has short data fields. For example, keeping track of extensive employee records may be an unsuitable domain if there are many data fields per employee.

  • Submission: Submit via TEAMMATES.
    • Details to submit:
      1. Product name (plain text only) e.g., ClientContactsPro
        We recommend using English characters only. Special or accented characters (e.g., è) might feel 'cute' now, but you will regret using them later when you need to use the product name in submission file names, etc.
      2. Target user profile (plain text only) e.g., freelance event photographers
        This is a general description of the target user, not the 'persona' you defined (the latter serves as a concrete representation of the target user, for your internal use only).
        No need to mention 'who prefer a CLI' here, as that is given.
      3. Value proposition, i.e., what problem does the product solve? (plain text paragraph, no more than 50 words) e.g., provide fast access to client contact details, optimized for users who prefer a CLI
        This is not a list of features -- you should not think about exact features yet.
        No need to explain why this app is better than other similar apps -- just explain what it does for the target user.
      4. Link to the project notes document:
        This should be an online document/page (not a folder) -- e.g., a GoogleDoc (not a Google Drive location) -- that is publicly accessible. If your project notes are in multiple locations/files, this one document should contain links to the other documents with guidance on what each link is for.
        This should be a link with 'view' permissions only, not an 'edit' link. (reason: if the latter, anybody will be able to edit your project notes after we publish the link on the course website)
    • You'll receive an email from TEAMMATES with the submission link. Only one member needs to submit on behalf of the team. All members can view/update the submission.
    • The submission link will be sent to you by Thu, Sep 3rd (reason: we need a few days to set up the submission system after teams have been finalized).
      If you can't find the submission link, you can go to the TEAMMATES link recovery page and enter your NUSNET email address e_______@u.nus.edu to get TEAMMATES to resend the link.

FAQ Can we change the product name, the target user, and the value proposition later in the project?


tP Week 3: KickofftP Week 5: Gather Requirements