Engagement sessions *

[widal001]

Summary

Members of the Co-Design Group and open source community have attended at least one event (per group)

Press release

We’re excited to announce the successful completion of the Collaborative Coding Challenge Pilot, which has laid the groundwork for a scalable framework to support future hackathons. This pilot event, conducted in a fully remote environment, brought together a select group of participants who engaged in innovative problem-solving and collaboration. The feedback gathered from this event will be instrumental in refining our processes and ensuring that future hackathons are even more impactful and inclusive. Participants praised the streamlined structure and the opportunity to contribute to the Grants.gov Open Source community, marking this pilot as a significant milestone in our ongoing efforts to foster innovation and collaboration.

We're also very happy to report on a successful first Co-Design Group session, where we engaged community members – especially those currently underserved and overburdened by the grantmaking process – in a collaborative workshop to get community input on which user needs we should prioritize for Simpler.Grants.gov. Fifteen community members attended this kickoff session, and 90% indicated that they would be excited to attend another session in the future.

Acceptance criteria

• [ ] Co-Design Group: At least one session has met of at least 10 representatives of communities currently underserved and overburdened by the grantmaking process, and attendees are compensated for their time and expertise.
• [ ] Collaborative Coding/Design Challenge (Alpha): At least one session has met with at least 5 people interested in open source contributions to the Simpler Grants.gov project, and attendees are compensated for their time and expertise.
• [ ] User research: At least 10 users participate in user research sessions and are compensated for their time and expertise.

Metrics

• [ ] Satisfaction: At least 50% of the attendees have indicated interest in attending another session in the future.
• [ ] Participation: Number of attendees for all events combined is greater than or equal to 25.
• [ ] Contribution: At least 2 new tickets are created in the backlog that were created due to user engagement.

Assumptions

Dependencies

[mxk0]

"Participation: Number of attendees for all events combined is greater than 25." <-- should be "equals 25"

[widal001]

"Participation: Number of attendees for all events combined is greater than 25." <-- should be "equals 25"

@mxk0 Good catch! I updated it to "greater than or equal to 25" to reflect the "at least" in the ACs and in case more folks wind up participating, but feel free to make it "equals 25" if you want to shoot for that number exactly.