doc: add extension list

README.md

@@ -35,3 +35,7 @@ For more information, read [here](./scrum-agile/README.md).
 ## Commitlint, ESLint and Prettier
 
 Setup Commitlint, ESLint and Prettier for repository [here](./setup-coding-style/README.md)
+
+## Extension
+
+List of necessary extensions, see [here](./extension/README.md)

extension/README.md

@@ -0,0 +1,14 @@
+# Extension
+
+Download in your Visual Studio Code these list of extensions
+
+1. ESLint
+2. Prettier - Code formatter
+3. Code Spell Checker
+4. DotENV
+5. markdownlint
+6. shell-format
+7. Tailwind CSS IntelliSense
+8. ES7+ React/Redux/React-Native snippets
+9. GitLens — Git supercharged
+10. Markdown Preview Enhanced

scrum-agile/README.md

@@ -3,6 +3,7 @@
 <img src="https://github.com/gdsc-hcmut/working-process/assets/131350457/2b641f3f-7595-4b6d-9337-dfb5c67f203e" alt="scrum process" style="height:250px" />
 
 ## Definition
+
 - Scrum is an agile project management framework that helps teams structure and manage their work through a set of values, principles, and practices.
 - **Scrum vs Agile**: *scrum is a framework for getting work done, whereas agile is a philosophy.*
 
@@ -12,13 +13,15 @@ A scrum team needs three specific roles: product owner, scrum master, and the de
 
 1. **product owner**
 They are focused on understanding business, customer, and market requirements, then prioritizing the work to be done by the engineering team accordingly. Requirement:
+
 - Build and manage the product backlog.
 - Closely partner with the business and the team to ensure everyone understands the work items in the product backlog.
 - Give the team clear guidance on which features to deliver next.
 - Decide when to ship the product with a predisposition towards more frequent delivery.
 
 2. **scrum master**
 They coach teams, product owners, and the business on the scrum process, and look for ways to fine-tune their practice of it. Requirement:
+
 - deeply understands the work being done by the team and can help the team optimize their transparency and delivery flow.
 - schedules the needed resources (both human and logistical) for sprint planning, stand-up, sprint review, and the sprint retrospective.
 
@@ -32,6 +35,7 @@ The scrum team drives the plan for each sprint. They forecast how much work they
 1. **Product Backlog**: a To Do list maintained by the product owner.
 
 2. **Sprint Backlog**: list of items, selected by the Development team for implementation in the current sprint cycle.
+
 - Before each sprint, in the sprint planning meeting, the team chooses which items it will work on for the sprint from the product backlog.
 - A sprint backlog may be flexible and can evolve during a sprint, but the fundamental sprint goal can not be compromised.
 
@@ -42,6 +46,7 @@ The scrum team drives the plan for each sprint. They forecast how much work they
 1. **Organize the backlog**: This event is the responsibility of the product owner. He/She maintains this list using feedback from users and the development team to help prioritize and keep the list clean and ready to be worked on at any given time.
 
 2. **Sprint planning**: The work to be performed (scope) during the current sprint is planned during this meeting by the entire development team. Requirements:
+
 - Deciding the sprint goal.
 - Adding specific user stories from the product backlog to the sprint.
 - After meeting, every scrum member needs to be clear on what can be delivered in the sprint and how the increment can be delivered.
@@ -57,14 +62,17 @@ git push origin <tag_name>
 During sprint planning, team discuss which tasks should be done first and decide the **task point**, which estimate the difficult and how long the task can be done in the next sprint.
 
 Points:
+
 - `1` simple and well-understood, 1-2 hours
+- `2` still well-understood but require more time, 6-10 hours
 - `3` more involved but still straightforward, 1 day
 - `5` 2-3 days
 - `8` up to 1 week
 
 *Notes: Team should consider other activities during the sprint time, such as club events, school schedules, ...*
 
 5. **Stand up**: This is a frequently super-short meeting that happens at the same time and a place to keep it simple. During this meeting, these flow should be focused:
+
 - **Report the previous task**: If there is any task on the previous meeting, it should be done before discussing the new one.
 - **Solve the difficulty**: If any difficulty happens, we should exchange with other members in team to find the best solution.
 - **Plan for the next task**: the leader creates task by Issues and assigns to other members.
@@ -74,7 +82,8 @@ Suggested: 3 meetings/week, 2 days apart each time.
 6. **Retrospective**: meetings after a time-boxed period of work is complete. It is an opportunity for agile development teams to reflect on past work together and identify ways to improve.
 
 Suggested questions:
+
 - What went well during the last sprint?
-- What didn’t go well? 
-- What did we learn? 
-- What should we do differently next time?
+- What didn’t go well?
+- What did we learn?
+- What should we do differently next time?