The document announces a workshop on open co-creation involving NGOs, cultural activists, and civil society. It provides details on the workshop's goals (to inspire and guide the development of open projects), date/time (March 12 from 10am-5pm), location (online), and intended participants (professionals from the third sector/NGOs and end-users, partners of cultural/social institutions, developers, designers). The agenda includes discussions of open content/processes, examples of open projects, scenario forecasting for open projects, rapid prototyping through visual brainstorming, presentations and evaluation of prototypes, and establishing implementation backlogs.

1. We're @platoniq & @goteofunding
Working in (offline) methods for (open) co-creation

2. A space to work
& learn/document as well
What: Discussions and co-design activities around open content and
processes for digital/offline projects, involving the third sector, NGOs,
cultural activists and civil society.
Why: In order to inspire, guide and help the development of open
projects.
When: The 12th of March (10am - 5pm)
Where: Here (and documenation here http://goteo.titanpad.com/4 :)
Who: - Professionals from the third sector or NGOs & end-users
- Partners of cultural or social institutions
- Developers / programmers of applications
- Designers and creative minds of different fields
#opencocreation

9. Open/Public licenses
When it comes to Creative Commons

12. Now let's see some examples
& get inspired by them
Image source: opensource.com Under Creative Commons by-sa 2.0

19. By cutting & pasting “the old way”
Collaborative collage as the seed of a project

20. #0 Your role
What's your skill?
#opencocreation
#0 Your role
Contribute with your skills/knowledge

21. “Rules”
Minimum ones
We’re all passionate and constructive about the topic
[openness & digital/offline projects]
and take some responsibility for creating things out of that passion
with what we have handy, helping our shared knowledge.
1) Whoever comes is the right people
2) Whatever happens is the only thing that could have
3) Law of 2 feet: if you're are neither learning nor contributing
go someplace else
4) “Angiepolski” allowed :)
#opencocreation

22. #1 “Apptizer”
What's open out there?
#opencocreation
1) Group with people you know or not (6 per group)
2) Write down on a postit the name of one of your favourite
open app / website / project
3) Explain a la “P2P” in 2 minutes to someone else
4) Each pair has to choose only one (open) example!

23. a#1 “Apptizer”
Which criteria...
“How could this benefit society?”
“To what extent is replicable?”
“Why and how is this open?”

24. a#1 “Apptizer”
Which criteria...

25. #1 “Apptizer”
Which criteria...

26. #2 What if...
Scenario forecast
“Let's imagine and combine possibilities”
What would be basic actions and opportunities
of open viable projects we imagine together?
Write down scenarios in one sentence:
“[What if as a <type of user>]
[I could <specific action>]
[with <open content / tool>]
[so <collective benefit>]”
Use at least one verb, describing an action.
#opencocreation

28. #2 What if...
Let's narrow down possibilities!

29. #3 Rapid prototyping
Visual brainstorming

30. #3 Rapid prototyping
Visual brainstorming
#opencocreation
“Draw a first 2D version of basic interactions”
1) Work in small groups selecting scenarios and personas
2) Finish the description of end-users
3) Start selecting icons and place them on the whiteboard
around the selected personas
4) Draw connections and add designs (wireframe / process)
trying to reflect the most relevant relationships or interactions

31. #4 P2Presentations
And rapid evaluation

32. #4 P2Presentations
And rapid evaluation
#opencocreation
“Sharing progress and/or designs”
1) Present briefly (5 minutes) the work done,
using the wireframing and other outputs to guide the presentation.
2) Evaluate with rest of participants using the voting boards.
3) Allow time at each indicator for Q&A from participants:
What’s open, innovative, engages, doable?
From there what can others add or do?

33. #5 Implementation
Backlogs (SCRUM adaptation)

34. #opencocreation
1) Express in the less technical language possible a backlog for:
Design // Technical work // Strategy // Content needed
One postit = One task or issue
2) Establish priorities of what to develop by the order of items in the list.
#5 Implementation
Backlogs (SCRUM adaptation)