- Mohammad Ashour
- Rawan Abu-Yasein
- Mohammad Momani
- Manar Abdelkarim
- Clone the app -->
git clone git@github.com:Team-Tech2021/kuro-space.git - Enter the app Directory -->
cd kuro-space - Install Dependencies -->
yarn install - Run development server -->
yarn dev - Deploy on Vercel --> Deploy Link
- Our group will meet online and talk about it and we will vote , we will respect each other’s opinions and only talk in a respectable manner.
What will your team do if one person is taking over the project and not letting the other members contribute?
- before we start we will divide the project into tasks and each one of us will take his task based on each one knowledge and every one will push his own code to Github.
How will you approach each other and the challenges of the project knowing that it is impossible for all members to be at the exact same place in understanding and skill level?
- We will divide the tasks based on the preference of the team members so that the team member will be enjoying doing their task. In the dividing process We will make sure that every member will gain new knowledge.
- We can discuss why this happened also the leader will keep up with the team. First we will have to know their reasons and if their reason is acceptable we will review our backup plan and if it was not acceptable the team leader will contact the instructor as last solution.
- We can discuss the different opinions and thoughts and share them with all of the group members and then take a vote on what to do next.
- When we fail to find a common solution together and the votes are equal and the problem is critical to the workflow we will let our instructor/TA help us with it.
- Manar: flexible , can help others in my free time and accept project changes.
- Rawan: quick learning ability , ability to process information and make connections on the fly and find different resources for the team.
- Mohammad Momani: Curiosity, able to pick up any Library and start using it with minimal ramp up time.
- Mohammad Ashour: Critical thinking and Puzzle-solver
- learn about other technologies needed in building a complete product, learn how to write code better and understand concepts such as design patterns and object-oriented programming.
Knowing that every person in your team needs to understand all aspects of the project, how do you plan to approach the day-to-day work?
- We will have a daily meetings, these meetings allow the team to review the previous day’s work, discuss the current day’s tasks, and each person explains the progress made and quickly explains the code written for the rest of the members of the group .
- All of our project except any file in .env
- We are all owners on the repo
- every feature will have its own branch and the team leader will merge the pull request
- 1
- team leader
- after every feature
- when every new feature is complete ,has no bugs and follow our github rules the and updated with main the request of merging will be in slack after sending pull request
- We agreed on 9am to 5pm work time from Sunday to Wednesday.
- We created a Slack group and we are using Discord and Zoom to meet
- we will have a break in the original break time on work days (12:00pm)
- we will extend work hours and ask for assistance
- any time ,we will use slack as our main communicate platform and we will meet at zoom at 7pm if needed
- We welcome all the different opinions and we don’t judge anyone, we are all here because we like doing the same thing which is web development. We support each other not just to finish the goal of this project but also because we are teammates. We will make sure to hear everyone opinion and encourage the members to participate
How will you ensure that you are creating a safe environment where everyone feels comfortable speaking up?
- When anyone speaks up about anything we will always listen and not interrupt also we will never make fun of them. We will be nice to each other and always communicate in a respectable manner
- using Trello we will create tasks and give each task deadline
- Trello : trello




