Research-Practice Partnership (RPP) Development Workshops For CSforAll


This fall, NNERPP is excited to co-host two RPP Development Workshops to support research-practice partnership teams applying for NSF’s Computer Science for All (CSforAll) RPP solicitation.

Over one-and-a-half days, teams will develop a deeper understanding of what an RPP is, how to form and sustain one, and how to design an RPP project or proposal. In particular, these workshops will emphasize how to identify and refine the problem of practice your partnership seeks to address, strategies for how to carry out partnership research in support of the identified problem, evaluation questions related to improving your partnership efforts, and the kinds of data you will need to collect to inform and improve your project in a timely way. You will leave the workshop with a plan or outline for a project or proposal that you can further develop as an established team.


November 14-15

San Mateo, CA



Digital Promise


Application deadline:

October 18, 2019



November 21-22

Washington, D.C.



University of the D.C.


Application deadline:

October 18, 2019



(Note: The San Mateo link takes you to the host’s workshop registration site and the Washington, D.C. link directly to the application form for that workshop. This link will be updated once the Washington, D.C. registration site is activated.)



To apply, click on the “apply” button above for the workshop you’re interested in attending, once they are active. It will take you to that particular workshop’s registration and application page. Please submit the application form there. 

Teams will be notified about their acceptance shortly after deadlines noted above. If space allows, we will accept additional teams on a rolling basis thereafter.

Funds are available to support your team’s travel, lodging, and subsistence, as well as all workshop costs.


Eligible teams will:

  • Be able to describe how your RPP project will advance equity in CS education.
  • Have a basic idea of the shared area of interest or CS for All activity that you want to develop and implement together.
  • Consist of 3-4 individuals, including:
    • an educational researcher
    • an educational partner from an LEA/SEA, school network, or similar
    • a computer scientist or CS/CT expert
    • an optional fourth team member representing community partners, informal education partners, evaluators, or additional LEA/SEA or research team members

Priority will be given to full teams of four.

Questions? Please contact us here.





Our friends at the Research + Practice Collaboratory previously headed up several RPP Development Workshops for CS4All. See their workshop homepage here and partnership resources for CSforAll here.



To help you get started on the RPP literature, we invite you to explore the following NNERPP resources:

  • RPP Knowledge Clearinghouse: Our curated collection of the most relevant resources and artifacts related to RPPs, organized into 12 major topic areas
  • NNERPP Extra: Our quarterly magazine shares deep and reflective articles around pressing issues in education tackled by research-practice partnerships across the country, the impacts and use of such research on policy and practice, and high priority questions that consider how to engage in RPP work more effectively

We also highly recommend exploring these additional websites for their own important contributions to our knowledge around RPPs:


The National Network of Education Research-Practice Partnerships (NNERPP) is a professional learning community for RPPs in education whose aim is to develop, support, and connect research-practice partnerships in education to improve their productivity. We invite you to connect with us on our homepage and subscribe to our twice-monthly newsletter to receive regular updates from around the RPP field.


Connect with us:

This material is based upon work supported by the National Science Foundation (NSF) under grant #1946648. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the authors and do not necessarily reflect the views of the NSF.