 | schedule | projects | overview | tips 2008 - 2009 Team Project Schedule | October | Form teams, "brainstorm" | | December | Conference call "check in" (December 4, 2008 9:00-10:00 a.m.) | | January | Submit written report: (January 5, 2009) - Name of project
- Name of group members
- Goals and Objectives (short for web-site)
| | January | Present short report on progress (January 14, 2009) | | March | Conference call "check in" (March 17, 2009 9:00-10:00 a.m.) | | March | Submit written report (March 31, 2009) - One page abstract (form attached) - please submit in abstract format per sample. This is the only way we can submit them for consideration.
- Use no smaller than 11 pt. font
- Do not repeat title information in body of abstract
- Sample included for reference
| | May | Present final report (written and oral) (May 6, 2009) - Alumni will be present
- 5-10 Minutes per report
- Reports will not be allowed to exceed time limit
|
back to top 2007 - 2008 Team Projects ALABAMA
Title: Members: Goals and Objectives: ARKANSAS
Title: Members: Goals and Objectives:
LOUISIANA
Title: Members: Goal: Objectives: LOUISIANA Title: Members: Goals and Objectives:
MISSISSIPPI
Title:
Members: Goal and Objectives: MISSISSIPPI Title: Members: Goals and Objectives: back to top
2008 - 2009 Team Project Overview | Form groups prior to (or no later than) October meeting | Select topic at October meeting - topic should be relevant to state/region
- topics should not be too broad
| | Groups should consist of approximately 5 people | | We encourage regional groups. Regional projects represent one of the reasons for establishing a regional institute. However, anyone considering a regional project should be aware of the logistical difficulties of collaborating with individuals across 4 or 5 states. | Team projects should be beneficial to the state (or region) - groups are encouraged to pursue their project beyond the Institute
- presentation at the local level, state meetings, APHA
| A defined project/report is expected for presentation and distribution at last on-site meeting - should provide enough copies for all participants (40), Institute staff (3-4), state level (?), and as many copies or executive summaries as possible for alumni attending presentations
| Funding for projects is at the state level - expenses for additional meetings if necessary
- producing reports
| | Process is as important as the product | In planning and developing your project, please consider - what role leadership played in your project
- how did the project help build public health infrastructure?
|
back to top Team Project Tips
(Provided by SCPHLI Alumni) | I. | Dispel fear of projects - public health staff are very resourceful
- already involved in projects/activities that can serve as a starting point for ideas
| | II. | Have group discussion - what is everyone currently doing/involved in
- hot topics
- new ideas
- passions
- strategic planning/direction of agency
| | III. | Make a list - identify possible topics/projects
- determine how much background info is available/needed
- research/check out additional info
- reevaluate possibilities
| | IV. | Develop goals & objectives - what is the overriding mission/goal of project
- should have 3-4 objectives
- break tasks into measurable/incremental pieces with time lines
- assign responsibilities
| | V. | Some ground rules - someone should serve as a facilitator - at least initially
- NEVER leave a meeting without another meeting or activity date set
- take initiative and learn new things
- use your innate skills
- utilize other resources/staff
- if you look for an excuse not to do something, there are dozens available
|
back to top | | |
