v3 Sprint 1 Week 1 - Code-the-Dream-School/React-Node-Practicum GitHub Wiki

At your first week Sprint 1 full-stack meeting you should cover the below project details. Have one group member take notes as you go, write the information in a Slack message and pin it to your group’s channel for later reference.

  • What will you be building?

    • What problem does your app solve?
    • What elements will you need? Outline your database’s models and relationships.
    • What features will you include? Outline what users can do with your app.
    • Check out this list of 60 ideas if your group is stuck!

  • What are the expectations of each group member?

    • Consider group norms like responding to messages in a timely manner, and building on one another’s ideas.

  • When will you plan to hold meetings?

    • Consider full-stack meeting time +/- front-end only and back-end only meetings

  • Your mentor will create a account on Jira (project management tool)

    • This tool will be explained by your mentor(s) and how to use it.
    • It will allow each team member to have tasks assigned to them.
    • Each task will have information on it about specifically explaining what needs to be done.

  • Begin to define work using tickets, or “Issues” on your Jira Kanban board. Break tasks into small, manageable chunks.

    • Your tasks for the first sprint (Week 1 & 2) will all about defining your MVP
    • Include tasks to decide on your project and functionality, wireframes, document core API routes and database schema.
    • Be sure to include a ticket for adding/editing the ReadMe
    • You will also need to consider how your React front-end will integrate with your Node back-end. Review JWT authentication and incorporate some tickets relating to setting this up.

  • There will be no coding tasks in the first 2 weeks.

At your weekly meetings, you’ll review the backlog (your “To-Do” column) and decide what needs to be worked on next.

  • Team members will assign themselves to tickets and that will be their project work for the week.
  • When a ticket is complete, move it to “Done,” resolve any merge conflicts, and make a pull request (more on that next week).

Additional Resources

Dev Methods