I Can Fix That

To​​: Dr. Bruce

From: ​Team ​I Can Fix That​ (Blank, 2003)
Date:​​ 25 September 2018
Subject:​​ iFixit Team Charter

Team Members
Project Manager – Aliyah Malapit
Research Manager – Michael Gonzalez
Research Manager – Terrinda Alonzo
Editing Manager – Haleigh St. Paul

Mission
Team ​I Can Fix That​’s objective is to deconstruct and reassemble an ASUS notebook, PC model
X200M, in order to compose an effective and straightforward guideline for iFixit.com and its
diverse group of users. In our guide, we will include clear step-by-step instructions along with
corresponding photos. We hope our guide will help ASUS users to not only troubleshoot issues
they may have with their laptop by removing obsolete or damaged parts and replacing them with
functioning parts, but also reassemble their computers for continued and improved use.

Expectations
In order to be a successful team, each member will be expected to adhere to pre-established
outcomes. Each team member will be required to complete assignments by due dates. When
working or meeting together, everyone must participate equally according to the assignments
listed on the charter timesheet. Team members are encouraged to ask for help when required.
Communication will be established via text message and email with responses expected within a
24 hours. Since the equipment is a vital part of the project, all members will be responsible for
keeping track of all parts and accessories, including the toolkit and magnet sheet. As meetings
will be essential to the group’s success, members must attend at least 90% of all agreed upon
team meetings (i.e. if we have 5 meetings in total, come to at least 4). Being a diverse team,
members must be respectful and considerate of other teammates’ time and ideas.

Resolving Conflict
Conflicts are a common occurrence that people often encounter in the workplace and in other
contexts. In order to facilitate successful resolutions for conflicts and a healthy team dynamic, all
communication about conflicts will take place in person during team meetings. In accordance
with Jayna Fey’s suggestions from her article, ​12 Techniques For Resolving Conflicts In The
Workplace,​ a team member presenting an issue to the group will follow 4 standard guidelines: 1)
set aside the idea of winning and being right, 2) search for a “root cause” rather than focusing on
placing blame, 3) collaborate with other teammates in order to work out the problem, and 4)
communicate what ideas and methods are working, and what can could be improved upon
(2018). In the event of conflicting ideas or arguments, the team will focus on implementing
techniques in order to counteract these type of situations. First, we will evaluate the problem in
order to construct a resolution. Next, we will listen to the individual(s) involved in the conflict.
Lastly, those involved will share a proposal of what that individual believes should be done, and
the group will vote to come to a mutual decision (Gua, 2011).

Termination Clause
If the team’s plan for conflict resolution fails, we will abide by a simple 3 strikes rule. Each
strike will be in the form of a written notice by the project manager, signed by both the party
receiving the strike and the project manager.
Actions worth a strike include:
● Failing to communicate with the team for 3 or more days or when important due dates
arrive
● Consistently not completing assigned or chosen tasks
● Disrespectful attitude/actions towards the group as a whole or an individual team member
● Not attending expected number of team meetings
● Consistently missing class
Upon receiving the third strike, the group will then discuss with professor Bruce for further
procedures.

Timeline
Group Charter for Peer Review
-Due Mon., Sept. 24 in class (Printed and Digital Copy)
Group Charter Final Draft
-Due Tues., Sept 25 by 11:55 p.m. on Titanium
First Team Member’s Progress Report – Mike G.
- Due Mon., Oct. 1 in class
Proposal First Draft and iFixit Email Message
- Due Weds., Oct. 3 in class (Printed)
Proposal Final Draft
- Due Thurs., Oct. 4 by 11:55 pm on iFixit.com
Troubleshooting Page
- Due Mon., Oct. 15 by 11:55 pm on iFixit.com
Device Page
- Due Weds., Oct. 17 by 11:55 pm on iFixit.com
Second Team Member’s Progress Report – Aliyah M.
- Due Weds., Oct. 17 in class
Third Team Member’s Progress Report – Haleigh S.
- Due Weds., Oct. 31 in class
Completed Guide
 - Due Weds., Oct. 31 by 11:55 pm on iFixit.com
Fourth Team Member’s Progress Report – Terrinda A.
- Due Weds., Nov. 7 in class
Draft Team’s Evaluation Memo
- Due Weds., Nov. 14 in class (Printed)
iFixit Final Project Folder
- Due Mon., Nov. 19 on Titanium

