added more examples

instructional_team/markdown_slides/02_teamwork_and_presenting.md

@@ -78,14 +78,15 @@ ___Develop a program that uses data creatively to solve a problem or provide ins
 ## FAQs from yesterday:
 
 * **How do you submit your videos?**
-    * We will provide links to a Google Drive folder for each team. Each team member will upload their video to that folder. Make sure your name is in the file name that you upload!
+    * The README should include links to each team member's video.
+    * The location where you host it is up to you, but we strongly recommend posting your video to your YouTube account (or unlisted). That way, potential future employers will be able to access it along with your project.
 
 ---
 
 ## FAQs from yesterday:
 
 * **We have an idea but someone else has already completed a similar analysis. Can we still use that idea?**
-    * It may be difficult to find a problem that nobody has worked on already, but you should still bring something new to your solution to extend the analysis. This is also about being creative!
+    * It may be difficult to find a problem that nobody has worked on already, but you should still bring something new to your solution. This is about being creative!
     * If your project is motivated by work that is already public, cite this in your README file.
     * If your goal is to improve on work that has already been done, state this explicitly in your README. Discuss how you want to improve the analysis.
 
@@ -100,7 +101,7 @@ ___Develop a program that uses data creatively to solve a problem or provide ins
 
 ## FAQs from yesterday:
 
