# data[].attributes.body
school norms

trust, respect, responsibility

professional behavior by ALL

*This needs to be an intergal part of your classroom!
How do we create change if we don't model it for our students?

# data[].attributes.body
You should bring the following to your peers when you participate in critical friends:
1. Standards and skills you hope to cover.
2. The driving question that you created and the problem statement you hope the kids will create.
3. A rough draft of the entry event.
4. A rough draft of the project planning statement.

* Do your students know/will they know, what you need them to know?!

# data[].attributes.body
Let students know during the first week (possibly day 3) about the benchmark and focus on what the need to knows around it are...perhaps grading for agency and oral communication for the first benchmark, not knowledge and thinking?

# data[].attributes.body
* Don't put 3 people in a group if the task doesn't require 3 people?
Reflect on how the task...how many people do you need in the group?

# data[].attributes.body
What are the benchmarks or big check ins for the project (writing, revision, etc.)?
What are the need to knows for your students and how do you scaffold, create assignments, and run workshops for the need to knows?

# data[].attributes.body
lhenry@newtechnetwork.org
http://newtechnetwork.org/resources/pblchat-project-rollout-101/
recording of PD: https://newtechnetwork.adobeconnect.com/p6qv8ivhot9/?launcher=false&fcsContent=true&pbMode=normal

# data[].attributes.body
*You make the driving question, the students make the problem statement.
How do we as (role)________do(action)________, so that(justification)_________.
Who are you (going to be in this project?
What are you doing?
*The problem statement lets you know whether or not they understand the project.  If they can't find the problem, you need to go back and rework the entry event/entry doc.
*Even though they might be working on different aspects of the project, THEY SHOULD ALL HAVE THE SAME PROBLEM STATEMENT.
*Sometimes it's better to create the problem statement before the knows/need to knows.

# data[].attributes.body
....must produce:
1. the driving question
2. a problem statement
3. knows and need to knows
*Remember to leave breadcrumbs!

# data[].attributes.body
What are your SWLOs?
How authentic (who cares about this) is your project?
Have you given the students a role as part of your driving question?
Are you taking advantage of your community partners (local businesses) to create more authentic assignments?
Is your rubric content specific with 1 row of SWLOs? Is it based on your final product? Do you have several rubrics for different parts of the project?

# data[].attributes.body
*THERE IS NO PRE-TEACHING!
1. Entry Doc/Entry Event
2. Knows/Need to Knows
3. Problem Statement
4. Revisit Knows/Need to Knows
5. Next Steps (may take 3 days to get here) evolve based on earlier steps
6. Group Contracts
7. Rubric
8. Resources (library day, field trip, research time)
9. Teach (scaffold, workshops)
10. Collaborate (model with peers)
11. Assess (benchmarks, IAKTS, etc.)

*Always connect back to the need to knows in all phases.

# data[].attributes.body
ppt 8/30/16