Syllabus  --   Fall  2004

Subject to revision to correct errors and omissions and/or in the interest of fairness.    GMU policies and procedures take precedence should there be a discrepancy between any of them and this syllabus.

 

Students should read the syllabus and confirm the dates shown. 

Deliverables and processes will be discussed in class. 

Please notify the instructor of any errors, omissions, or contradictions.

 

Syst 798 --  Research Project

Sections 002 & 632

CRN  74515 &  76152

 

GMU  --   Fairfax & Dahlgren

 

 

Instructor

William Adams, PE, PhD

wadams1@gmu.edu –

Please do not send attachments.

Please virus check your PC before sending emails or creating softcopy of files.  Thanks.

 

Other contact information will be given in class.

Office: TBD - best to see me before or after class

 

 

Schedule of class meetings

Tuesdays 

(but see the GMU schedule of classes for recess, holiday closings, one time exceptions,  etc.  )   Check the GMU phone number for late breaking snow cancellation information.

 

Time:   16h30 – 19h10  J **

Bldg.- Room --  IN 131 &   NSWC Bldg 216 Room 116

[JD's Training and Conference Center 17320 Dahlgren RD]     

 

(Also see the Detailed schedule with planned  lectures and assignments  below).  Some generic  assignment dates will be instantiated in class eg which specific date(s)  you/your team is assigned.

 

Schedule Strategy

We must get a running start or risk not being able to complete the project on time without a lot of effort concentrated near the end of the semester.

 

Students should come to the first class with a possible topic, a general outline of a technical report, and a moderately detailed list of steps that need to be performed.

 

We will discuss these and tailor them as appropriate.

 

No Tuesday class is held at GMU on 12 October 2004  TBV  due to Columbus Day;  because those Monday GMU classes meet on Tuesday that week.

NB: The fall schedule of classes has Columbus day as the 13th (sic) (Wednesday), my calendar says it is the 11th (Monday).

Students should continue to be working diligently this week; and be prepared to present/submit deliverables due the next class as shown on the schedule below.

 

Many classes will start with group discussions and or presentations, followed by team working sessions/faculty consultation,  and  followed by optionally individual consultation as desired.   Lectures will be minimal and primarily address administrative items, unless specific  topics are requested by the students.

 

If we do not need all the class time then the groups should use the rest of session to coordinate their work and continue working on their TR (Technical Report).   I will stay to answer questions and consult as needed.

 

We will not meet every week.  Students are expected to continue to  work diligently and use the class time for their project.  Status reports are due every week whether we meet or not.  They can be emailed as text in the email on those days.

 

If a team needs additional consultation  about their project they may schedule it for an off week but the rest of the class will not be required to attend that session.


 

Communications

Most communications will be by email or in class. 

 

Students must provide contact information that is functional.   Students are responsible for all group/team broadcasts sent to the email(s) provided.

 

Please provide work, home, and any alternate emails and phone numbers that may be necessary to ensure that you get course information without delay.   Phone calls will be limited to emergency situation such as snow preventing class from being held.

 

Teams may choose to communicate amongst themselves by any method they prefer.  Many teams make heavy use of email, and/or web based bulletin boards, wikis, etc.  

 

 

Course Description

Research Project.   Prerequisite 21 Graduate Credits.

This course is the capstone course for the MS program in SE and/or OR, for those who choose the project option instead of the thesis option.

 

Either Syst798 (fall)  or OR680 (spring) may be taken as the required project course.

 

As is common with the capstone course at  many universities, this course uses a team oriented approach

 

This course will use many of  the systems engineering and related skills normally developed through previous classes and as would be used in a business teamwork environment.  Soft skills as well as technical ones will be exercised.

 

Students will select a research project,  which will be completed under the guidance of the  graduate faculty member assigned to the class.   A condensed version of the report will be presented orally to the SEOR faculty which must approve the work done.  A hard copy of the complete report will also be turned in and graded separately.

 

See details below of all deliverables that are required.

 

Project Description

The project must reflect a real life problem or application  and ideally will have a sponsor.    Note:  GMU policy does not allow for anyone to have a project that they are also being paid for doing. 

 

 Projects must also involve analytical components such as a decision and or risk analysis, cost benefit and tradeoff analysis,  mathematical modeling,  simulation, etc.  Projects should also include a data gathering element.

 

The project will be done by teams of 3-5 persons.  

Teams will be self selected and formed by the students at the first class.

 

Each person must have explicit responsibilities that they do on their own.

 

Each team member must provide part of the final briefing at 1300J  in the Johnson Center at GMU on 10 December 2004. 

 

Participation is important.  All teams should review and  comment on other teams work during in-class reviews.  

 

 

Objective/Outcomes

Create a technical report (TR) using the KSAs gained through previous coursework or experience.  The report must be acceptable to the SEOR faculty.  

 

Students will demonstrate what they have learned by gathering data and analysing it by applying an appropriate SE process.

 

The report should be comparable to one given at a conference or printed in professional publications.  

 

Ideally the TR will be accepted by a conference, or journal, or published internally by  the student's employer.

 

“Best Practices” of SE Processes are to be used.   The processes should be tailored to facilitate the technical report project.

 

Expectations

Each student will succeed in helping their team achieve an acceptable TR by working diligently and cooperatively by using the SE skills and techniques from their previous courses.

 


 

Textbook and Reference Materials

Text:  None.

 

Some useful references:

·        Technical Report Writing

NASA Technical Memorandum 105419

Was recently available at

http://grcpublishing.grc.nasa.gov/editing/vidcover.cfm

http://grcpublishing.grc.nasa.gov/editing/vidoli.CFM

Highly Recommended !!

 

·        How To Write And Publish Engineering Papers And Reports 3E

Michaelson, Herbert B.

Phoenix AZ

Oryx Press 1990

T11.M418 1990

 

·        How To Write And Present Technical Informaton  3E

Sides, Charles H.

Phoenix AZ

Oryx Press 1999

T11.M418 1990

 

·        Writing And Speaking In The Technology Professions: A Practical Guide

Beer, David F.

New York

IEEE Press c1992

T11.W75  1992

 

·        The Craft Of Research

Booth Colomb and Williams

Q180.55.M4  B66 1995

University of Chicago Press

 

·        Practical Research Planning and Design 6E

Leedy, Paul D.

Q180.55.M4 L43 1997

Prentice Hall (Simon & Schuster) 1997

 

·        IEEE

http://standards.ieee.org/guides/style/

 

·        Textbooks from previous courses.

 

 

 

Other Assistance

Research

For help with research, Kelly Jordan, Information Technology and Engineering Librarian, is a useful resource.  Stop by the Fenwick library or email her at kjordan2@gmu.edu.

 

Writing

For help with writing,  the GMU writing center may be useful.  There are many web sites that provide writing and grammar assistance.  Many universities have on line writing centers  (OWL = online writing lab) for assistance.  The GMU center is at

http://writingcenter.gmu.edu/owl/

 

Some OWLS  are listed at

http://owl.english.purdue.edu/internet/owls/writing-labs.html

 

NOTE

Whilst grammar and style are  important, quality content is the first priority.  Do not get sidetracked with mechanics before the content has been instantiated.   But allow time to create a quality document.

 

 

Course Requirements

See details below under deliverables and schedule. 

 

Students will tailor and use a process to be followed.  Metrics will be captured and progress tracked versus the schedule based on the planned tasks. 

 

Interim status presentations will be made periodically as if to a corporate director.

 

A final presentation will be presented as well as a final hard and soft copy of the report being turned in.   This would be comparable to one given to a corporate VP or at a technical conference.   Faculty and advisors will be invited to the final presentations.

 

A project plan with sufficiently detailed list of tasks, schedules, persons assigned, milestones, etc., to execute and control the project, will be turned in.  

 

At the end of the semester, the plan with any modifications made, and  indicating actual results will be turned in including  metrics captured that can help future planning .

 

An earned value report for the team will be due weekly.

 

Team and individual status reports will be due weekly. 

 

Each person must turn in an AALL (After Action /Lessons Learned) report with  suggested process improvements for the course, team, and individuals. 

This AALL should cover everything that can be improved, including the strategy, processes,  instructor, syllabus, room, A/V equipment,  project plan, teamwork, research, analysis, writing, etc..

 

Each person will turn in an evaluation of themselves as well as all teammates contributions.  This will be used as a guide to adjust the team scores for each individual.

 

Each team should turn in all artifacts they used or located that they used and/or could help future teams.  This should include a list of bookmarks for web resources.

 

The key deliverable is the technical report and a formal presentation to the faculty.

Interim presentations and status reports will be given in class.

 

There are no formal exams. 

 


 

Grading Criteria

Grades will be per GMU policy. 

This course uses required grading scheme GT for graduate courses.

 

Students will be required to turn in a self assessment as well as one for their team.  Students will assess the other presentations.

 

Faculty will be invited to the final presentation and to review the final TR. Their feedback will be given considerable weight.

 

The final grade   will be determined by myself with consideration given to inputs from student and faculty evaluations. 

 

Grades will be based on the following items - with the noted relative weighting factors.

 

·        30%   -  Final written Technical Report - teams self allocate distribution of  total awarded points.

v     Emphasis is on content, but presentation and mechanics will count

v     NOTE: allocation is based on a par of 100% of the team grade.   Awards may be smaller for those who do not contribute and may be larger for someone who carried the team by doing more than their share.

·        40%  -  Final oral Presentation - teams self allocate distribution of  total awarded by the faculty

v      Emphasis is on content, but presentation and mechanics will count

v     NOTE: allocation is based on a par of 100% of the team grade.   Awards may be smaller for those who do not contribute and may be larger for someone who carried the team by doing more than their share.

·        20% - AALL and other required team/individual submissions.

·        10%  - Status reports – Team and individual

·        Additional bonus points may be awarded for

ιDraft presentions or other work of exceptional quality

ιClass participation - PAL contributions

ιMiscellaneous - TBD

 

Late work

Late work is accepted but the grade is reduced by 10% a week unless an acceptable reason is provided.  

 

If you anticipate  any religious holidays, employer mandated travel, health appointments, or critical personal issues (tax audits, court appearances, funerals, weddings, etc.),  that will require you to miss class or be late with work please notify the instructor as early as possible.   And coordinate with your team so they are not impacted too.   Confirming documentation is  required.

 

Even if you have an excused absence,  you must still meet all of  your team commitments! 

If your team does not consider your excuse acceptable they may lower their assessment of your contributions which will lower your final grade.

 

Conversely, any superstars that do more than expected may have their grade increased based on the team’s assessment of that effort.

 

 

Scale

A+       98-100+

A         93-97

A-        90-92

B+       87-89

B          83-86

B-        76-82

 

C         63-75

 

F          £ 62

 

Other grades are theoretically possible in accordance with GMU policy:

IN        incomplete - missing work - shows as F

AB       - absent last day with acceptable excuse - ten day limit to finish

S          - no grade required

NC      - no grade required

IP         in process -  will require department approval

 

Success Criteria

A Sample TR will be provided as a guide.

 

Details of specific presentation and TR grading criteria will be provided in class.

 


 

Honor Code

Attention should be paid to the honor code provisions.

 

All work is open book, open notes, and done collaboratively, as would occur in an industrial team oriented project environment.  

 

For academic purposes though, acknowledgement must be made of all sources used.   This includes all team and classmates, colleagues at work, text books, web references, etc.

 

Work is intended to be done collaboratively with their team, and/or the class.  Teams may help each other but acknowledgement is to be given to such help. 

 

Proper credit is to be given to any other information sources used by citing them in the TR.

 

Style and usage

Use the GPO or Chicago style manuals for citation format.

Use the Columbia guide for web based content citations.

Harbrace College Handbook or Hacker are good guides for grammar usage.

 

References:

The Chicago Manual of Style  13E (or later)

Chicago

U of Chicago  1982

 

Style Manual rev.

US GPO

Washington

GPO 1973 (or later)

http://www.gpoaccess.gov/stylemanual/browse.html

 

Rules for Writer 3E  (or later)

Diana Hacker

Boston

St Martin's Press  1991

 

The Columbia Guide to Online Style by Janice R. Walker and Todd Taylor (Columbia UP, 1998)

http://www.columbia.edu/cu/cup/cgos/idx_basic.html

 

Class Policies and Approach

All applicable laws and GMU policies are hereby included by reference.

Students are responsible for knowing the school policies as documented in the Catalog including the honor code provisions.

 

Smoking is not allowed in the classroom.

 

All notes as well as class submissions should be annotated with a timestamp and the source.

 

Acknowledgement of all sources is expected if material from a textbook, website,  intra/inter-team collaboration, or class discussions is used.

 

Students are expected to

·        attend all sessions on time. 

·        You may synchronise your watches by telephone at 202 762 1401.

·        be prepared

·        participate actively

·        be alert, having had adequate sleep and rest

·        manage their time effectively

F   plan their work and budget their time

F   keep a log of all resources expended

F   do not get behind

·        coordinate and work with their team effectively and collegially

·        first attempt to do all the work by themselves

F   ask for help when necessary

 

Teamwork is an integral factor of this course.  All students are expected to work in a collaborative and cooperative manner both on their project team and in the class as a whole.   Planning and coordination are expected to minimise duplication of efforts.

 

Communication is vital to success  and will be emphasised through in‑class briefings concerning the team projects and written status reports.

 

 

Accommodations

Any student needing accommodation for a handicap will be given whatever course modifications they need as determined appropriate by the DRC staff.   The DRC form is required.


 

Project/Assignments

The main product is a technical report.  

A final oral presentation will also be given. 

Interim status reports and drafts will be due.

 

Each student is to log all resources used by category for the entire course.

This will be used to create the metrics turned in as part of the other course  deliverables.

 

Frequently,  status reports will be presented by teams as well as being  turned in for evaluation. 

 

Additional items will be assigned in class.

 

For mats

Please provide hardcopy of all assignments. 

Softcopy is also required for the final report and presentation as well as the AALL and PAL contributions.  

 

E-mail format

When sending emails, please put 798 as the first item in the subject line, followed  by your name, team number, and a sequence number, then a  few keywords of the subject. 

 

Please include the actual time and date at  the top of the  message.

 

Please do not send attachments.

 

Fonts

To prevent my having eyestrain or other visual problems:

Please use a font that is 12-14 points, with 2-3 points of leading for text. 

Do not justify,  ie use ragged right margins.   

 

Use 1.5" left margin and all other margins set at 1".

If headers/footers are used and/or page numbers, then they should be spaced 1/2" from the text body.

 

Preferred fonts are  American Typewriter aka Editor, or Dark Courier.  Other large x-height fonts with uniform stroke weight may be used; but, please confirm readability with the professor first.  Thanks!

 

 Trebuchet and  Antiqua are other MS fonts that may be used.

 

Do not use Garamond or (new) times roman or similar fonts with small x‑height or tight tracking.  

If you prefer that style of font then please use Georgia instead,  which  is a free MS font that is equivalent in style, but was designed to be  easy to read.

 

Fonts can be provided to those who do not have them and are unable to download them from Microsoft, HP, or public domain sites.

 

Spreadsheets and similar items should use Arial Narrow 8-10 point.

 

TIPS:

  • Do not procrastinate
  • Communicate
  • Log all references used in real time
    • Easier than trying to go back to find them
    • Web sites disappear
      • Capture any web pages that are used in the report
    • Fully format each reference as it is captured
  • Timestamp all artifacts to ease CM/DM version control
  • Work Smart not Hard
  • Do the requirements right before starting
  • Allow buffer time for contingency
    • Consider using Goldratt Critical Chain
  • Do the outline early on
    • Fill in as you go – helps easy CM and version control
  • One master copy on the web helps versioning
    • Coordinate so only one person changes things at a time
  •  

 


 

 

Deliverables – see schedule below  for due dates

Note:   Most of these are small routine items that you need to do your work anyway. 

 

  1. Final oral presentation given to faculty. – Team –
    1. 30 copies of the slides used – 2/page & double sided okay
    2. Softcopy of the powerpoint files used - to load on PC
  2. Final written technical report – Team – 
    1. Three copies hardcopy
    2. One Softcopy CDrom or Floppy
  3. Class participation – Individual – weekly
  4. Team artifacts -  others supporting the plan – typically £ 1 page each
    1. Team Charter
    2. Ground rules
    3. Roles and task assignments

1)      Due date

