Project+Reports


 * This is a place to write the project report**

We need a description of how we generated our sample plots.

What //n// value did USFS use, 110 or 64? Will we be getting new graph data? Based on land use?
 * __Questions for USFS__**

- Enhance and build upon generated report - Build some context within the presentation and report to anticipate questions - Sit down as a class, go through the entire report, find errors, questions, areas for improvement... - Create an outline: order/skelton (3 Apr) - Develop a list of potential questions audience members or readers might ask - and find the answers.

Content development Layout development (some overlap) Presentation development
 * __General Timeline:__**

__**Report**__ //Aesthetics//: Design, charts, tables, graphics, layout...the looks of the report Lisa Hannah

//Content//: Writing, data - Distribute sections for writing - Have one person in charge of editing for tone/grammar/unity - "specialists" for presentation would stem from those writing each section - develop "sidebar info" once layout team has a better idea

__**Groups**__

__**Executive Summary**__ Lisa and Hannah

__**Introduction**__ Sarah and Bethany

__**I/II Tree char/Urban forest cover**__ Sarah and Trent

__**Structural and Functional Values (VI)**__ Chris and Trevor

__**Air Pollution Removal (III) /Carbon Storage and Seq (IV)**__ Mary and Bethany

__**Potential Pest Impacts** **and Trees and building Energy Use**__ Lee and Jody

__**Appendix I - update**__ Hannah and Mary

__**Appendix II**__ general updates

- Start once we have a good amount of the report finished - Generate potential questions that we may get about the report and prepare answers - Build some context within the presentation and report to anticipate questions - Split up areas of expertise, certain people address specific questions - //**Need to organize areas of expertise**//
 * __Presentation__**

//Comfortable with public speaking//: Hannah, Lisa, Bethany, Trevor

Report Submittal Point Person: Sarah Presentation Development Team: Mary, Lee, Chris

__**Reference protocol**__ (Author, Date) in text keep references format at end

NOTE: Remember to change Tulip tree to tulip poplar and tar to asphalt include scientific names on first reference (Sarah may need to double check/edit this)

__**Schedule**__ TODAY April 16 - Each group will present status of research/report, give the class presentation on subject area - discussion about printing / final product


 * Sunday night.. April 20** - Content and bullets to Gmail account

- Compiled bullets for powerpoint for class tues (Mary?)
 * Monday April 21 (midnight)** – Sarah to submit first draft to Dr. Hess

- Determine who will present each slide, develop script - Dr. Hess gives edits back. Review in class?
 * Tuesday April 22** - Begin presentation development in class
 * Wednesday April 23** – Presentation development, run through

- Hannah and Lisa will use this draft to do layout formatting
 * Thursday April 24 ** - first run through of presentation - Grad students / audience will give comments

Saturday April 26 – Edits due to Sarah/Bethany Sunday April 27 – 2nd Report Draft to Dr. Hess Wednesday April 30 – Final edits from Dr. Hess to Lisa / Hannah Friday May 2 – Report to printers (if necessesary, may push this back pending class discussion) T uesday May 6 - 1-4pm, some food? FINAL REPORT / PRESENTATION  NEED TO SCHEDULE another run through day. Tuesday May 5?

..... PARTY at Bethany's


 * //People and Organizations to Acknowledge//**

Also include a sentence or two about what we're thanking them for.