1. Collaborative Design Processes and Plone

• • Christopher Johnson | ifPeople

• Jon Stahl | ONE/Northwest

• Plone Conference | Washington, DC

• October, 2008

2. Why are we here? 3. Goals of Session

Understand how Plone community creates Plone the software

Inspire ideas for improving the process

Contribute to shared interest in improving the process

Recruit people who want to help improve the process

4. Outline

Process map!

Collaborative design outside the community

What it all means

Conversation about how to move forward

5. Is Plone an Orchestra? http://flickr.com/photos/jordanfischer/72510316/ 6. Chaordic = chaos + order http://flickr.com/photos/chriscorrigan/381481875/ 7. http://flickr.com/photos/nh567/2774100797/ 8. Process Map 9. Learning from Others

Where are the best practices in remote collaboration and collaborative design processes?

10. Example: Datacenter Charrette

RMI convened whole-system design charrette for data centers (Feb 2-5, 2003)

"clean sheet model with no compromises"

Goal: leapfrog incremental improvements to advance overall design

11. The Problem The Problem 12. Solution Criteria

Can't just keep applying more brute force to this problem

Must use energy efficiently

Design system around efficiency, reliability, and availability

13. What is a Charrette? image: eyetopixel 14. Crosses Boundaries image:zoomzoom 15. Crosses Boundaries image:zoomzoom 16. Image: http://en.wikipedia.org/wiki/Blind_Men_and_an_Elephant 17. image: jeffwerner 18. image: danielfarrell 19. The People

90 people, including industry experts in:

• engineering

• computer design

• energy

• data management

• business

• real estate

• facilities design

image: dcassaa 20. The Result

Data center design that

• reduces energy conception by 89%,

• with equivalent computing power

• and greater reliability.

Over 50 major recommendations

See www.rmi.org 21. What made it work?

Facilitated dialogue on:

• innovative and functional design and engineering

• strategies to improve results of design decisions

22. What made it work?

Whole-system thinking:

• actively considers interconnections between systems

• seeks solutions that address multiple problems at same time

23. What makes it work?

Unites stakeholders and experts at the beginning of design / problem-solving process

Aggregate demand/needs from many stakeholders

24. http://flickr.com/photos/maxine/1523329505/ 25. Small group activity

Break into groups of ~5-7

Brainstorm: What are ways we can make the process of developing Plone more collaborative and approachable?

• What would help us better front-load the design process so that we had more input and commitment before code had to be written?

• What activities will generate engagement & participation from stakeholders?

• What can you do to drive this forward?

• Who's not here that should be engaged in this conversation?

Log in to OpenPlans athttp://tinyurl.com/plone-processto record your group's ideas on a new page

• Separate page per group to avoid edit conflicts!

15 minutes

26. What next?

Become a fan of Framework Team on FB

Join OpenPlans Group:http://tinyurl.com/plone-process

• Add your name to list

• Volunteer for a followup task

• Keep the conversation alive!

27. Thank you!

Christopher Johnson (irc: cjj)

• cjj at ifpeople.net

• www.ifpeople.net

Jon Stahl

• jon at onenw.org

• www.onenw.org