2)      Criteria for acceptability

    1. Communications process
    2. Meeting process
    3. Decision process
    4. Conflict resolution process
    5. Writing process
    6. Risk plan
    7. Peer Review
    8. CM/DM or version control process
    9. Others if appropriate
  1. Status reports – Team tasks only, time spent by task- weekly -  extract from individual status reports - OPTIONAL with a  resulting Earned Value estimate
  2. Status reports – Individual – with team tasks allocated to team WBS – weekly
  3. Project Plan – MS Project – Initial Planned – Team
    1. WBS  sufficiently detailed to monitor and control the project
    2. Tasks allocated to a team member
    3. Gantt Version to show dependencies and time estimate
  4. Earned value report – team – weekly – with team status report
  5. Project Plan – Final  Actual – Team
    1. Show actual effort used
    2. Reflects all  changes to original plan
  6. Project Proposal – Team
  7. Report Outline – Template or DID – Team
  8. Interim status briefings – Team – oral status report
    1. Each team member must be prepared to give the report

1)      Presenter will be selected at random

 

  1. Interim artifacts – team –
    1. Report outline -  with some detail
    2. Data
    3. Bibliography
    4. Analysis
    5. Rough draft – paper
    6. Presentation outline
    7. Rough draft – presentation
    8. Dry Run presentation
    9. Near Final Draft – paper
    10. Rough outline
    11. Draft presentation
    12. Final draft paper

