Step 9: Next Meeting Sprint 2

[PaulaR-05]

Please Fill up the When2meet: https://www.when2meet.com/?19957775-yXTNu

• Sprint 2 - Getting off to a Solid Start

  • Create a low-fidelity wireframe

    Objective

    Establish a common understanding across the team of what information is in each screen and the actions that may be invoked from each screen.

    How

    • Using the features you added to the the Feature Planning template in step 4 identify the screens you’ll need and the information on each one.
    • Map the actions users will be able to perform from each screen and the navigation from screen-to-screen
    • Create a low-fidelity wireframe using a tool like [Figma](https://www.figma.com/) or even pencil and paper.

    Resources

    [How To Wireframe A Website in 3 Easy Steps](https://elementor.com/blog/wireframe-website/)

  • Setup Project Backlog

    Objective

    The [Project Backlog](https://www.notion.so/c0b10b9e0c9a4e80a0c3482433fb08a4) is where you track the work that needs to be completed to finish the project.

    How

    • Identify & prioritize features
    • Create an epic for each feature
    • Choose the highest priority epics & divide them into user stories
    • Add your epics & user stories to a backlog tool. Due to it’s tight integration with GitHub we suggest using ZenHub (it’s free for teams using public repositories)
    • Prioritize the user stories

    During the Voyage you’ll refine the Project Backlog and in every Sprint you’ll move tasks from it to the Sprint Backlog. This is part of the Agile process helps you and your team concentrate only on the tasks that must be completed in that Sprint.

    Resources

    [Define Your MVP](https://www.notion.so/c0b10b9e0c9a4e80a0c3482433fb08a4)

    [How to Create a Project Backlog (video)](https://youtu.be/FaoT-DTtXyA)

    [Agile Methodology 101 (article)](https://www.notion.so/f9e0ccc88d894f609a652d6d8a4c0df6)

    [ZenHub website](https://www.zenhub.com/)

    [Install ZenHub browser extension](https://tinyurl.com/yfpcf7ke)

  • Setup your team workflow

    Objective

    Define how you plan to work together as a team. This includes how often you’ll share status, coding standards, git/GitHub processes, and deciding how many meetings you need each week and when and where they’ll take place.

    How

    • Decide on the coding standards the team must follow.
    • Define the characteristics of your repo including the number of branches, branch names, & the workflow everyone must follow.
    • Agree on the format of commit messages, how Pull Requests will be reviewed, and GitHub branch protection rules.
    • Decide on where you’ll deploy your app and the branch to be considered as ‘production’ you’ll be deploying from.
    • Decide on what meetings you’ll need each week and to save time, schedule them as recurring meetings. You might want to look ahead to to learn more about the types of meetings you’ll need.
    • [Develop the App](https://www.notion.so/Voyage-Guide-1e528dcbf1d241c9a93b4627f6f1c809)

    Resources

    [Javascript Style Guides](https://codeburst.io/5-javascript-style-guides-including-airbnb-github-google-88cbc6b2b7aa)

    [Defining a Git Workflow (Chingu Handbook)](https://www.notion.so/d5fba28e1d3043e1910b7d2eb8999793)

    [Git Branches (Chingu Handbook)](https://www.notion.so/7ccbd0a34e1c4b87af583e3760632727)

    [Git Commits (Chingu Handbook)](https://www.notion.so/6334daca89f840f381ee1e57243091ad)

    [Git Pull Requests (Chingu Handbook)](https://www.notion.so/6eeda3f9342941ef9a06d1057f0b87a6)

  [Sprint 2 Tasks at a Glance](https://www.notion.so/e02745c27a774a21a9a47c49d740db61)

[PaulaR-05]

We met today, I still have to finish one task from this SPRINT 2. The "team workflow".
I might be finishing it tomorrow.