|
1 | | -<!-- this template is for inspiration, feel free to change it however you like! --> |
| 1 | +# 🧱 Constraints |
2 | 2 |
|
3 | | -# Constraints |
| 3 | +Some boundaries around our project — these constraints helpus |
| 4 | +stay realistic, focused, and creative. |
4 | 5 |
|
5 | | -Some boundaries around our project. |
| 6 | +--- |
6 | 7 |
|
7 | | -## External |
| 8 | +## 🌍 External Constraints |
8 | 9 |
|
9 | | -<!-- |
10 | | - constraints coming from the outside that your team has no control over: |
11 | | - - project deadlines |
12 | | - - number of unit tests required to pass a code review |
13 | | - - technologies (sometimes a client will tell you what to use) |
14 | | - - power or connectivity |
15 | | - - ... |
16 | | ---> |
| 10 | +_Constraints outside of our control._ |
17 | 11 |
|
18 | | -## Internal: Involuntary |
| 12 | +- We have a fixed timeline (project must be completed by August 25). |
| 13 | +- Our project scope must remain within a data science context |
| 14 | +(no full-stack apps or hardware prototypes). |
| 15 | +- We may only use public or ethically sourced data. |
| 16 | +- All deliverables must follow the MIT Emerging Talent milestone structure and deadlines. |
| 17 | +- Group members are spread across different time zones and schedules. |
19 | 18 |
|
20 | | -<!-- |
21 | | - constraints that come from within your team, and you have no control over: |
22 | | - - each of your individual skill levels |
23 | | - - amount of time available to work on the project |
24 | | ---> |
| 19 | +--- |
25 | 20 |
|
26 | | -## Internal: Voluntary |
| 21 | +## ⛓️ Internal Constraints – Involuntary |
27 | 22 |
|
28 | | -<!-- |
29 | | - constraints that your team decided on to help scope the project. they may include: |
30 | | - - coding style & conventions |
31 | | - - agree on a code review checklist for the project repository |
32 | | - - the number of hours you want to spend working |
33 | | - - only using the colors black and white |
34 | | ---> |
| 23 | +_Constraints we didn’t choose, but still need to work with._ |
| 24 | + |
| 25 | +- Team members have different levels of technical experience with data analysis |
| 26 | +and Git. |
| 27 | +- Internet stability and device access may vary for team members. |
| 28 | +- Limited access to proprietary datasets or paid tools/services. |
| 29 | +- English is not the first language for some members, which may |
| 30 | +affect communication pace or clarity. |
| 31 | + |
| 32 | +--- |
| 33 | + |
| 34 | +## 🎯 Internal Constraints – Voluntary |
| 35 | + |
| 36 | +_Constraints we are choosing to adopt to help us focus and grow._ |
| 37 | + |
| 38 | +- We will not aim to build a full product; instead, we’ll focus on strong research, |
| 39 | +analysis, and communication artifacts. |
| 40 | +- We will set a soft deadline of 48 hours before each milestone |
| 41 | +to allow for reviews and backups. |
| 42 | +- We will only include tools and code we understand and can explain clearly. |
| 43 | +- We will prioritize clarity over complexity in both data and code. |
| 44 | + |
| 45 | +📨 Communication |
| 46 | + |
| 47 | +- Communication will primarily be asynchronous through Slack for quick updates |
| 48 | +and GitHub for task tracking and collaboration. We’ll manage our workflow using |
| 49 | +GitHub Issues and Project Boards.💬 |
| 50 | + |
| 51 | +🕒 Scheduling and Deadlines |
| 52 | + |
| 53 | +- Each team member is encouraged to dedicate consistent working hours throughout |
| 54 | +the week. This helps ensure steady progress, timely milestone delivery, |
| 55 | +and a healthy balance between productivity and well-being. |
| 56 | + |
| 57 | +--- |
| 58 | + |
| 59 | +> Defining clear constraints helps us commit to achievable goals and encourages |
| 60 | +> creative, focused work. |
| 61 | +> |
0 commit comments