14              AALL – Individuals  --  hard and softcopy   

15              PAL (Process Asset Library) Artifacts -   TEAM – hard and softcopy

a)      Reference documents

b)      Sample of all team generated artifacts for reuse

c)      Web Favorites/Bookmark list (softcopy)

16      Team and self evaluations and grade allocation recommendations.

 

 

-------------------------------------------------

Notes:

 

**   J = local time.  We change from DST to EST in October.

 

-------------------------------------------------

 

 

The Schedule is Below in Landscape Orientation

 

-------------------------------------------------


 

 

Schedule  --  Refers to Deliverables as numbered above

Line

Week nr.

Class nr.

Date

Student activity

Class agenda

Team Items Due

Individual Items Due

Notes

1

 

 

 

 

 

 

 

 

2

 

 

 

  • Identify possible topic

 

  • Think about what tasks are necessary

 

  • Think about the contents of a TR eg high level outline

 

  • Read Syllabus

 

 

 

 

 

3

 

 

 

 

 

 

 

 

4

1

1

31-Aug-04

  • Teams meet – exchange contact info, determine communications methods, next meeting, initial steps necessary for next class.

 

  • Administrative items
  • Kickoff/Introduction
  • Go over Syllabus
  • Review Schedule
  • Review Requirements
  • Teams
  • Process to be tailored
  • Resources
  • Grading
  • Deliverables
  • DIDs/Templates
  • Q&A - Discussion
    • Break
  • Teams Assigned
  • Identify Possible Topics
  • Brainstorm alternatives
  • Discussion
  • Tentative topic selection  -  primary  and  one alternate
  • Teams meet briefly
  • Identify supporting topics eg time management etc.
  • Wrap up – Final questions

 

 