-* **Are there examples to refer to?**
+* **Are there example projects to refer to?**
     * We will not provide any specific examples since we want you to develop your idea on your own, and showcase your creativity.
     * Some example of how regression can be applied in business:
         * [simplilearn](https://www.simplilearn.com/tutorials/excel-tutorial/regression-analysis#)
@@ -129,7 +130,7 @@ ___Develop a program that uses data creatively to solve a problem or provide ins
 * **What are the exact steps to set up the GitHub repository for your team?**
 
     6. Each team member must submit at least one of these PRs.
-    7. Each PR must be reviewed by at least one other team member. We recommend assigning different reviewers to each PR, as one of the requirements is also that each team member review at least one PR.
+    7. Each PR must be reviewed by at least one other team member. We recommend assigning different reviewers to each PR, as one of the requirements is that each team member review at least one PR.
     8. When the project is completed, the `team-project-1` branch should be the final working version.
     9. The project is submitted by submitting a PR to merge the `team-project-1` branch into the `main` branch of your **forked** repository. Any team member can submit this.
 
@@ -142,33 +143,71 @@ ___Develop a program that uses data creatively to solve a problem or provide ins
 2. Rules of engagement and strategies for effective teamwork.
 
 ---
-
 # Presenting your work
+---
+
+## Presenting your work
+
+1. Understand your target audience.
+2. Clearly articulate the takeaways.
+3. Highlight the value added.
 
 ---
 
 ## 1. Understand your target audience
 
-* What knowledge do they have about your project?
+* What are their goals? What is their jurisdiction?
+
+* Determine which details about your project they *need* to know; consider what they know about it already.
+
+--- 
 
-* Provide the necessary context.
+## 1. Understand your target audience
 
-* Reinforce the insights that __they__ can act on.
+**Example:** We are presenting our analysis of office space usage to the department heads who assign seating. They are not technical, but understand the company is paying more than it needs to for real estate. Furthermore, they have their own prior perspectives on office space utilization.
 
 --- 
 
 ## 1. Understand your target audience
 
-**Example:** We are presenting our analysis of office space usage to the department heads who assign seating. They are not technical, but understand the problem and are looking for a solution. Furthermore, they have their own prior perspectives on office space utilization.
+**Example:** We are presenting our analysis of office space usage to the department heads who **assign seating**. They are not technical, but understand **the company is paying more than it needs to for real estate**. Furthermore, they have their own prior perspectives on office space utilization.
+
+* **What are their goals and jurisdiction?**
+    * They want to make the most efficient use out of office space, and minimize real estate costs where possible.
+    * They are able to change how team seating is assigned.
+
+--- 
+
+## 1. Understand your target audience
+
+**Example:** We are presenting our analysis of office space usage to the department heads who assign seating. **They are not technical**, but understand the company is paying more than it needs to for real estate. Furthermore, they have their own prior perspectives on office space utilization.
+
+* **Determine which details about your project they *need* to know; consider what they know about it already.**
+    * They understand that you are investigating ways to decrease real estate costs.
+
+---
+
+
+* **Determine which details about your project they *need* to know; consider what they know about it already.**
+    * They **should** know the factors that you are considering.
+        * Office usage broken down by a variety of factors (team, day of the week, season, etc...).
+        * Amount of assigned seating.
+        * Amount of flexible seating.
+        * Time spend in meetings (by individual and team).
+    * They **should** know your data sources.
+    * They **do not** need to know how you are cleaning your data, what libraries you are using, or your statistical techniques.
+        * A technical audience (eg. software architect reviewing your work) would want to know these details.
 
 --- 
 
 ## 2. Clearly articulate the takeaways
 
-* Make sure your audience understands the most important information.
+* Ensure that your audience understands the most important information.
 
 * Don't add unnecessary detail, but be prepared to speak in depth if asked.
 
+* Highlight the actionable insights.
+
 --- 
 
 ## 2. Clearly articulate the takeaways
@@ -188,7 +227,29 @@ ___Develop a program that uses data creatively to solve a problem or provide ins
 
 ## 2. Clearly articulate the takeaways
 
-**Example:** Our company could reduce real estate overhead, while maintaining productivity and employee comfort, if we removed the assigned seating for 10% of teams but updated 25% of our office space to be flexible seating.
+**Example:** Our company could reduce real estate overhead, without restricting the ability of employees to work where they want to (based on current office usage), if we removed the assigned seating for 10% of teams but updated 25% of our office space to be flexible seating.
+
+---
+
+## 2. Clearly articulate the takeaways
+
+**Example:** Our company could **reduce real estate overhead**, without restricting the ability of employees to **work where they want** (based on current office usage), if we **removed the assigned seating for 10% of teams** but **updated 25% of our office space** to be flexible seating.
+
+* **Ensure that your audience understands the most important information**.
+    * Align your takeaways to your audience's goals.
+    * Be specific.
+    * ***Communicate the actionable insights.***
+
+---
+
+## 2. Clearly articulate the takeaways
+
+**Example:** Our company could **reduce real estate overhead**, without restricting the ability of employees to **work where they want** (based on current office usage), if we **removed the assigned seating for 10% of teams** but **updated 25% of our office space** to be flexible seating.
+
+* **Don't add unnecessary detail, but be prepared to speak in depth if asked.**
+    * Understand the rationale behind the numbers and be ready to justify your logic.
+    * Eg. there may be no need to list specific floors or sections that assigned seating should be removed from at this time, but you should have some ideas.
+
 
 ---
 
@@ -205,12 +266,24 @@ ___Develop a program that uses data creatively to solve a problem or provide ins
 **Example:** Updating the office spaces would add 5% to our real estate costs over the next year, but would save 10% per year once the new seating is implemented.
 
 ---
+
+## 3. Highlight the value added
+
+**Example:** Updating the office spaces **would add 5% to our real estate costs** over the next year, but **would save 10% per year** once the new seating is implemented.
+
+* **Quantify as much as possible.**
+    * Provide specific % or $ amounts if able, along with any uncertainties.
+* **Indicate how your work improves over previous work or the status quo.**
+    * This will incentivize the action that you are recommending.
+
+---
+
 # Rules of engagement and strategies for effective teamwork
 ---
 
-### Think about: how did yesterday go?
+### How did yesterday go?
 
-Do you think your team functioned well?
+Do you think your team was organized well?
 
 What could be improved?
 
@@ -224,23 +297,25 @@ Would the others on your team agree with you?
 
 1. Have strong communication.
 
-2. Have a clear undertanding of everyone's role on the team.
+2. Have a clear undertanding of everyone's role on the team and work collaboratively towards a common goal.
 
-3. Work collaboratively towards a common goal.
+3. Always understand what needs to be done, what is in progress, and what has been done.
 
 ---
 
 ## Rules of engagement
 
-* Every time will land on slight different rules of engagement!
+* Every team may land on slight different rules of engagement!
+
+* The key is awareness of what works and what doesn't, and adjust accordingly.
 
-* The key is to be aware of what works and what doesn't, and adjust accordingly.
+* Iteration is good!
 
 ---
 
 ## Rules of engagement
 
-* However, **rules must be explicit**.
+* **Rules must be explicit**.
 
 * Miscommunication happens when rules are left up to individual interpretation.
 
@@ -255,6 +330,25 @@ Would the others on your team agree with you?
 
 2. **Respectful and honest communication**. For discussions to be productive, team members must feel able to both speak their minds and discuss their mistakes without judgement.
 
+---
+
+1. **Feedback as a habit**. A feedback framework helps teams focus on improving processes instead of laying blame.
+
+* **Bad example:**
+    * Team members only communicate when something has gone wrong to figure out who made a mistake.
+* **Good example:**
+    * Your team schedules 10 minutes daily to discuss what went well, what didn't go well, and processes that can improve how the team works.
+
+---
+
+## Communication and feedback
+
+2. **Respectful and honest communication**. For discussions to be productive, team members must feel able to both speak their minds and discuss their mistakes without judgement.
+
+* **Bad example:**
+    * Teammate X gets angry at teammate Y because teammate Y introduced a bug in the code.
+* **Good example:**
+    * The team comes up with a solution to address the bug, and clarifies the level of testing required to make sure more bugs don't get introduced.
 
 ---
 
@@ -266,6 +360,28 @@ Would the others on your team agree with you?
 
 ---
 
+## A self-organizing team
+
+1. **Clear accountability and ownership of tasks**. Every action item should have someone assigned. Of course, the assigned person can change if workloads become unbalanced.
+
+* **Bad example:**
+    * We will get to this task later, so there is no need to assign it to someone now.
+* **Good example:**
+    * Team member X will own this task and should be able to work on it 2 days from now. If they hit any roadblocks, they will request help from the rest of the team.
+
+---
+
+## A self-organizing team
+
+2. **Be solution-oriented**. Instead of only presenting problems, try to always suggest a possible solution along with a problem.
+
+* **Bad example:**
+    * Data set 1 is at the province level and data set 2 is at the city level, so we can't join the data sets.
+* **Good example:**
+    * We need to decide whether to join all of our data at the province level by mapping city to province, or find a dataset that can provide city-level detail for data set 1.
+
+---
+
 ## Clear tracking of progress
 
 1. **Communication of roadblocks**. It is just as important to communicate roadblocks and failures as successes. The faster problems are identified, the faster they can be addressed.
@@ -274,13 +390,49 @@ Would the others on your team agree with you?
 
 3. **Documentation of work**. The level and type of documentation should be agree upon as a team, and included in the rules of engagement. Team members should be able to understand and continue each others' work.
 
+---
+
+## Clear tracking of progress
+
+1. **Communication of roadblocks**. It is just as important to communicate roadblocks and failures as successes. The faster problems are identified, the faster they can be addressed.
+
+* **Bad example:**
+    * Every team member says they are doing well with their tasks, even if they have problems. The project deadline passes and nobody is finished their work.
+* **Good example:**
+    * Team members communicate the progress they have made, and tasks they are struggling with. They get help from other team members where required.
 
 --- 
 
-## Prioritization
+## Clear tracking of progress
+
+2. **Track all of your tasks**. Tracking is necessary to objectively assess your progress as a team. The data-driven mindset applies here too!
+
+* **Bad example:**
+    * Team members all memorize their tasks and assume the other members have done so too.
+* **Good example:**
+    * Team members use a shared Jira board so everyone can see what the status of all tasks are.
+
+--- 
+
+## Clear tracking of progress
+
+3. **Documentation of work**. The level and type of documentation should be agree upon as a team, and included in the rules of engagement. Team members should be able to understand and continue each others' work.
+
+* **Bad example:**
+    * Team member X doesn't comment their code because they think it is obvious what the code does. Team member Y comments every line of code because they want to be detailed.
+* **Good example:**
+    * Team members all agree on the level of commenting that should be added to their code, and on the length of description required in pull requests.
+
+---
+
+# Prioritization
 
 Many different frameworks exist.
 
+---
+
+## Prioritization
+
 The **RICE** prioritization framework is an example, in which we try to quantify the:
 1. Reach of a project (how many people it will affect).
 2. The impact that it will have.