Timesheet
Topics and Items Worked Date Time Spent: Name(s) of Team
Due Dates: On: Worked Member(s):
On:

Group Charter for Peer - Mission - 9/17 - 30 minutes - Mike Gonzalez

Review - Due 9/24/18 - Expectations
in class (Printed and
Digital Copy)

- Mission - 9/19 - 30 minutes - Haleigh St. Paul

- Expectations

- Firing clause - 9/23 - 60 minutes - Haleigh St. Paul

- Timeline
- Expectations
- Revisions

Group Charter Final - Timesheet - 9/24 - 20 minutes - Haleigh St. Paul

Draft - Due 9/25/18 by - Firing Clause - 9/25 - 60 minutes
11:55 pm on Titanium - Resolving
Conflict
- Revisions

- Resolving - 9/25 - 60 minutes - Mike Gonzalez

Conflict
- Firing Clause
- Revisions

First Team Member’s - Mike Gonzalez

Progress Report - Due
10/01/18 in class and on
Titanium by 11:55 pm
Project Proposal First - Introduction -9/26 -30 minutes - Terrinda Alonzo
Draft and iFixit Email - Project
Message - Due 10/03/18 Description
in class (Printed) - Revisions
- Project Abstract

- Introduction -10/01 -30 minutes - Terrinda Alonzo

- Project - Aliyah Malapit
Description
- Revisions
- Project Abstract

- Introduction -9/26 - 10 minutes - Aliyah Malapit

- Project -10/01 - 20 minutes
Description - 10 minutes
- Revisions
- Project Abstract

- Memo - 9/27 - 10 minutes - Haleigh St. Paul

formatting - 10/01 - 20 minutes
- Summary - 10/03 - 30 minutes
- Timeline
- Conclusion
- Editing/revisions

Troubleshooting Page - - Create different -10/08 - 60 minutes - Aliyah Malapit

Due 10/15/18 by 11:55 sections - Haleigh St Paul
pm on iFixit.com - Laptop won’t - Mike Gonzalez
turn on section - Terrinda Alonzo
- Device
overheating
section
- Speakers not
working section
- Screen won’t
turn on section

- Device - 10/10 - 10 minutes - Haleigh St. Paul

overheating - 10/15 - 45 minutes
section
- Editing/revisions
- Coding text to
create headers

Device Page - Due - 10/17 - 50 minutes - Haleigh St. Paul

10/17/18 by 11:55 pm
on iFixit.com

Second Team Member’s - Aliyah Malapit

Progress Report - Due
10/17/18 in class and on
Titanium by 11:55 pm

First Completed Guide - - Create guides on - 10/28 - 150 minutes - Aliyah Malapit
Due 10/31/18 by 11:55 iFixit and provide - 10/29 - 30 minutes - Terrinda Alonzo
pm on iFixit.com introduction - 10/30 - 60 minutes - Mike Gonzalez
- Disassemble - Haleigh St. Paul
product
- Capture images
of disassembly

- Battery - 10/29 - 30 minutes - Haleigh St. Paul

Replacement - 10/31 - 100 minutes
Guide
- Keyboard
Replacement
Guide
- Upload images
to iFixit and
- Guide
instructions/steps

Third Team Member’s - Purpose and - 10/30 - 125 minutes - Haleigh St. Paul
Progress Report - Due Summary
10/31/18 in class and on - Problems
Titanium by 11:55 pm Encountered
- Completed iFixit
Tasks
- List of Current
and Remaining
Work
- Conclusion

Fourth Team Member’s - Terrinda Alonzo

Progress Report - Due
11/07/18 by 11:55 pm
on Titanium and in class
on 11/12/18
Draft Team’s
Evaluation Memo - Due
11/14/18 in class
(Printed)

iFixit Final Project

Folder - Due 11/19/18
by 11:55 pm on
Titanium
 References

Blank, L. (Producer), & Davis, A. (Director). (2003). ​Holes.​ [Motion Picture]. United States:

Walt Disney Pictures.

Fey, J. (March 4, 2018). ​12 Conflict Resolution Techniques for a Peace Workplace.​

Retrieved from TheDigitalProjectManager.com

Gua, J. (January 27, 2011). ​Methods of Resolving Conflict.​ Retrieved from blog.Marconet.com