- possible topic

 

- high level tasks to be done

- high level outline of a TR

 

5

 

 

 

Teams – Storm & Norm

 

Document Team processes; set up meetings, communications, initial task assignments, etc.

 

WBS

Draft Plan

 

Investigate topics

Focus topics

Select

 

Prepare proposal

 

 

 

 

 

 

6

2

2

7-Sep-04

 

Team Proposals

Discussion

 

optional team working session

 

Will meet with teams or individuals if requested at the end of any class

4

10

13J

 

5

8

 

3

6

 

3&6;5&8 due every scheduled class whether we meet or not – fax or email as text

7

 

 

 

Teams Form (Gel)

 

Finalise Plan and Sked

 

Continue working tasks

 

 

 

 

 

8

3

3

14-Sep-04

 

Present status – plans emphasis but also sked problems etc briefly

 

optional team work sessions

 

I will be available for consultation during the rest of the class while  any students remain

7

12

 

5

8

 

3

6

I will give you comments on any item turned in if you request.

 

I may comment on them anyway.

9

 

 

 

Teams Perform

 

Work Your Plan!!

 

 

 

 

 

10

4

4

21-Sep-04

 

Project status -  progress including outlines but briefly problems etc

 

working sessions

consultation as requested

11

12

13A

 

5

8

