Skip to main content

Project: Sprint 2

For the second sprint of the group project, you will plan the sprint with your team members and implement the features you committed to for this sprint.

danger

The provided slip day and resubmission accommodations may not be used on group assignments.

Learning Objectives​

  • Author a project backlog for your prototype app.
  • Prioritize the items in your project backlog.
  • Plan a sprint with your team members.
  • Complete the tasks you committed to for the sprint.
  • Manage your time effectively to complete the work for the sprint.
  • Communicate effectively with your team members to complete the work for the sprint.

Help & Support Resources​

We want you to get the help and support you need. Use the course's support resources for help with this assignment.

Git Repository & Codespace​

  1. Create your submission repository.

    Visit https://landrace.infosci.cornell.edu/courses/info4340-2026sp/repos/project in your browser.

  2. Open your repository in GitHub.

    After creating your repository, visit https://landrace.infosci.cornell.edu/courses/info4340-2026sp/repos/project in your browser and follow the link to open the repository on github.com.

  3. Open your repository as a codespace.

Teamwork​

Working effectively together is every team member's responsibly. If there's a conflict, address it. Don't pretend that the conflict will simply go away.

Resolving Conflict​

Conflict is a healthy part of any team relationship. If your team doesn't have conflict, then your team members are likely not communicating their issues with the other team members. This is bad. Use a team contract to keep your team dynamic healthy.

When you have conflict, you should follow this procedure:

  1. Refer to the team contract and follow it.

  2. If you resolve the conflict without issue, great! Otherwise, update the team contract to improve your ability to work together moving forward. This is required.

  3. With the updated team contract, try to resolve the conflict.

  4. If that fails, please contact the instructor. I'll ask to meet with all the group members and figure out how we can work together to move forward. I will not help your team unless I see that the team contract has been updated to try and resolve the conflict internally first.

  5. Do not, under any circumstance, avoid confrontation if you have conflict. If there's a conflict, the best way to handle it is to bring it into the open and address it.

The Slacking Team Member​

Do not cover for a team member who is slacking. This only rewards their bad behavior. Never put a team member's name down for a submission if they did not contribute. This is a violation of the code of academic integrity.

Tip: If you have a team member who is not contributing, have them work on non-essential work the project. Maybe that's making them responsible for a designing/coding an optional top-level view. If this view doesn't get made, since it was non-essential, that's okay. If it does, great!

Part I: Project Backlog​

The project backlog is a list of all the tasks that need to be done for your project. This includes both the basic features that you need to have for your app to work and the cool features you want to add. It also includes the tasks associated with implementing those features, such as designing the UI, writing the code, and testing the app.

Requirements & Credit​

Credit: ~10 points

This part is graded for correctness. Meet the following requirements for full credit:

  • A thorough project backlog for all project tasks is provided.
  • The project backlog is prioritized. The most important tasks are at the top of the backlog.
  • The backlog lists all tasks that are needed for all features of your project, like designing the UI, writing the code, and testing the app.

Professionalism:

Professionalism means meeting the client's requirements. Not doing less and not do more. Your submission should meet the requirements specified for this part and no more.

Instructions​

  1. Create a project backlog for your project.

    You may use any tool you like, including GitHub Projects.

  2. Upload a PDF of your project backlog to Canvas.

Submission​

Upload a PDF of your project backlog to Canvas. The content of your project backlog must reside inside the PDF. No credit for PDF files with links to other documents. (We will not follow any link provided in the PDF file when grading.)

It is every team member's responsibility to verify that the PDF is complete, ready to be graded, and correctly submitted before the deadline. One person forgetting to submit will result in a 0 for the entire team. You are professionals. Act like professionals.

Part I: Sprint 2 Planning​

Plan your second sprint with your team members.

Requirements & Credit​

Credit: ~10 points

This part is graded for correctness. Meet the following requirements for full credit:

  • A clear and detailed plan for sprint 2 is provided.
  • The plan includes the specific features that will be implemented in sprint 2.
  • The plan includes the specific tasks that will be completed in sprint 2.
  • The plan includes a clear timeline for completing the tasks in sprint 2.
  • The plan includes a clear assignment of responsibilities for each team member for the tasks in sprint 2.
  • The plan is ambitious, but realistic and achievable within the sprint 2 timeline.

Professionalism:

Professionalism means meeting the client's requirements. Not doing less and not do more. Your submission should meet the requirements specified for this part and no more.

Instructions​

  1. Create a plan for your next sprint.

    You may use any tool you like, including GitHub Projects.

    Move items from your project backlog into your sprint plan.

    Your team will commit to completing all the items in your sprint plan by the end of the sprint. (This upcoming Thursday.)

    Suggestion: Feasibility is a common risk for new app ideas. Consider including tasks in your sprint plan that will help you assess the feasibility of your app idea.

  2. Submit your sprint 2 plan as the preparation for the next class.

Submission​

Upload a PDF of your sprint 2 plan to Canvas. The content of your sprint 2 plan must reside inside the PDF. No credit for PDF files with links to other documents. (We will not follow any link provided in the PDF file when grading.)

It is every team member's responsibility to verify that the PDF is complete, ready to be graded, and correctly submitted before the deadline. One person forgetting to submit will result in a 0 for the entire team. You are professionals. Act like professionals.

Part III: Sprint 2 Implementation​

In this part, you will implement the features you committed to for sprint 2. You must complete all the tasks you committed to for sprint 2 by the end of the sprint. (This upcoming Thursday.)

Requirements & Credit​

Credit: ~30 points

This part is graded for correctness. Meet the following requirements for full credit:

  • All the items that were committed to in the sprint 2 plan are complete.
  • The work completed (design, testing, feasibility assessment, planning, coding, etc.) should be done well and to the standards set by the course.
  • For full credit, the work completed should be ambitious.

Professionalism:

Professionalism means meeting the client's requirements. Not doing less and not do more. Your submission should meet the requirements specified for this part and no more.

Instructions​

  1. Implement the features you committed to for sprint 2 in your team's repository: https://landrace.infosci.cornell.edu/courses/info4340-2026sp/repos/project

    Use your sprint 2 plan as a guide for what to implement.

  2. Include any instructions to the grader where to find the work you completed for sprint 2 in the README.md file at the root of repository.

Submission​

Thoroughly check your prototype submission and verify that it is ready to be graded. Check that your submission meets all assignment requirement. Note that if npm run dev fails to successfully run from the root of your repository during grading and render the app in the browser, we won't be able to grade your submission, and you will receive a 0 for the assignment.

Stage, commit and push all changed files in your Git repository to the GitHub server. (All commits should reside on the main branch.)

One team member must complete the submission form for sprint2 to submit the assignment.

It is every team member's responsibility to verify that the prototype is complete, ready to be graded, and correctly submitted before the deadline. One person forgetting to submit will result in a 0 for the entire team. You are professionals. Act like professionals.

Contributors​

Copyright © 2023 - 2026:

  • Kyle Harms
Last updated on