|
Project Management - IBMGT-487 (3) |
University of Maryland
University College Electronic Distance Education Heidelberg, Germany |
| DE Term 5, 2001-2002; Dates: 10 June - 4 October 2002 | ||
|
|||||||||||
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.
The Modules in our WT classroom provide you with a general outline for this course which is broadly the same as your text. However, we will spend more time on Module 3 than either of the other two. I will make assignments from your text and the modules, so you will need to refer to both.
Please also make use of the Student Companion site for your text. (See http://jws-edcv.wiley.com/college/tlp/0,9842,BUSC-DSC-DS21C_0471298298_BKS,00.html) I will make assignments from that site from time to time.
| Week 1 (10 - 15 June '02) Course Intro & Orientation | |||
|
See Week 1 Group Assignments and Week 1 Individual Assignments |
|||
|
Text: Review
Table of Contents and Preface of your book |
|||
|
Turn In & Participate:
|
|
Week 2 (16 - 22 June. '02) (Module 1) Overview & Project Initiation |
|||
|
Many of us participate or lead project activity regularly. We do not stop to analyze and understand the degree to which project activity differs from our "normal" job - but we know we have to do both. The first
chapter of the text gets us oriented. The second chapter allows us to
look at several project selection models. It also introduces us to the
issue of risk and uncertainty which are much more common for projects
than for routine organizational activity.
|
|||
|
Study:
Text:
Chapters 1-2. (Note: Assignments include the Directed Readings
at the end of each chapter.) |
|||
| 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: Text Chapter Incidents for Discussion |
||
|
Week
3 (23 - 29 June '02) (Module 2) Project Initiation
(continued) |
|||
|
By now everyone should have your textbook and be well into the course. If you do not have your text by now, please send me an email. Module 2 has a simple title - People. Pay close attention. People make all the difference. Project Managers are not always around for the selection phase of a project. But hopefully they come on board very quickly after that at least. Chapter 3 explains many of the issues activity leaders must consider when selecting a project manager. You have seen in your prior course work how organizations structure themselves to carry out their normal functions. Chapter Four shows you how project organization is different. Government organizations, particularly the DoD, have long been help up
as the model for one of the most complex types of organization - the matrix.
This chapter will perhaps help you understand why this structure has evolved
and why projects seem to fit so easily into our method of working. Topics:
|
|||
|
Study:
Text:
Chapters 3 & 4; Appendix B. |
|||
| Turn In & Participate: | |||
Individual
Work:
|
Group Work: Incidents for Discussion Module Cases 1-4 |
||
|
Week 4 (30 June - 6 July '02) (Module 2) Project Initiation (continued) |
|||
|
Some of you may have thought that we would start the course here. After all, planning comes first, right? Not really. First comes preplanning as you have seen in the prior chapters. If the preplanning is good, then you can move on the the planning. Chapter Five introduces you to a key concept - projects do not exist in a vacuum. Projects are typically part of complex systems and must be tied into the environment via a complex web of communications. Also in this chapter you see one of the guiding tools for the project manager - the Work Breakdown Structure. This highly structured document, key to organized activity and audit trails, actually flows from a more narrative document called a Statement of Work which is often provided by the customer with a Request for Proposal. If you have been avoiding charts and graphs up to now, please dive in head first. We use graphical aids extensively in project management. You need to learn how to make them your best friends. Negotiations are central to project management - as is conflict. Your authors present an excellent review of both in Chapter Six. Topics:
|
|||
|
Study:
Text:
Chapters 5 & 6. |
|||
| Turn In & Participate: | |||
Individual
Work:
|
Group
Work: Incidents for Discussion Module Cases 5-7 & Exercises A & B |
||
|
Show me the money. More correctly, show me what you plan to do with my money. A budget is a plan and project managers live by plans and controls. The section on improving cost estimation takes you into some quantitative methods that will be useful in other applications as well. Topics:
|
|||
|
Study:
Text:
Chapter 7. |
|||
| Turn In & Participate: | |||
Individual
Work:
|
Group
Work:
Incidents for Discussion Module Case 8 |
||
|
Week 6 (14 - 19 July '02) (Module 3) Project Implementation (continued) |
|||
|
Performance, time, cost - the three bywords of the project manager. This week we look more closely at how to keep time on track. But of course we find that time, cost and performance are all interrelated. You may have seen the PERT or CPM method in another course. You will get a strong dose of both here. It is time to break out your Microsoft Project 2000 disc and become familiar with it. Your 120 day trial will take you past the end of the course. Use the tutorials. Visit the web site. Topics:
|
|||
|
Study:
Text:
Chapter 8. |
|||
| Turn In & Participate: | |||
Individual
Work:
|
Group
Work:
Incidents for Discussion Module Cases 9 & 10 |
||
|
Week 7 (20 - 26 July '02) Midterm Exam "Week" ** Journal.2 due NLT 26 July '02 ** |
|||
|
Review for the Midterm Exam. |
|||
| Text: Review prior assigned material, WebTycho conferences, and your notes. | |||
Individual
Work:
|
Group
Work:
None |
||
| Week 8 (17 - 24 Aug. '02) (Module 3) Project Implementation (continued) | |||
|
Welcome back. It is now time to start our course project. You have enough tools and you have completed more than half the text. See my separate message on this tasking. Chapter Nine shows us that there is more than one way to skin a cat - or complete a project on time, under budget, with a happy customer. Well, perhaps just a little over budget - a little late - and with a few frowns all around. One thing you can count on - change. Your plan will be adjusted many times and often not because you want to make the changes. So you need to learn how to react to change in an effective manner. Plan ahead. Know where you can save time and money. Know where you cannot. Topics:
|
|||
|
Study:
Text:
Chapter 9. |
|||
| Turn In & Participate: | |||
Individual
Work:
|
Group
Work:
Incidents for Discussion Module Case 11
|
||
|
Week 9 (25 - 31 Aug. '02) (Module 3) Project Implementation (continued) |
|||
|
We had reporting and monitoring systems long before we had computers. But computers do make such systems more capable and responsive. Unfortunately, there are still people in the middle and often at each end. So imperfection is inevitable. Topics:
|
|||
|
Study:
Text:
Chapter 10. |
|||
| Turn In & Participate: | |||
Individual
Work:
|
Group
Work:
Incidents for Discussion Module Case 12 Weekly Term Project Report |
||
|
Week 10 (1 - 7 Sep. '02) (Module 3) Project Implementation (continued) ** Journal.3 due NLT 7 Sep. 2002 ** |
|||
|
If it is not measured, it is not controlled, so they say. But controls can be threatening. It is so each to control what is easy to measure. But it is not so easy to measure or control the most important aspects of any project. Moreover, we do not want to stem the creativity of our workers as we try to keep them and the project pointed and moving in the right direction. By now you are well aware of some of the ways that projects just seem to get bigger. This is only one of many areas that must be controlled. This is another useful chapter from your authors. Topics:
|
|||
|
Study:
Text:
Chapters 11. |
|||
| Turn In & Participate: | |||
Individual
Work:
|
Group
Work:
Incidents for Discussion Module Case 10 Weekly Term Project Report |
||
|
Week 11 (8 - 14 Sep. '02) (Module 3) Project Termination Complete course Critique on WebTycho |
|||
|
Managers just love audits, right? Well, maybe not. But auditors love audits, right? "Depends" is the best answer, I suspect. Witch hunts help no one. We need an audit to help us learn how to conduct projects better next time. Be prepared to audit early and often to help you as a project manager learn from mistakes and still complete your project to the customer's satisfaction. Yes, I know, you boss has to be happy too. Topics:
|
|||
|
Study:
Text:
Chapter 12. |
|||
| Turn In & Participate: | |||
Individual
Work:
|
Group
Work:
Incidents for Discussion Weekly Term Project Report |
||
| Week 12 (15 - 21 Sep. '02) (Module 3) Project Termination (continued) | |||
|
Some projects seem endless. You have probably seen a few. Ever present for years then slowly they fade into the background. But there always seems to be someone assigned to the project team or to complete "Items of Interest" on key project objectives. Knowing when and how to call a halt saves more than money. It releases people to do other things and helps fellow workers know that there is a Santa Claus. Keep projects alive past their "Sell By" date steals resources from other parts of your firm and your workers know this. They pay the price more than anyone else. Pay attention to the lessons of Chapter 13. Don't miss the Final Report. Your term project will have one. Topics:
|
|||
|
Study:
Text:
Chapter 13. |
|||
| Turn In & Participate: | |||
Individual
Work:
|
Group Work: Incidents for Discussion Module Cases Exercise C Weekly Term Project Report |
||
|
Use this week to finish up your course project and review for your final exam. |
|||
|
Study:
Text:
Epilogue and Review. |
|||
| Turn In & Participate: | |||
Individual
Work:
|
Group Work: Course Project |
||
|
Week 14 (28 Sep. - 4 Oct. 2002) Final Exam Week. ** Journal.4 due NLT 4 Oct. 2002 ** |
|||
|
Course Review, Wrap-up & Final comments, Course Critique, etc. |
|||
| Text: Review prior assigned material, WebTycho conferences, 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
Final Report Due
Week 1 Group Assignment BMGT 487 Index Page Index to Phil's BMGT 487 Postings
| Phil Richardson; prichard@faculty.ed.umuc.edu | Revised 9 June 2002 |