3

6

 

11

 

 

 

 

optional appointment for consultation

 

Keep Working!

 

 

 

 

 

 

12

5

5

28-Sep-04

 

 

Keep Working your plan!

Formal Class Not Planned

 

Will meet with any team that requests it  by  previous Friday

12

 

5

8

 

3

6

 

13

 

 

 

 

Keep Working your plan!

 

 

 

 

 

14

6

6

5-Oct-04

 

Keep Working your plan!

Present status – data  emphasis but also progress and problems briefly

 

working sessions

consultation as requested

13B

 

5

8

3

6

 

 

15

 

 

 

 

Keep Working your plan!

 

 

 

 

 

 

 

16

7

 

12-Oct-04

Keep Working your plan!

 

NO CLASS – GMU  Holiday

 

--

--

No Class

17

 

 

 

 

 

Keep Working your plan!

 

 

 

 

 

18

8

7

19-Oct-04

 

Present Status – emphasis analysis but briefly progress and problems

 

working sessions

consultation as requested

 

12

13D

 

5

8

3

6

 

 

19

 

 

 

optional appointment for consultation

 

Keep Working your plan!

 

 

 

 

 

20

9

8

26-Oct-04

 

Keep Working your plan!

 

Formal Class Not Planned

 

Will meet with any team that requests it  by  previous Friday

