Skip to content

Commit e49a9b7

Browse files
Merge pull request #5 from MIT-Emerging-Talent/Caesar-Constrains-Update
Caesar constrains update
2 parents 07725e6 + 11b374f commit e49a9b7

File tree

1 file changed

+25
-23
lines changed

1 file changed

+25
-23
lines changed

collaboration/constraints.md

Lines changed: 25 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,34 +1,36 @@
1-
<!-- this template is for inspiration, feel free to change it however you like! -->
2-
31
# Constraints
42

5-
Some boundaries around our project.
3+
Some boundaries around our project. This document outlines both external
4+
constraints (factors beyond our control) and internal constraints
5+
(team-specific challenges, both involuntary and voluntary) to
6+
provide a clear framework for delivering a successful project.
67

78
## External
89

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+
External constraints are limitations imposed by factors outside the team’s
11+
direct control.
12+
13+
- **Internet Connectivity**: Unreliable or slow internet access can disrupt
14+
communication, research, and collaborative workflows, affecting project progress.
1715

1816
## Internal: Involuntary
1917

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-
-->
18+
Internal involuntary constraints arise from unavoidable limitations within
19+
the team or organization.
20+
21+
- **Varying Levels in Programming**: The team has varying levels of
22+
programming expertise. Prioritizing tasks that align with team
23+
members’ learning goals or strengths to foster growth while
24+
ensuring quality output.
25+
- **Time Availability**: Team members may have limited hours
26+
to dedicate to the project due to fixed schedules, personal commitments,
27+
or overlapping responsibilities.
2528

2629
## Internal: Voluntary
2730

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-
-->
31+
Voluntary internal constraints are self-imposed limitations set by the team
32+
to guide the project and ensure quality, efficiency,
33+
and alignment with goals.
34+
35+
- **Repository Collaboration**: All members will contribute to a shared GitHub
36+
repository, promoting teamwork and collective ownership of the project.

0 commit comments

Comments
 (0)