DOC PREVIEW
MIT 16 01 - SP2 Lecture

This preview shows page 1-2-16-17-18-33-34 out of 34 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 34 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 34 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 34 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 34 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 34 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 34 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 34 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 34 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

UnifiedUnified --Systems and LabsSystems and Labs Requirements, Teamwork, CompetitionRequirements, Teamwork, Competition Spring Semester 2004Spring Semester 2004 SP2 Lecture 16.030-040 Unified Engineering Prof. Charles P Coleman Col. Pete Young 16.030/040 Unified Engineering February 12, 2004 System Problems and LabsLecture OverviewLecture Overview Importance of Requirements – Case Study Harrier Teamwork Project Management Competition SP2 and Team Assignments 16.030/040 Unified Engineering February 12, 2004 System Problems and LabsSystemsSystems • People • Product U.S. Airways – Hardware – Software McDonald's • Process – Procedures AWACS Global Positioning System 16.030/040 Unified Engineering February 12, 2004 System Problems and LabsCDIOCDIO Groups of people: – Conceive – Design – Implement and – Operate systems 16.030/040 Unified Engineering February 12, 2004 System Problems and LabsCDIOCDIO Getting groups of people to: – Conceive – Design – Implement and – Operate systems is…not easy 16.030/040 Unified Engineering February 12, 2004 System Problems and LabsTeamworkTeamwork MIT - The Collaboration Toolbox http://web.mit.edu/collaboration/ Systems Problem 1: 1.1 Formulate a Team Mission and Vision Statement 1.2 Create Team Management Plan 1.3 Minutes of Meeting #1 1.4 Agenda for Meeting #2 1.5 List of Action Items 16.030/040 Unified Engineering February 12, 2004 System Problems and LabsWhen it’s good…When it’s good… • When we started the project, our main goals (printed or not) were tocomplete the parts of the projectthe best we could in the time allowed. Winning the competition was certainly not a main goal. Thefinished product performed WAYbeyond what we expected and wecould not be more pleased. 16.030/040 Unified Engineering February 12, 2004 System Problems and LabsWhen it’s good…When it’s good… • I believe that as a team we worked extremely well together. We weretolerant with each other, alwaystrying to maintain constructive criticism and respect each other’s opinion, in every situation. Welearned to depend on each other very much and had to pull eachother “out of the hole”… 16.030/040 Unified Engineering February 12, 2004 System Problems and LabsWhen it’s bad…When it’s bad… • There were frustrating moments…Thedynamic of my group when we sat together to do a System Problem did not work the way I like. Basically it wasa disorganized meeting, witheverybody giving ideas but withoutreally reaching a consensus. We could spend 1 or 2 hours without doing anyproductive work… 16.030/040 Unified Engineering February 12, 2004 System Problems and LabsWhen it’s bad…When it’s bad… • When we had to divide up the work on the design problems, it seemed like we all just did our stuff and attached it in one ugly mess to turn in…Another period of unorganization” was building the plane. We never knew exactly when we were going tomeet….I guess that’s more of aproblem of communication, though… 16.030/040 Unified Engineering February 12, 2004 System Problems and LabsWhen it’s bad…When it’s bad… • Trying to get our group together to work on theplane/assignments earlier than the Thursday nightbefore it was due. Nobody was willing to work onFriday night (especially me). Saturday’s werefilled with other commitments people had such assports, sleep, etc. Sunday, we worked on the Unified problem set, which took all of that day andMonday. Tuesdays were always shot because ofa 16.070 problem set due the next day.Wednesdays were usually used to study for theusual Unified test on Thursday. This left Thursdaynights to complete the entire assignment. 16.030/040 Unified Engineering February 12, 2004 System Problems and LabsTools:• FRDIARRCKeys to SuccessKeys to Success Design Project Mgmt Teamwork • Process • Time • Communication • Analysis • Resources • Coordination • Risk • Roles & Responsibilities • Motivation! Tools: Tools: Tools: • Mission/Vision• FRDIARRC • WBS • Gantt Chart • Management Plan • Roles & Resp • Effective Mtgs 16.030/040 Unified Engineering February 12, 2004 System Problems and LabsTeamworkTeamwork ––Mission & VisionMission & Vision StatementsStatements Mission Statement • Describes current state • Defines Purpose and Values Vision Statement • Describes a desired future state • Measurable, actionable, and achievable goals Clear, simple, precise language 16.030/040 Unified Engineering February 12, 2004 System Problems and LabsTeamworkTeamwork ––Mission & VisionMission & Vision StatementsStatements Pros • Establishes framework for ethical behavior • Defines performance standards • Communicates common focus and goals Cons • Unrealistic goals • Insufficient resources allocated to support plan • “Business as usual” after introduction • Lack of support and commitment www.bain.com/bainweb/expertise/tools/mtt/mission_value.asp www.libertysystems.net/missionandvisionworkshops.html wi.essortment.com/writemissionvi_rvld.htm 16.030/040 Unified Engineering February 12, 2004 System Problems and LabsTeamworkTeamwork ––Mission & VisionMission & Vision StatementsStatements US Dept of Labor Women’s Bureau Mission Statement • To promote profitable employment opportunities for women, to empower them by enhancing their skills and improving their working conditions, and to provide employers with more alternatives to meet their labor needs by advocating for equitable employment standards, policies, and programs. Vision Statement • We will empower women to enhance their potential for securing more satisfying employment as they seek to balance their work-life needs. http://www.dol.gov/wb 16.030/040 Unified Engineering February 12, 2004 System Problems and LabsExpectationsExpectations • We expect from each member not onlyto put in the required amount of work each week but to follow through with what they say they will do, respect team members, and be able to trust each member of the team. • We decided as a team that winning isn’t everything, we will give winning a fairshot, but do not expect to say up nights,and burn ourselves out in order to win. 16.030/040 Unified Engineering February 12, 2004 System Problems and LabsTeamworkTeamwork ––Mission & VisionMission & Vision StatementsStatements Mission Statement • We are a group of Unified Engineering students respectful of


View Full Document

MIT 16 01 - SP2 Lecture

Documents in this Course
Fluids

Fluids

3 pages

Fluids

Fluids

4 pages

Fluids

Fluids

4 pages

Fluids

Fluids

5 pages

Load more
Download SP2 Lecture
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view SP2 Lecture and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view SP2 Lecture 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?