| Home | General Info | Getting In | Policies | Calendar | Contact Info | Handouts | Teams | Project |
| Home | General Info | Getting In | Policies | Calendar | Contact Info | Handouts | Teams | Project |
The case study is intended to give you an opportunity to
apply the concepts of the course in the context of a "real" business
situation. Each of the cases are based on a key situation or event in the
history of a high tech company. The cases we will cover in E145 are:
On specified rotating days, students will either be required to submit group or case analysis to e145-homework@lists.stanford.edu.
Submissions should reflect an understanding of the critical issues of the case,
integrate the material covered in class and present concise and well reasoned
justification for the stance that the group takes. Each case
analysis should consist of a POWERPOINT DECK WITH 6 SLIDES MAXIMUM as follows (Yahoo example is inserted here):
Slide 1: Team photos and names of team members plus the team name (for example, Team XXX DART of Yahoo! 1995 case, for E 145 October 1, 2007)
Slide 2: Your decision(s): answer Jerry and Davefs decisions in the case.
Slide 3-5: Analysis: Any quantitative and qualitative analysis to support your decision. Use the readings for the day. Find two or three tools that seem to apply. Apply them.
Slide 6: Reality Test: Identify 3-5 of the biggest risks facing Yahoo!. How will you manage those risks? What is a contingency plan if your game plan fails?
Excel workbook: Two pages not larger than 8.5 inches by 11 inches with font we can read. Do tables, graphs of any of your quantitative analysis to support your decision. Use the tools from your readings and the workshop that we will conduct, as well as any tools from your other courses that apply. Make sure your assumptions are clearly documented. Cite any sources of tools you use in a footnote.
DART = Decisions + Analysis + Reality Test
This framework will be the way that you do case openings and that the teaching team grades them.
For background and context,
please read a description of the case method prepared by Fred Gibbons. For
an additional perspective, read notes on the case
method by K. Davis.
Team case assignments
should be prepared as a team, but only one submission is required per group.
Assignments should be
submitted via e-mail no later than 9 am the morning of the corresponding
session in class to e145-homework@lists.stanford.edu.
The teaching team reads each powerpoint before class starts to optimize that session's learning environment. Grading is on a "plus(+)/check/minus(-)" basis. The instructors will often post several submissions to stimulate further on-line discussion.
Submission Format Guidelines
1. PUT IN EMAIL HEADER: Assignment no.
Team Name. Section no.
i.e. Email
Assignment 1 The Hills 3:15
Avoid common errors in online assignments, case analyses and other submissions, such as:
1. Focusing too heavily on minor issues or those on which there are little data.
2. Lamenting because of insufficient data in the case and ignoring creative alternatives.
3. Rehashing of case data -- assume the reader knows the case.
4. Not appropriately evaluating the quality of the case's data.
5. Obscuring the quantitative analysis, making it difficult to understand.
6. Typical "minus(-)" grades result from submissions that
o are late
o exceed the sge limit
o are not well integrated and lack clarity
o do not address timing issues
o do not recognize the cost implications or are not practical
o get carried away with personal biases and are not pertinent to the key issues
o are not thoroughly proofread and corrected.