5

8

 

3

6

 

21

 

 

 

 

 

Keep Working your plan!

 

 

 

 

 

 

 

 

 

 

22

10

9

2-Nov-04

 

Status – progress and problems

 

working sessions

consultation as requested

12

 

5

8

 

3

6

 

 

23

 

 

 

 

Keep Working your plan!

 

 

 

 

 

24

11

10

9-Nov-04

 

Present status emphasis recent results but briefly progress and problems

 

working sessions

consultation as requested

13C

13E

13F

 

5

8

 

3

6

 

 

25

 

 

 

 

 

Keep Working your plan!

 

 

 

 

 

 

 

26

12

11

16-Nov-04

 

Project status -  emphasis rough draft paper and  briefly describe rough draft of presentation

 

working sessions

consultation as requested

13I

13G

 

5

8

3

6

 

 

27

 

 

 

 

 

Keep Working your plan!

 

 

 

 

 

 

 

28

13

12

23-Nov-04

 

Present rough draft version of final presentation

 

discussion, comments, feedback

13K

13L

 

5

8

 

3

6

 

29

 

 

 

 

 

 

Keep Working your plan!

 

 

 

 

 

 

 

30

14

13

30-Nov-04

 

Final Comments on papers returned

 

5

8

3

6

 

31

 

 

 

