├── docs ├── meeting-sprint_preview.pdf ├── meeting-voyage_kickoff.pdf ├── meeting-sprint_planning.pdf ├── meeting-sprint_retrospective.pdf ├── meeting-vision_and_feature_planning.pdf ├── team_project_ideas.md └── team_decision_log.md ├── .github └── ISSUE_TEMPLATE │ ├── task-template.md │ ├── epic-template.md │ ├── user-story-template.md │ └── bug-report-template.md └── README.md /docs/meeting-sprint_preview.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chingu-voyages/voyage-template/HEAD/docs/meeting-sprint_preview.pdf -------------------------------------------------------------------------------- /docs/meeting-voyage_kickoff.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chingu-voyages/voyage-template/HEAD/docs/meeting-voyage_kickoff.pdf -------------------------------------------------------------------------------- /docs/meeting-sprint_planning.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chingu-voyages/voyage-template/HEAD/docs/meeting-sprint_planning.pdf -------------------------------------------------------------------------------- /docs/meeting-sprint_retrospective.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chingu-voyages/voyage-template/HEAD/docs/meeting-sprint_retrospective.pdf -------------------------------------------------------------------------------- /docs/meeting-vision_and_feature_planning.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chingu-voyages/voyage-template/HEAD/docs/meeting-vision_and_feature_planning.pdf -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/task-template.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Task template 3 | about: Tasks are small units of work that can be completed in a single sprint 4 | title: '' 5 | labels: task 6 | assignees: '' 7 | 8 | --- 9 | 10 | **__Task Description__** 11 | Describe the task to be completed. 12 | 13 | **__Technical Considerations__** 14 | Include any technical considerations including architecture (e.g. API), required libraries, etc. 15 | 16 | **__Additional Considerations__** 17 | Any supplemental information including unresolved questions, links to external resources, screenshots, etc. 18 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/epic-template.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Epic template 3 | about: An epic represents functionality that will span multiple sprints 4 | title: '' 5 | labels: epic 6 | assignees: '' 7 | 8 | --- 9 | 10 | **__Feature Description__** 11 | Describe what the feature is intended to accomplish & why it's important 12 | 13 | **__Major User Stories/tasks__** 14 | - [ ] User Story or Task #1 15 | - [ ] User Story or Task #2 16 | - [ ] Additional User Stories or Tasks as necessary 17 | 18 | **__Additional Considerations__** 19 | Include anything else that may be helpful. For example, links to external resources. 20 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/user-story-template.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: User Story template 3 | about: User Stories are features supporting user requirements that can be completed 4 | in a single sprint 5 | title: '' 6 | labels: user_story 7 | assignees: '' 8 | 9 | --- 10 | 11 | **__User Story Description__** 12 | As a [role] 13 | I want to [action to be performed] 14 | So I can [result to be achieved] 15 | 16 | **__Steps to Follow (optional)__** 17 | - [ ] Step #1 18 | - [ ] Step #2 19 | - [ ] Additional steps as necessary 20 | 21 | **__Additional Considerations__** 22 | Any supplemental information including unresolved questions, links to external resources, screenshots, etc. 23 | -------------------------------------------------------------------------------- /docs/team_project_ideas.md: -------------------------------------------------------------------------------- 1 | # Team Project Ideas 2 | 3 | Update this with 1-2 ideas per team member for what your teams app project. 4 | 5 | To set this up add each teammates name in the `teammate name` column. Everyone 6 | on the team should then updated it, adding 1-2 ideas along with a short 7 | description. Keep in mind that the descriptions should be only 1-3 short 8 | sentences. 9 | 10 | Each team member should Place an 'X' under their name to vote for the ideas 11 | you like the best. 12 | 13 | | Project Idea | Description | teammate name | teammate name | teammate name | teammate name | teammate name | teammate name | 14 | | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | 15 | | First idea | Description | | | | | | | 16 | | Second idea | Description | | | | | | | 17 | | ... | Description | | | | | | | 18 | | Last idea | Description | | | | | | | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug-report-template.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report template 3 | about: Create a report to help us improve 4 | title: '' 5 | labels: bug 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Describe the problem** 11 | A clear and concise description of what the bug is. 12 | 13 | **Actual behavior** 14 | A clear and concise description of what you experienced. 15 | 16 | **Expected behavior** 17 | A clear and concise description of what you expected to happen. 18 | 19 | **To Reproduce** 20 | Steps to reproduce the behavior: 21 | 1. Go to '...' 22 | 2. Click on '....' 23 | 3. Scroll down to '....' 24 | 4. See error 25 | 26 | **Screenshots** 27 | If applicable, add screenshots or gifs to help explain your problem. 28 | 29 | **Your Environment:** 30 | - Your browser & its version 31 | - Any other software that may impact this issue 32 | 33 | **Additional Information** 34 | Add any other context about the problem here. 35 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # voyage-tasks 2 | 3 | Your project's `readme` is as important to success as your code. For 4 | this reason you should put as much care into its creation and maintenance 5 | as you would any other component of the application. 6 | 7 | If you are unsure of what should go into the `readme` let this article, 8 | written by an experienced Chingu, be your starting point - 9 | [Keys to a well written README](https://tinyurl.com/yk3wubft). 10 | 11 | And before we go there's "one more thing"! Once you decide what to include 12 | in your `readme` feel free to replace the text we've provided here. 13 | 14 | > Own it & Make it your Own! 15 | 16 | ## Team Documents 17 | 18 | You may find these helpful as you work together to organize your project. 19 | 20 | - [Team Project Ideas](./docs/team_project_ideas.md) 21 | - [Team Decision Log](./docs/team_decision_log.md) 22 | 23 | Meeting Agenda templates (located in the `/docs` directory in this repo): 24 | 25 | - Meeting - Voyage Kickoff --> ./docs/meeting-voyage_kickoff.docx 26 | - Meeting - App Vision & Feature Planning --> ./docs/meeting-vision_and_feature_planning.docx 27 | - Meeting - Sprint Retrospective, Review, and Planning --> ./docs/meeting-sprint_retrospective_review_and_planning.docx 28 | - Meeting - Sprint Open Topic Session --> ./docs/meeting-sprint_open_topic_session.docx 29 | 30 | ## Our Team 31 | 32 | Everyone on your team should add their name along with a link to their GitHub 33 | & optionally their LinkedIn profiles below. Do this in Sprint #1 to validate 34 | your repo access and to practice PR'ing with your team *before* you start 35 | coding! 36 | 37 | - Teammate name #1: [GitHub](https://github.com/ghaccountname) / [LinkedIn](https://linkedin.com/in/liaccountname) 38 | - Teammate name #2: [GitHub](https://github.com/ghaccountname) / [LinkedIn](https://linkedin.com/in/liaccountname) 39 | 40 | ... 41 | - Teammate name #n: [GitHub](https://github.com/ghaccountname) / [LinkedIn](https://linkedin.com/in/liaccountname) -------------------------------------------------------------------------------- /docs/team_decision_log.md: -------------------------------------------------------------------------------- 1 | # Team Decision Log 2 | 3 | Update this with key decisions your team makes that you need to make...and 4 | remember. The entries in this table are only examples. You may add, change, or 5 | delete these based on the needs of your team. 6 | 7 | To set this up add each teammates name in the `teammate name` column. Each 8 | team member should Place an 'X' under their name to vote for the ideas 9 | you like the best. 10 | 11 | | No. | Question/Option | Teammate name | Teammate name | Teammate name | Teammate name | Teammate name | Teammate name | 12 | | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | 13 | | 1 | Team meeting schedule | | | | | | | 14 | | | - Sprint Planning Sunday@9:00 a.m. CST | | | | | | | 15 | | | - Knowledge Xfer as needed | | | | | | | 16 | | | - Working Session Thursday@4:00 p.m. CST | | | | | | | 17 | | 2 | Project Backlog Tool | | | | | | | 18 | | | - Notion | | | | | | | 19 | | | - Jira | | | | | | | 20 | | 3 | Technical Stack (vote by adding your pref. in the cell under your name) | | | | | | | 21 | | | - BE Language | | | | | | | 22 | | | - FE Language | | | | | | | 23 | | | - FE Framework | | | | | | | 24 | | | - ML Framework | | | | | | | 25 | | | - Visualization/Graphics package (if required, e.g. D3, Nivo, etc.) | | | | | | | 26 | | 4 | Where to host the app? | | | | | | | 27 | | | - Heroku (suitable for FE, BE, & Postgres) | | | | | | | 28 | | | - Netlify (suitable only for FE) | | | | | | | 29 | | | - Vercel (suitable only for FE) | | | | | | | 30 | | | - Mongo Atlas (suitable only for MongoDB) | | | | | | | 31 | | 5 | BE/FE repos organization | | | | | | | 32 | | | - Separate GitHub repos for each | | | | | | | 33 | | | - Single GitHub repo for both | | | | | | | 34 | | 6 | Wireframing tool | | | | | | | 35 | | | - Paper & pencil | | | | | | | 36 | | | - Adobe XD | | | | | | | 37 | | | - Balsamiq | | | | | | | 38 | | | - Figma | | | | | | | 39 | | 7 | Who works in which part of the app? | | | | | | | 40 | | | - BE (not applicable for Tier 1 teams) | | | | | | | 41 | | | - FE | | | | | | | 42 | | 8 | ... | | | | | | | 43 | | n | ... | | | | | | | --------------------------------------------------------------------------------