Update README.md

group-norms/README.md

@@ -46,29 +46,15 @@ Be sure to find your voice on your team.
 
 ### Continuous Learning
 
-Stay open-minded, accept feedback and constructive criticism, apply what you are learning and be kind and thoughtful as you give feedback to others
+Stay open-minded, accept feedback and constructive criticism, apply what you are learning and be kind and thoughtful as you give feedback to others.
 
 ### Effective Work Practices
 
 In the upcoming lessons we will go into greater depth about how to work effectively as a software engineering team. Each team and their work will likely have somewhat different best practices based on the type of work and goals they have.
 
 ## Getting Started
 
-The purpose of today is to
-
-- Pick an app idea
-- Do a quick 5 minute check-in with an instructor to approve your app idea (your instructor will help you navigate if your idea is too similar to other group(s))
-- Create a positive work culture by planning your group work and having open communication
-
-### Picking an App Idea
-
-Earlier, every member of your team ideated and submitted a minimum of two ideas for an app. Everyone should now present one app idea and then discuss as a group, which idea is the most exciting for everyone to want to work on together.
-
-Remember, unused Capstone ideas can always become personal projects.
-
-You should choose a name (it is ok to change it later) and be able to summarize your app in 2-3 sentences.
-
-You will do a quick check-in with your instructor to make sure you have the green light on your app idea and to continue working.
+The purpose of today is to create a positive work culture by planning your group work and having open communication.
 
 ### Working in Groups
 
@@ -78,9 +64,9 @@ What are your takeaways?
 
 ### Creating Group Norms
 
-Team norms are a set of rules that shape team member's interactions. These are clear agreed-upon behavior, communication, and understanding expectations of each other. This will also help you assign tasks when building your app.
+Group norms are a set of rules that shape team member's interactions. These are clear agreed-upon behavior, communication, and understanding expectations of each other. This will also help you assign tasks when building your app.
 
-Use this [worksheet to help establish your team norms](https://www.ccl.org/articles/leading-effectively-articles/the-real-world-guide-to-team-norms/)
+Use this [worksheet to help establish your team norms](https://www.ccl.org/articles/leading-effectively-articles/the-real-world-guide-to-team-norms/).
 
 Here is a summary, in case the link becomes broken in the future
 
@@ -96,11 +82,13 @@ Here is a summary, in case the link becomes broken in the future
 1. Discuss which ones can the team support and adhere to
 1. Flag any concerns or challenges (see below)
 1. Discuss how to deal with a team member who does not follow norms (see below)
-1. Someone else should volunteer to take the list and create a `must do` list - this list should be shared with your whole team and your instructor. This are the norms your teams should now follow for the project.
+1. Someone else should volunteer to take the list and create a `must do` list - this list should be shared with your whole team and your instructor. 
+
+This are the norms your teams should now follow for the project.
 
 ### Challenges
 
-All of you are in this program part-time with different external obligations. It's really important to set norms around this. A great way to frame is it for your behavioral interview: One of the biggest challenges will be everyone's different schedules. How did you handle it? How did you make it work? Think of the best ways your group can deal with this.
+All of you are in this program with different external obligations. It's really important to set norms around this. How do you handle it? How do you make it work? Think of the best ways your group can deal with this.
 
 How do you want communication to happen? Over slack? Over text message? What are "normal work hours"? What are the hours that if someone reaches out they should not expect an immediate answer because it is "after hours". How quickly do you expect everyone to respond during "normal work hours"? If someone has another obligation (or takes a lunch break etc.) that will make them unavailable during "normal work hours" - how should they let the team know?
 
@@ -114,46 +102,35 @@ Understanding that everyone is expected to work on the front-end and back-end of
 
 There are many ways to handle conflicts, but here are some dos and don'ts to get you started as you make your own team norms.
 
-#### Don'ts
+#### Don't
 
-- Assume the worst. If someone is unexpectedly offline, first ask if they are ok. Take time to understand the situation first
-- Go over everyone's head. If you have a problem with someone your first step should not be to go to the instructor, start with your team first
-- Assume that people know what is bothering you. Be sure to let people know, early and follow up if the issue is not resolved or comes up again
-- Assume it will get better without talking about it
-- Disappear/stop communicating. If you are not comfortable talking in person, try zoom, if not zoom, try the phone, if not the phone, try slack, if not slack, try email.
+- Assume the worst. If someone is unexpectedly offline, first ask if they are OK. Take time to understand the situation first.
+- Go over everyone's head. If you have a problem with someone your first step should not be to go to the instructor, start with your team first.
+- Assume that people know what is bothering you. Be sure to let people know and follow up if the issue is not resolved or comes up again.
+- Assume it will get better without talking about it.
+- Disappear/stop communicating. If you are not comfortable talking in person, try zoom, if not zoom, try the phone, if not the phone, try Slack, if not Slack, try email.
 
 #### Do
 
-- Keep communication open
+- Keep communication open.
 
-  - Always talk to the person you are having an issue with
-    - If you are not sure what to do, talk it through with a friend or a peer first, privately, use the session to develop a plan. Do not escalate unless you have already made attempts at fixing the situation yourself
+  - Always talk to the person you are having an issue with.
+    - If you are not sure what to do, talk it through with a friend or a peer first, privately, use the session to develop a plan. Do not escalate unless you have already made attempts at fixing the situation yourself.
 
-- Try to resolve the conflict yourself/within the team first
-- Try to be empathetic
-- Listen before giving advice
-- Reach out to an instructor if you can't resolve something, on your own or if the issue is bigger than what your group can solve (someone has a family emergency that will take them away from a project for a while).
+- Try to resolve the conflict yourself or within the team first.
+- Try to be empathetic.
+- Listen before giving advice.
+- Reach out to an instructor if you can't resolve something, on your own or if the issue is bigger than what your group can solve (e.g., someone has a family emergency that will take them away from a project for a while).
 
 Remember, your instructor wants to help you succeed and is here to support you. It's not about getting people in trouble, it's about learning to work on a team in a professional way.
 
 ## Checklist
 
-- [ ] Pick an app idea
-- [ ] Choose an app name (can be changed later)
-- [ ] Write a 2-3 sentence summary of the app idea
-- [ ] 5 minute check-in with instructor
 - [ ] Read and discuss Working in Groups
 - [ ] Create group norms (a document you will share with your team and instructor)
 - [ ] Learned everyone's work hours
 - [ ] Discuss best methods of communication
 - [ ] Determine initial work cadence (can be changed later)
-- [ ] Create user stories
-- [ ] Create wireframes
-- [ ] Create ERDs
-
-## Have Time Left Over?
-
-Firstly, keep refining and building your idea. If you are not ready to build your user stories, wireframes and ERDs, take the time to socialize and get to know each other better. A core part of team building is getting to know your teammates, understanding what they like and don't like. Having a good sense of who they are will help you work with them better.
 
 ## References