Upload
others
View
0
Download
0
Embed Size (px)
Citation preview
“Ge$ng to More” Computer Science PD
Design Studio April 26, 2013
Goals for our “Design Studio”
1. Learn Together. Network with leaders in the field. 2. Recognize Characteris5cs of Good PD. Explore
lessons from math and science, and generate consensus around common values for good CS PD.
3. Iden5fy Strategies for Improvement. What strategies can we use to deepen/scale/broaden impacts?
4. Outline Implica5ons. What does it mean for our individual work and the field writ large?
5. Develop Ac5on Plans. What will each of us do to improve our work for the future?
To promote learning and sharing so we can all improve, we must…
1. ParOcipate AcOvely 2. Listen ARenOvely 3. Be Candid 4. Build on the Ideas of Others 5. RespecYully Challenge One Another’s Ideas 6. Recognize the Needs of Others 7. Be Open to New Ideas
I got… I valued… I need… • Specific
techniques • New people
• Respect • Trust • Community
ExperOse
• Money • Time with
my team to process
• Common Tools
Agenda – Day Two
Working with School Districts ReflecOon AcOon Plans Final Thoughts EvaluaOon
Agenda – Day Two
Working with School Districts ReflecOon AcOon Plans Final Thoughts EvaluaOon
Working with School Districts Cameron Fadjo Director of So4ware Engineering Educa7on, Office of Postsecondary Readiness, New York City Department of Educa7on
Charity Fesler STEM Project Specialist, Office of Curriculum and Instruc7on, D.C. Public Schools
Brenda Wilkerson Program Manager for Informa7on Technology, Office of Career and Technology Educa7on and STEM High Schools, Chicago Public Schools
Tables/Groupings Table 1 Table 2 Table 3
Baxter, D. Frankie, T. Pollock, L.
Koch, M. Meloy, T. DeRori, L. Yanek, D.
Gray, J. Muralidhar, D.
Lee, I. Psaila-‐Dombrowski, M.
Allen, R. White, L.
Greenawalt, J. O'Grady-‐Cunniff, D.
Hu, H. Lyman, C.
Chapman, G. Washington, A.
Bort, H. Brylow, D. Gibbs, D.
Table 4 Table 5 Table 6 Astrachan, O.
Diaz, L. Osborne, R. Cambridge, D. Rasmussen, C..
Garcia, D. Harvey, B. Morelli, R. Uche, C.
Ericson, B. Furman, C. Brown, B. Kind, B.
Baker Franke Chair, Computer Science Department University of Chicago Laboratory
Schools
Pu$ng it all together
Team ReflecOon
Team Poster
Collegial Feedback
Make a Plan
Team Reflec5on
1. Reconvene with your team member. 2. As a pair, discuss the following.
a. What about your PD are you most proud of? b. What areas do you most want to improve? c. What strategies will you use to make that
improvement happen? d. What are the biggest barriers you face?
3. Make a poster…
Team Reflec5on Poster What we’re proud of:
What are three areas you would like to improve in? 1. 2. 3.
What strategies are you going to do to address those areas: 1. 2. 3.
What are the biggest barriers?
Collegial Feedback 1. Pair up with another team (pairs on next slide) 2. With the other team take turns presenOng [10 min each]:
a. Reminder of current PD design from flash talk templates. b. Use poster to discuss key changes to PD design that address
your PD’s less-‐to-‐more issues c. Discuss strategies and possible implementaOon d. Other team provide feedback, ask hard ques+ons and
respec0ully challenge ideas. e. Switch
3. As a Table: a. Choose a speaker b. IdenOfy 3-‐5 ideas worth sharing
Whole Group Discussion
1. Each table will share out 3-‐5 ideas. 2. Whole Group Q & A.
Jean Westrick Associate Director, 100Kin100 STEM
Project, Urban Educa7on Ins7tute (UEI) at the University of Chicago
These are plans for you.
These are plans for you for one year.
We’d love to see
these, if you’d
care to share!
What will you do to improve over the next year?
What goals will you make to “move from less to more”? Be mindful of ways you can focus on: • Improving coherence • Addressing the needs of classrooms • Customizing to the needs of teachers • PD Design
Be SMART about what you want to change:
• Specific (and strategic): Linked to mission, overall goals and/or strategic plans.
• Measurable: Can be measured.
• A\ainable: Is realisOc and reasonable and can be achieved given context.
• Relevant: Is aligned with current projects/needs.
• Time-‐bound: Has a clear Omeframe and deadline.
Plans should meet several criteria.
• Completeness. Does it idenOfy/list all the acOon steps needed to impact your goal?
• Clarity. Have you clearly idenOfied who will do what by when?
• Current. Is the plan reflecOve of current needs? Have you anOcipated opportuniOes and barriers?
Note: Ac7on Plans are “living” documents that should be revised as needed.
Ac5on plans should clearly iden5fy:
• What acOons or changes will occur? • Who will carry out these changes? • When will they take place, for how long? • What resources, including money, staff, etc., are needed to carry out these changes?
• Communica+on. Who should know what and how?
• Poten+al Barriers. What things might challenge your success? How might you overcome them?
With your team member…
1. Spend the first 5 minutes, and idenOfy the area(s) of improvement you want to address.
2. For each, dras a SMART goal. 3. StarOng with where you want to end up,
outline the steps needed to get you there. 4. Each acOon step represents a milestone—
think “key deliverable.” 5. If you’d like, share your work via Dropbox.
Michael Lach Director of STEM Policy and Strategic
Ini7a7ves, Urban Educa7on Ins7tute at the University of Chicago
Baker Franke Chair, Computer Science Department University of Chicago Laboratory
Schools
Goals for our “Design Studio”
1. Learn Together. Network with leaders in the field. 2. Recognize Characteris5cs of Good PD. Explore
lessons from math and science, and generate consensus around common values for good CS PD.
3. Iden5fy Strategies for Improvement. What strategies can we use to deepen/scale/broaden impacts?
4. Outline Implica5ons. What does it mean for our individual work and the field writ large?
5. Develop Ac5on Plans. What will each of us do to improve our work for the future?
Meta
1. Consider goals and contexts.
2. Different strategies target different needs.
3. Lead by example.
1 2 3 4 5 5 n
Thank you!
Thank you!
Thank you!