Build a ToDo Application (a classic web/mobile application). We’ll accept any sort of classic ToDo application, built using GitHub CoPilot (or CoPilot Chat), or any (current!) tutorial online, see, e.g.:
Regardless of how you create your app, we suggest that you attend to the implementation of the following key concepts:
- Reusable components
- Passing properties
- Flex styling
- Button event handler functions
- Using hooks to manage state
Submit this application by pushing it to your cs262
repo along with a screen dump of the running program (in a web
browser or mobile device emulator, e.g., see the web image to
the right).
Use the "Stakeholders" wiki in Moodle to sign up to be a
stakeholder for one of the other project teams (cf. Guide 4).
You will follow this team for the remainder of the semester so,
as much as possible, we’d like to have only one member
from each team reviewing any other team. Sign up for your team
in Moodle under “Team Stakeholders”. When
you’ve picked your team, review the sprint-one
deliverables from the other team you are reviewing
(see project deliverable
#1 — see the team GitHub repo linked from the
Moodle “Team Members” page) and post the following
to their Slack #stakeholders channel:
- A one-paragraph review of their vision statement — How unique and compelling is their project idea? Is the vision statement well-written?
- A one-paragraph review of their prototype code — Is it there? Is it well-documented? Did they implement something reasonable on which to base their application?
Be prepared to explain your review to them during their team meeting in lab 4.
You may need to save a copy of your comments until your
stakeholder team gives you access to their Slack
#stakeholders channel. Let them know if you cannot
access all of their materials by the end of lab 4.
Review your teammates with respect to the following aspects of their work on your team. The agreement value is on a standard Likert scale (1-strongly disagree; 2-disagree; 3-neutral; 4-agree; 5-strongly agree).
Characteristics Agreement Comments Communication Stays in contact with other team members. 1 - 2 - 3 - 4 - 5 Do they keep up with the project management tools? respond to email? Stays on topic during meetings. 1 - 2 - 3 - 4 - 5 Deals with conflict openly and respectfully. 1 - 2 - 3 - 4 - 5 Contribution Finds and fills a useful role on your project. 1 - 2 - 3 - 4 - 5 If yes, which role (or roles)? Does their share of the work. X% Estimate what percentage of the work this team member has done relative to the others. Steps in to help others when needed. 1 - 2 - 3 - 4 - 5 Engagement Shows up on time (or make alternate arrangements). 1 - 2 - 3 - 4 - 5 Meets deadlines. 1 - 2 - 3 - 4 - 5 Is passionate! 1 - 2 - 3 - 4 - 5
Include your assessment and comments in a copy of this: Team Member Review
chart.
Copy/edit this sheet as appropriate and then save/submit it as a
XLSX (or CSV if needed) named memberReview.xlsx,
and submit it in Moodle (so that it’s private!).