The documents in this section are a breakdown of the governance structures, management tools, and high level relationships that preceded the launch of the lab. Governance deals with the constitution of and relationships between the funders, clients, lab teams, secretariat, and hosting team. It also deals with setting up an information infrastructure that can organize lab communications at all levels.
Page 1
The end
Standard
Chicago Workstreams
This diagram shows the different agile workstreams that were used during the Grove3547 Social Lab. It highlights the different activities of each workstream and lists accountabilities and teams for each. In this case you’ll notice that the Roller side is populated, while the client side is blank. In order to build internal capacity, a 1:1 ratio is advised, as in “co-delivery”. This ensures that the local/home team is able to build their internal capacity and ultimately take over responsibility for the Social Lab.
CHICAGO AGILE WORKSTREAMSThe end
Standard
Agile Regime
Agile is an iterative and incremental project management process that works well in situations of complexity, making it well-suited for organizing the set-up and delivery of Social Labs. Agile is central to the ways we manage and run social labs at Roller.
The Agile Regime 2.0 diagram offers a visual guide for how our agile regime was organized. At the top you’ll notice that the meetings, actions and decisions are at a strategic level and then become more granular and tactical at the the bottom of the diagram. The delivery/hosting team for Grove worked across several “workstreams”.
AGILE REGIME 2.0
The Agile Regime 3.0 document outlines the basic components for an agile team and gives some guidelines for how time can be managed and work organized. The Grove3547 Hosting and Delivery Teams utilized agile during the running of the Preconditions and the Lab delivery phases. This is the third iteration of the regime process.
AGILE REGIME 3.0The end
Image
Lab Cycle Diagrams
The first cycle of Grove3547 ran for a four month period. This period is what we call “one cycle” or a Minimum Viable Lab. While very short, this allows enough time to demonstrate the process and generate value within the system. This diagram shows the birds-eye-view breakdown of activities over the four month period including specific workshops each month and then the monthly sprints where prototyping teams are working independently to test out the latest versions of the prototypes.
The repeating cycles of a lab look something like this:
This is a full, detailed timeline of one cycle including preconditions:
The end
Standard
Social Labs Fieldbook
The Social Labs Fieldbook attempts to support practitioners who are interested in building social labs. It provides practical, step-by-step guidance as to how to design spaces, run processes and build the teams required to run labs.
THE SOCIAL LABS FIELDBOOK
The end