|
Workplace ProductivityIFSM-302(3) |
University of Maryland
University College Electronic Distance Education Heidelberg, Germany |
| DE Term 4, 2002-2003; Dates: 7 Apr. - 25 Jul. 2003 | ||
|
|||||||||||
There will be several discussion threads taking place at any one time in our WT classroom, so check in every couple days and be prepared to stay awhile. Each of you is expected to contribute to our discussions just as if you were in a face-to-face classroom. Also note that each of you can expect to lead or initiate a discussion several times during the course. The recorder is not necessarily the group leader, but you can expect to be a recorder more than once as well.
During Week 1, our discussion will focus on course mission, objectives and evaluation criteria as well as coping with technical problems raised by this distance learning method.
| Week 1 (7 - 11 Apr. '03) Course Intro & Orientation | |||
|
See Week 1 Group Assignments and Week 1 Individual Assignments Begin Course Module 1 (See WT Course Content Area.) The Course Modules have been prepared to help guide you through your study of workplace productivity. There are few experts in this vast field - but many who claim to be. Information systems can be designed to enhance productivity or retard it. That is one of the reasons we study largely non-IT methods of improving productivity in the workplace. Nonetheless, I want you to focus on IT areas for your examples and for applying the techniques you will be learning. |
|||
| Texts: Review Table of Contents, Introduction and Preface of both books, (TH = Team Handbook; MJ = Memory Jogger) | |||
|
Turn In & Participate:
|
|
Students often have difficulty identifying processes in their own work areas, in particular complete processes. In information systems we know from that certain processes are associated with transaction processing, others with operational systems like inventory management, still others with Knowledge Work Systems such as computer aided design. Workers often know their part of more than one process rather well, but struggle to comprehend the full processes in which they are involved. Pay attention to these introductory chapters. The Joiner Triangle is introduced in TH. MJ presents some basic tools that you will apply to problem situations. I want your Course Project to focus on IT/IS processes in a work area to which you have current placement and access. You will need the cooperation of the supervisor and workers. If you are familiar with quality improvement methods, that will help you with the implementation and analysis of the project. If not, the Memory Jogger booklet will prove an early source of techniques. So think about IT/IS processes that do not work as well as you think they might. If we can arrange it, I would like the Course Project conducted as a team with 5-9 students looking at the same type of situation in similar work environments. I suspect that will be tough, so I am prepared for individual projects as well. But even individual projects will have a team element - for I want each individual project to have an advisory team to discuss the improvement plan, data collection and analysis and the final report of results and method. (Typically members of each advisory team will share their individual projects with each other, solicit feedback and provide the same for each of the other members of that advisory group.) By the way, your Memory Jogger booklet is only a memory aid AFTER you have learned the techniques. So study it carefully and supplement its descriptions with research in the UMUC databases or other sources (Internet and local physical locations) as needed. Then you will have some grey cells properly trained so that Memory Jogger can do its real job of REMINDING you of "best practice" methods. This week we will look at the tools for generating and grouping ideas both in MJ and TH. I will address them in the sequence shown on the MJ Tool Selector chart, pg. vi: Affinity diagram, Brainstorming, C&E/Fishbone, Flowchart, Force Field, ID, and Tree. |
|||
| Text: Study TH Chapters 1 & 2; study MJ Working with Ideas see MJ Tool Selector chart, pg. vi: - especially the Affinity diagram, Brainstorming, C&E/Fishbone, Flowchart, Force Field, ID, and Tree. Study Module 1. | |||
| Turn In & Participate: Specifically assigned students will launch the discussions. The active participation of all students in these discussions is important. Do not miss out. We will follow this pattern often during this course. Where teams are assigned, I will appoint a team recorder. | |||
Individual
Work:
|
Group Work: Apply Process Analysis tools to Module Exercises. |
||
|
Week 3 (22 - 28 Apr. '03) Module 1: What is a process? (cont.) |
|||
|
By now everyone should have textbooks and be well into the course. You should also have started your search for a Course Project focus and perhaps started self-organizing a team of students to broaden the scope of the research. Do not let this task fall through the cracks. We continue our look at process analysis tools that focus on ideas in MJ with a look at the tools for deciding & implementing ideas both in MJ and TH. I will address them in the sequence shown on the MJ Tool Selector chart, pg. vi: Activity Network Diagram (AND), Gantt Charts, Matrix Diagram, Nominal Group Technique (NGT)/Multivoting, Prioritization, Process Decision Program Chart (PDPC), and Radar Charts. A powerful productivity tool not shown in MJ is Quality Function Deployment (QFD) which builds on the Matrix Diagram tool; we shall examine and try to apply QFD for ourselves. We look a little more deeply into TH Chapter 2 and examine why successful projects need support (Chapter 3). |
|||
| Text: Review TH Chapters 2 & 3; complete your study of MJ Working with Ideas see MJ Tool Selector chart, pg. vi - especially the Activity Network Diagram (AND), Gantt Charts, Matrix Diagram, Nominal Group Technique (NGT)/Multivoting, Prioritization, Process Decision Program Chart (PDPC), and Radar Charts; study electronic handouts (Quality Function Deployment, Hoshin Planning Techniques, etc.). | |||
| Turn In & Participate: Specifically assigned students will launch the discussions. The active participation of all students in these discussions is important. Do not miss out. We will follow this pattern often during this course. Where teams are assigned, I will appoint a team recorder. | |||
Individual
Work:
|
Group Work: Apply Process Analysis tools to Module Exercises. |
||
|
Week 4 (29 Apr. - 5 May '03) Module 2: Meetings ** Journal.1 due NLT 5 May '03 ** |
|||
|
Many of us have too many meetings. Even when tied to a computer terminal, we have meetings in virtual rooms on the Internet. So why are so many meetings so poorly conducted? Can we do something to improve this critical process? TH Chapter 4 addresses this area as does Module 2. TH Appendix C offers us several exercises that help us explore the process of teamworking in our work area. We will explore several of the exercises on teams in our work areas or local area. MJ has a set of tools related to teams as well but there is a lot of information collapsed into just a few pages. Note that there are different techniques for starting, maintaining and ending teams. See also my web site for information on small group dynamics - small groups can be teams too. (We save the Storyboard Study until next week.) |
|||
| Texts: Study: TH Chapters 2 & 4 and Appendix C; study MJ Working with Teams see MJ Tool Selector chart, pg. vii. - especially the Team Roadmap (Starting Teams, Maintaining Teams, Ending Teams/Projects and Effective Meetings); study electronic handouts on teams. Study Module 2. | |||
| Turn In & Participate: | |||
Individual
Work:
|
Group
Work:
|
||
|
Week 5 (6 - 12 May '03) Module 2: Meetings (cont.) ** Course Project Selection and Team Assignments: Due 12 May '03 ** |
|||
|
Practice your team working skills in our own class. You will be building an improvement plan as part of a team. TH Chapter 5 is a meaty chapter so we will spend this week and our short Week 6 examining it. MJ's Storyboard Case Study (pp. 115-131) is also called the Problem-Solving/ Process-Improvement Model. Here you see a variety of techniques organized to explore, explain, document, and improve a process - and then document the improvement. Some of the techniques we have not covred yet, but that is ok. The objective of the Storyboard, as with Appendix B of TH, is to provide you with an example of how to use the tools we are studying. Use this week to finalize your preliminary planning for your Course Project. Work with the implementation or advisory team to make sure you are on a clear, directed path. |
|||
| Texts: Review: TH Chapters 2 & 5 and Appendices B & C; MJ Working with Teams see MJ Tool Selector chart, pg. vii. - especially the Improvement Roadmap (Storyboard Case Study); study electronic handouts. | |||
| Turn In & Participate: | |||
Individual
Work:
|
Group
Work:
Course Project Teams must be fully formed. This includes those that will conduct a joint project and those that will advise others on their projects. |
||
|
We complete Module 2 and TH Chapter 5. |
|||
|
Texts: Review: TH Chapters 2 & 5 and Appendix C; MJ Working with Teams; Handouts. |
|||
| Turn In & Participate: | |||
Individual
Work:
|
Group
Work:
Apply Process Analysis tools to Module Exercises. |
||
|
Week 7 (17 - 23 May '03) Midterm Exam "Week" ** Journal.2 due NLT 23 May '03 ** |
|||
|
Review for the Midterm Exam. |
|||
| Text: Review prior assigned material, WebTycho conferences, and your notes. | |||
Individual
Work:
|
Group
Work:
None |
||
|
We return refreshed, I hope, with new ideas and observations about improving Information Systems processes in our workplaces. We skip Module 3 (Leadership) for now and move on to Module 4. Many of you will be familiar with reductionist strategies - divide and conquer strategies that we use in programming are among them. We take a huge problem that no one can solve and tear it apart, hoping that we can remember where we started, why, where we are going, why, how we might put the pieces back together, etc. The strategies we look at here will help us reduce problems to manageable proportions, keep track of where we have been and are going, and see the bigger picture as well (holistic strategies). We start off with simple checksheets, run charts, plotting data points, making histograms, and Pareto charts. Enjoy. |
|||
| Texts: Study: TH Chapter 2; study MJ Working with Numbers see MJ Tool Selector chart, pg. vii. - especially Checksheets, Run Charts, Data Points, Histograms and Pareto Charts; study electronic handouts. | |||
| Turn In & Participate: | |||
Individual
Work:
|
Group
Work:
Apply Process Analysis
tools to Module Exercises. |
||
|
Week 9 (17 - 23 June '03) Module 4: Scientific Techniques (cont.) |
|||
|
This week we will look more closely at other quantitative techniques. In particular we will look at continual process improvement techniques such as control charts, process capability, scatter diagrams, and Kaizen methods. |
|||
| Texts: Review: TH Chapter 2; complete your study of MJ Working with Numbers see MJ Tool Selector chart, pg. vii. - especially Control Charts, Process Capability and Scatter Diagrams; study electronic handouts. | |||
| Turn In & Participate: | |||
Individual
Work:
|
Group
Work:
Apply Process Analysis tools to Module Exercises. |
||
|
Week 11 (1 - 7 July '03) Module 3: Leadership ** Journal.3 due NLT 7 July 2003 ** Complete course Critique on WebTycho |
|||
|
If there is one subject in the military that we hear too much - and too little - about, I suspect it is leadership. Everyone has their own approach. So do not assume you have heard this all before. Again, please pay attention to your author's insights. Then critique and research to find support for your own views. |
|||
|
Texts: Study: TH Chapter 6 & Appendix A. |
|||
| Turn In & Participate: | |||
Individual
Work:
|
Group
Work:
Your Course Project team should be busy with preliminary reviews of project plans (process improvement planning). |
||
| Week 12 (8 - 14 July '03) Module 3: Leadership (cont.) | |||
|
I know this is a short spin around such a large topic, but if you are interested in learning more, we have other UMUC courses that cover this area in much more detail. |
|||
|
Texts: Study: TH Chapter 7. |
|||
| Turn In & Participate: | |||
Individual
Work:
|
Group
Work:
TBD. |
||
|
Week 14 (19 - 25 July '03) Final Exam Week. ** Course Project Report: Due 21 July 2003 ** ** Journal.4 due NLT 21 July 2003 ** |
|||
|
Course Review, Wrap-up & Final comments, Course Critique, etc. |
|||
| Text: Review prior assigned material, WebTycho conferences, handouts, and your notes. | |||
Individual
Work:
|
Group
Work:
None |
||
Weekly Assignments
Week 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14Final Exam Special AssignmentsCourse Project Due:
Topic and Team | Report
Week 1 Group Assignment IFSM-302 Index Page Index to Phil's IFSM-302 Postings
| Phil Richardson; prichard@faculty.ed.umuc.edu | Revised 17 Apr. 2003 |