1. Designing Your Project Output Achieving your objectives by targeting your audience Ken Peffers UNLV February 2004

2. Types of Project  Case study  Literature survey  Project proposal  Policy memorandum  System implementation

3. Case study  Audience managers and researchers  Objective to contribute to knowledge about a problem by studying what actors did in a particular situation, their reasons, and the outcomes  Note that a research case differs from a teaching case Research case uses case as data to investigate problem. Teaching case intended to stimulate discussion.

4. Case Study  Abstract Summarizes the whole paper in about 100-200 words. Independent of the paper  Introduction Problem Why is the problem important Method (case) Data collection (where and when etc.) Results Preview the remainder of the paper  Lit review Briefly review current research on this question  Case story Tell the story of the case, including all of the factors, reasons, and events leading up to the outcome  Discussion Inferences about a solution to the problem Managerial implications  Conclusions Lessons Limitations Research needed, etc.  References

5. Literature review  Most general kind of paper.  Purpose to explore a focused research area and to contribute to knowledge by drawing some conclusions about it.  Audience usually mixed managers, others  Structure as an article for a particular journal

6. Literature review  Abstract Summarizes the whole paper in about 100-200 words. Independent of the paper  Introduction Problem Why is the problem important Method Data Results Preview the remainder of the paper  Literature review Review of the literature should tell a story Develop a concept, framework  Discussion Inferences about a solution to the problem Managerial implications  Conclusions Lessons Limitations Research needed, etc.  References

7. Project Proposal  Audience: a specific group of senior executives  Objective to persuade toward a specific course of action

8. Project Proposal  Executive summary ¾ to 1 ½ pp. Independently complete  Project overview Statement of the problem, its significance, the general nature of the solution to be proposed, and cost  Problem definition Detailed description of the problem (opportunity) and its significance.  Alternative solutions Description, architecture, source, cost, benefits, risks Each alternative should be feasible; no “straw dogs” Comparison among alternatives  Recommendations Alternative solution recommended and why Recommendations to manage implementation, sourcing, and risks  Costs, schedules, personnel  References  Appendices Include material too detailed for body of the proposal

9. Policy Memorandum  Audience: senior managers  Purpose: to persuade managers to take a specific course of action other than to build a new system Here the word “policy” might be considered to be synonymous with “strategy” vs tactical  Paper structure same as project proposal, except that alternatives may not involve systems

10. System Implementation  Audience managers  Objective to report on the development of the system

11. Documentation for Implemented System  Executive summary ¾ to 1 ½ pp. Independently complete  Project overview Statement of the problem, its significance, the general nature of the solution to be proposed, and cost  Problem definition Detailed description of the problem (opportunity) and its significance.  Chosen solution Description, architecture, source, cost, benefits, risks  Implementation report How you managed implementation, sourcing, and risks  Post-implementation report Realized functionality Actual costs, schedule, personal resources  System documentation User manual Technical data  References  Appendices Source code Testing documentation Licenses, if any Include material too detailed for body of the proposal

12. Use of this Guide  Use templates as guide, not rule  Modify when convenient  What’s important Your objectives The audience’s objectives