# Start scoping problems

At the start of the scope-a-thon, community partners should share their background presentations and announce their priority challenges. Once participants have had a chance to hear from each community partner, they should separate into medium-sized groups to begin discussing the details of partners' challenges.  

### Set expectations early

It's easy to get swept up in the excitement of biting into a new challenge. When the potential for a technological or data solution is presented, there can sometimes be an eagerness to apply the most innovative technology first. As University of Chicago's Civic Scope-a-thon keynote speaker Matt Gee pointed out, this is also known as the Peak of Inflated Expectations. 

![Credit: Gartner](https://1060224550-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LT-3LNTAsA_rjnEu_Uq%2F-LT0FNf8yp-yDbUllhcD%2F-LT0LeOJ8r0og1rGjhLX%2Fimage.png?alt=media\&token=23845503-a1a7-4c3f-aba9-9f4ec6b57ca7)

However, stepping back from expectations to listen and learn about the real challenges that communities face can be both a daunting and humbling experience. Project participants should challenge themselves to set aside assumptions and listen openly to the expertise of community partners who have on-the-ground experience with local problem-solving.  

### Guidance for team discussions

First, assign each team a facilitator. Facilitators can help guide teams through the discussion topics outlined below. Facilitators should remember to be neutral, keep discussions focused, and resolve disagreements equitably with a focus on moving forward. [Here is some sample guidance for facilitators.](https://docs.google.com/document/d/1VJDxqGwQTY3gjo5aeQrKLmtfSva-CC3UySpCZVFtpsQ/edit?usp=sharing)

Ultimately the day's goal is for each teams to put together a **10-minute presentation** outlining the challenge their team aimed to tackle, and the data-driven solution they'd like to propose. 

Once teams have been assembled, they should walk through each of the discussion topics below, starting with aligning around the partner organization's mission and desired impact. Teams should work through the discussion topics below throughout the day, spending extra time on scoping the final tools and solutions, and crafting a presentation. 

{% hint style="info" %}

#### Proposed discussion topics

1. Understand the organization's mission and desired impact
2. Identify essential stakeholders and challenges
3. Understand stakeholders' critical information needs
4. Understand and explore available data, including open data and organization's internal data
5. Select appropriate tools and methods for solutions
   {% endhint %}

### Present and evaluate solutions

Once teams have spent time discussing the nuances of challenges, they should present their final solutions. Presenters should be open to a discussion about the feasibility, impact, and sustainability of their proposed solutions. 

Conveners can invite judges to help evaluate proposed solutions. Judges with subject matter or local expertise can ensure that solutions are feasible, particularly if scope-a-thon offers project support for winners. Below is a sample rubric that judges might use to evaluate presentations.

| **Topic**                | Score | **Assessment**                                        |
| ------------------------ | ----- | ----------------------------------------------------- |
| **Problem articulation** | 1-20  | **Problem is well-defined.**                          |
| **Mapping the Data**     | 1-10  | **Team used or proposed creative use of data.**       |
| **Mapping the Solution** | 1-10  | **Likelihood of implementation of solution is high.** |
| **Overall presentation** | 1-10  | **Presentation was clear and compelling.**            |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://sunlight-open-cities.gitbook.io/playbook-open-data-scope-a-thon/start-scoping-problems.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.