#  Mobile Computing
## Pre-Emptive Agile & Team Working Contract

**Team Name / Project Name:** ____________________________________

**Date:** ________________________

**Team Members Present:**
1. ____________________________________ 
2. ____________________________________ 
3. ____________________________________
4. ____________________________________

---

### Part 1: Anti-Pattern Diagnosis & Risk Assessment

#### Step 1: Card Sorting
Review the Agile Anti-Pattern cards provided to your team. Discuss how each scenario might play out in your mobile computing project, then categorize them into three piles:
* **High Risk:** High likelihood of happening / severe impact on our team.
* **Low Risk:** Low likelihood of happening / easy to manage.
* **Unsure:** Need clarification or unsure of practical impact.

#### Step 2: Deep Dive into Top 2 "High Risk" Anti-Patterns
Select your team's two highest-risk anti-patterns and complete the diagnosis below.

##### Anti-Pattern #1: _________________________________________________
* **What specific Agile value or principle does this violate?**
  ____________________________________________________________________________________________________
* **What are 2 early warning signs that our team is falling into this trap?**
  1. ________________________________________________________________________________________________
  2. ________________________________________________________________________________________________

##### Anti-Pattern #2: _________________________________________________
* **What specific Agile value or principle does this violate?**
  ____________________________________________________________________________________________________
* **What are 2 early warning signs that our team is falling into this trap?**
  1. ________________________________________________________________________________________________
  2. ________________________________________________________________________________________________

---

### Part 2: Constructing the Agile Team Contract

Use your anti-pattern diagnosis and team discussion to draft your team's working agreements below. Be specific and realistic.

#### Section 1: Anti-Pattern Shields
*Draft explicit rules to prevent or resolve the two high-risk anti-patterns you identified above.*

* **Rule to Prevent Anti-Pattern #1:**
  ____________________________________________________________________________________________________
  ____________________________________________________________________________________________________

* **Rule to Prevent Anti-Pattern #2:**
  ____________________________________________________________________________________________________
  ____________________________________________________________________________________________________

---

#### Section 2: Communication & Sprint Cadence
*Establish how your team will stay aligned throughout the term.*

* **Sprint Cycle Length:** [  ] 1 Week    [  ] 2 Weeks    [  ] Other: __________________
* **Daily Sync / Standup Plan:**
  * **Format:** [  ] Async via Slack/Discord    [  ] Synchronous (In-person / Zoom)
  * **Timing / Frequency:** __________________________________________________________________________
  * **The 3 Key Questions:** (1) What was completed? (2) What is next? (3) Any blockers?
* **Unblocking Protocol:** If a team member is stuck for more than ________ hours, they agree to post in channel / contact: ____________________________________________________________________________

---

#### Section 3: Technical Definition of Ready (DoR)
*What must be true BEFORE a team member begins working on a user story or task card? (Check all that apply & fill in specifics).*

* [  ] Card has clear User Acceptance Criteria defined.
* [  ] Mobile UI/UX screen wireframe or sketch is attached (if applicable).
* [  ] API schema or endpoint contract is agreed upon (if full-stack/mobile API).
* [  ] Estimated effort (Story Points or relative size) is agreed upon by team.
* [  ] Other: ______________________________________________________________________________________

---

#### Section 4: Technical Definition of Done (DoD)
*What must be completed BEFORE a task card is moved to "Done" and code is merged into `main`?*

* [  ] Code builds and executes cleanly on device / emulator without crashing.
* [  ] Feature tested across key conditions (e.g., offline mode, screen rotation, light/dark mode).
* [  ] Code passes linting/formatting standards and contains no hardcoded credentials.
* [  ] Peer Code Review completed and approved by at least ________ teammate(s).
* [  ] Pull Request (PR) merged to `main` branch with no unresolved merge conflicts.
* [  ] Other: ______________________________________________________________________________________

---

### Part 3: Team Commitment & Sign-Off 

By signing below, all team members agree to uphold these working standards. If a team member violates an agreement, the team agrees to address it openly and constructively during the next Sprint Retrospective.

| Member Name (Print) | Signature / Initial | Date |
| :--- | :--- | :--- |
| 1. _________________________________ | _________________________________ | ____________ |
| 2. _________________________________ | _________________________________ | ____________ |
| 3. _________________________________ | _________________________________ | ____________ |
| 4. _________________________________ | _________________________________ | ____________ |

---

### Debrief Question (For In-Class Discussion)
*Which agreement on this contract do you anticipate will be the hardest to enforce, and why?*
________________________________________________________________________________________________________
________________________________________________________________________________________________________






*Disclaimer: AI assistance was used in the preparation of this material.*