·        Produce Final TR

·        Produce Final Presentation PPT

·        Rehearse presentation for dry run

 

 

 

 

32

15

14

7-Dec-04

 

  • Dry Run Final Presentation

 

2

9

15

13H

 

5

8

 

 

14

16

 

3

6

 

 

 

33

 

 

 

·  Rehearse Presentation

·  Make 30 Hard Copies

·  Make softcopy for team use

 

 

 

 

34

16

15

 

10-Dec-04

 

 

  • Presentation to Faculty

 

 

1

 

 

1

 

35

16A

 

Rain/Snow/Ice Alternate Date  -  TBD

 

 

 

 

 

36

 

 

 

 

 

 

 

 

Line

Week nr.

Class nr.

Date

Student activity

Class agenda

Team Items Due

Individual Items Due

Notes

 

 


 

Skills that may be used to some extent:

  • Time Management
    • Prioritisation
  • Project planning
  • Presentations
  • Writing Process
    • Topic Selection
    • Focus
    • Question – Hypothesis
    • Research
    • Analyse
    • Assess
    • Proof
    • Conclusions
    • Organise
    • Write Draft
    • Edit
    • Format and Package
    • Publish
    • Present
  • SE Processes
    • Problem Definition
    • Define Stakeholder
    • Define criteria for success
    • Tailor processes for the specific project
    • IPT/IPPD teams
    • Requirements
    • Peer review
    • Validate
    • Conops if appropriate
    • Architecture if appropriate
    • Alternatives
    • Analysis
    • Assessment
    • Selection
    • Design if appropriate
    • Develop if appropriate
    • Verify
    • Recommendation
    • Documentation
    • Plan and Organise
    • Monitor and Control
      • Earned value
      • Capture metrics
    • Coordinate
    • Manage Risk
    • Control Data and configurations
    • Ensure Quality
      • Reliability
      • HF- MMI/CHI
      •  
    • Tailor processes
    • Capture metrics
    • Recommend Improvements
    • Coordinate with customer
    • Manage suppliers
    • Training
    • Problem resolution
    • Prevent defects
    • Use and Manage tools
    • PAL – use and improve tools, techniques, data, templates, reports, and other artifacts for reuse
    • Statistical and Six Sigma techniques
  • Teamwork
  • Meetings
    • Agenda
    • Document decisions and action items
    • Assign tasks and deadlines
    •  
  • MS Office
    • Word – TR and status reports
    • Project – plans
    • Powerpoint – presentation
    • Excel –  status reports  - and  if needed for data storage and reports/analysis or graphs
    • Visio – or similar for diagrams
    • Access – if needed for data storage and reports
  • SE or Scientific Software
    • Statistical Analysis
    • Graphic displays
  • Risk Mitigation
  • Analysis tools and techniques
    • 7 M&T tools
    • 5 Whys
    • Affinity Diagram
    • Brainstorming
    • Cause and Effect Diagram
    • Causal Loop
    • Check Lists
    • Confidence Intervals
    • DOE
    • Control Charts
    • Flow Chart
      • DFD
      • FFBD
    • HIPO diagrams
    • Process Maps
    • FMEA
    • Histograms
    • Pareto Diagrams
    • Matrices
    • Statistics
      • Mean, mode, average
      • SD
    • Type I – Type II error optimisation
    • Hypothesis testing
    • Process model
    • QFD
    • Triz
    • Visual controls
    • Allocations
    • Nominal Group Technique
    • Scatter diagrams
    • Fishbone chart
    • Force Field diagram
    • Priority setting
    • Constrained optimisation
    • Linear programming
    • Game theory
    • Dynamic programming
    • VUCA tolerant

 

  • Time management
  • Common Sense
  • Salesmanship
  • Creativity
  • Resourcefulness
  • Listening
  • Negotiation
  • Diplomacy
  • Ethics