Hi Class,
Your deliverable consists of a 40 slide PPT (excluding appendices). Should be emailed to me with a copy to the AAs before deadline: 27-Nov 6 pm.
More specifically, your PPT should contain:
1. Filename (mandatory) - should be of the form group_name.pptxwhen submitted.
2. Title slide (mandatory) - Project title - something concise but informative that describes the gist of what you've done. In addition, the title slide should also contain your Group Name, Team-member names, PGIDs MKTR section.
Pls note, make no mention of your team member names anywhere else in the PPT, have it only in the title slide.
3. Presentation Outline (Optional) - a Contents page that outlines your presentation structured along sections (e.g. methodology, [...] , recommendations, etc).
4. Decision Problem(s) (Mandatory) - State as clearly as feasible the decision problems (D.P.s) you are analyzing Give numbers to the D.P.s if there're more than one.
If small enough in number, you may also list the R.O.s you have in this slide.
5. A Methodology Section (Mandatory) - In preferably a graph or flowchart form, lay down what analysis procedures you used, in what order to answer particular Research Objectives (R.O.s) that cover the D.P.s.
6.A Data section (Mandatory) - explains that nature and structure of the data that were used. Be very brief but very informative - write (ii) the dimensions of the data matrices used as input to in different procedures, and (ii) the sources of data - cited sources if secondary data are used, and Question numbers in the survey questionnaire if primary data are used.
I strongly suggest using a tabular format here. Packs a lot of info into compact space. Easy to read and compare too.
Some clue as to what filters or conditions were used to clean the data would be very valuable also.
7. Model Expressions (Mandatory)- Write the conceptual and/or mathematical expressions of any dependence models used. Then directly use the results in downstream analysis.
Kindly place in the appendix section a descriptives table of the input data, a brief explanation of the X variables used, and of course, output tables along with interpretation.
8. Appendix Section (Optional): Some of the less important tables can be plugged into a separate appendix section (outside the 40 slide limit) in case you are running out of slide space. Have only the most important results tables in the main portion.
9. Recommendations (Mandatory) - crisp, clear, in simple words directed towards the client. Emphasize the usability and actionability of the recommendations.
Further, I strongly advise groups to make their PPT deliverables reader-friendly. That is:
- use as simple language as feasible.
- Animate the slides if they are cluttered so that when I go through them later, the proper sequence of material will show up.
- Highlight keywords and important phrases.
- Use callouts etc as required to call attention to particularly important points.
- An economy of words (sentence fragments for eaxmple) is always welcome.
I hope that clarifies a lot of issues with deliverable format. Groups that flout these norms may lose a few points here and there.
Sudhir
Your deliverable consists of a 40 slide PPT (excluding appendices). Should be emailed to me with a copy to the AAs before deadline: 27-Nov 6 pm.
More specifically, your PPT should contain:
1. Filename (mandatory) - should be of the form group_name.pptx
2. Title slide (mandatory) - Project title - something concise but informative that describes the gist of what you've done. In addition, the title slide should also contain your Group Name, Team-member names, PGIDs MKTR section.
Pls note, make no mention of your team member names anywhere else in the PPT, have it only in the title slide.
3. Presentation Outline (Optional) - a Contents page that outlines your presentation structured along sections (e.g. methodology, [...] , recommendations, etc).
4. Decision Problem(s) (Mandatory) - State as clearly as feasible the decision problems (D.P.s) you are analyzing Give numbers to the D.P.s if there're more than one.
If small enough in number, you may also list the R.O.s you have in this slide.
5. A Methodology Section (Mandatory) - In preferably a graph or flowchart form, lay down what analysis procedures you used, in what order to answer particular Research Objectives (R.O.s) that cover the D.P.s.
6.A Data section (Mandatory) - explains that nature and structure of the data that were used. Be very brief but very informative - write (ii) the dimensions of the data matrices used as input to in different procedures, and (ii) the sources of data - cited sources if secondary data are used, and Question numbers in the survey questionnaire if primary data are used.
I strongly suggest using a tabular format here. Packs a lot of info into compact space. Easy to read and compare too.
Some clue as to what filters or conditions were used to clean the data would be very valuable also.
7. Model Expressions (Mandatory)- Write the conceptual and/or mathematical expressions of any dependence models used. Then directly use the results in downstream analysis.
Kindly place in the appendix section a descriptives table of the input data, a brief explanation of the X variables used, and of course, output tables along with interpretation.
8. Appendix Section (Optional): Some of the less important tables can be plugged into a separate appendix section (outside the 40 slide limit) in case you are running out of slide space. Have only the most important results tables in the main portion.
9. Recommendations (Mandatory) - crisp, clear, in simple words directed towards the client. Emphasize the usability and actionability of the recommendations.
Further, I strongly advise groups to make their PPT deliverables reader-friendly. That is:
- use as simple language as feasible.
- Animate the slides if they are cluttered so that when I go through them later, the proper sequence of material will show up.
- Highlight keywords and important phrases.
- Use callouts etc as required to call attention to particularly important points.
- An economy of words (sentence fragments for eaxmple) is always welcome.
I hope that clarifies a lot of issues with deliverable format. Groups that flout these norms may lose a few points here and there.
Sudhir
No comments:
Post a Comment
Constructive feedback appreciated. Please try to be civil, as far as feasible. Thanks.