Data: Cyberinfrastructure project lifecycle

<h3>Sharing materials</h3> "When you survey what's already there, you could put that out and help people who want to do something today, even if they're not interested in PB. You don't have to join the community to benefit from it, you can benefit from the product of the community because the community publishes." (<span class="glossary-term" title="Workshop 2 (Oct. 15-18, 2008) brought participants together to discuss the Directions that emerged from the data analysis conducted on the wiki. Participants suggested questions and issues for each Direction, and formed groups to delve further into their chosen Direction, including what aspects are within the scope of Project Bamboo, what Demonstrators would be helpful, and what the plan should be for the working group."><abbr title="Workshop 2 (Oct. 15-18, 2008) brought participants together to discuss the Directions that emerged from the data analysis conducted on the wiki. Participants suggested questions and issues for each Direction, and formed groups to delve further into their chosen Direction, including what aspects are within the scope of Project Bamboo, what Demonstrators would be helpful, and what the plan should be for the working group.">W2</abbr>, Plenary Sharing 5, Facilitated Discussion with <span class="glossary-term" title="Greg Jackson, Vice President & Chief Information Officer at the University of Chicago, was a Principal Investigator for the Bamboo Planning Project through September 2009."><abbr title="Greg Jackson, Vice President & Chief Information Officer at the University of Chicago, was a Principal Investigator for the Bamboo Planning Project through September 2009.">Greg Jackson</abbr>) <h3>Buy-in</h3> "Kuali story: continuing attempt between Kuali and University of Chicago comptroller to have conversation - "Here's things we need, and when we need them - can we get it?" Kuali: "Well, this is a collaboration - what will come is product of collaboration. Yes, it'll happen if you persuade everyone." "I can't get into it unless I know." "Unless you're in, we can't guarantee anything." Different than vendor/customer relationships - real dilemma; there'll not be a satisfactory resolution in a way. Lots of linguistic issues floating around: different between "plan" and "promise". Plan - best thought about best steps to get to a given goal. Most of us don't do what exactly we planned, sometimes to a different goal. Can't confuse plan with promises to achieve particular ends, and proceed in particular ways. Nature of implementation plan/proposal - have to remember both ambiguities" (<abbr title="Workshop 3 (January 12 - 14, 2009) built off the progress of the Working Groups. A straw consortial model for Project Bamboo was also introduced and discussed.">W3</abbr>, Straw Consortial Model, <span class="glossary-term" title="Greg Jackson, Vice President & Chief Information Officer at the University of Chicago, was a Principal Investigator for the Bamboo Planning Project through September 2009."><abbr title="Greg Jackson, Vice President & Chief Information Officer at the University of Chicago, was a Principal Investigator for the Bamboo Planning Project through September 2009.">Greg Jackson</abbr>) "Faculty not feeling comfortable w/ language we're using as focus of work. "So IT oriented, not sure of concrete value of what they're going to get out of this". How will a scholar/teacher see how to use all this. Value propositions - not clear how institutions could see moving ahead. We could see our institutions participating, even smaller institutions about faculty pushback - the faculty here feel comfortable, but pitching to other faculty is a problem." (<abbr title="Workshop 3 (January 12 - 14, 2009) built off the progress of the Working Groups. A straw consortial model for Project Bamboo was also introduced and discussed.">W3</abbr>, Table Discussions of Consortial Model 2, Table 2) "Should there be a clear communication goal specified in the plan. A lot of faculty needs would be/are getting solved in variety of ways. We all need bamboo-like conversations at local institutions. PB has to make sure it adds value to these conversations; if not, members need to effect change." (<abbr title="Workshop 3 (January 12 - 14, 2009) built off the progress of the Working Groups. A straw consortial model for Project Bamboo was also introduced and discussed.">W3</abbr>, Table Discussions of Consortial Model 2, Table 3) "One thing that would help clarify: ultimate goal of advancing hum and arts research through new tech has appeal to humanities faculty but goal of PB, deliverable, are services which are great and networking, all is valuable in preparing the way for ultimate goal. There's a gap between goal of what PB can contribute to ultimate goal, and other pieces that will make the ultimate goal happen may not be in PB's provenance. PB can connect to, support those things - help explain to hum faculty how this is valuable, even if it itself isn't going to fund dig research labs." (<abbr title="Workshop 3 (January 12 - 14, 2009) built off the progress of the Working Groups. A straw consortial model for Project Bamboo was also introduced and discussed.">W3</abbr>, Table Discussions of Consortial Model 2, Table 5) "Articulation of value propositions is important, understanding of what it means for people/institutions to be involved. Need arguments to take back to their institutions, make the case with people there. We recognize that in working group; want to rename as "strategic communications" - arguments for involvement, roadmap for involvement and contribution - what are the steps an institution might follow as they participate in PB. Practical point about the timescale - we go into the work plan of implementation project, we need to do that NOW, before the proposal. Can be part of the work plan to refine, improve, etc but we need a statement ASAP" (<abbr title="Workshop 3 (January 12 - 14, 2009) built off the progress of the Working Groups. A straw consortial model for Project Bamboo was also introduced and discussed.">W3</abbr>, Table Discussions of Consortial Model 2, <span class="glossary-term" title="Chad J. Kainz, Senior Director for Academic Technologies in Networking Services & Information Technologies at the University of Chicago (later, Asst. Chief IT Officer and Executive Director, Campus & Academic Services in IT Services) was a Co-Director and subsequently Principal Investigator for the Bamboo Planning Project."><abbr title="Chad J. Kainz, Senior Director for Academic Technologies in Networking Services & Information Technologies at the University of Chicago (later, Asst. Chief IT Officer and Executive Director, Campus & Academic Services in IT Services) was a Co-Director and subsequently Principal Investigator for the Bamboo Planning Project.">Chad Kainz</abbr>) <h3>Defining community</h3> "Interesting question particularly about the question of who the community is. Is it the people in the room or the institutions we represent? Tension between that and that goes back to question of individuals as members." (<abbr title="Workshop 3 (January 12 - 14, 2009) built off the progress of the Working Groups. A straw consortial model for Project Bamboo was also introduced and discussed.">W3</abbr>, Table Discussions of Consortial Model 2, Table 5) "What do people put in, and what do they expect to get out? People will be involved if they have resources like access to experts, projects relevant to them, etc. But as soon as they start putting something into the larger PB community (hosting, also, participation in workshops and discussing ways where institutions could add something in the long term. At that stage, they're exercising a leadership role at a generalized level within PB. A year isn't a great deal of time (or money). There should be leadership at a slightly more centralized level. Be aware of individuals with expertise/commitment even if they're not in a participating institution" (<span class="glossary-term" title="Workshop 4 (April 16 - 18, 2009) included conversations about the discussion draft of the Bamboo Program Document, straw polls about interest in the program draft's areas of focus, and action plans by the groups that formed out of the straw polls."><abbr title="Workshop 4 (April 16 - 18, 2009) included conversations about the discussion draft of the Bamboo Program Document, straw polls about interest in the program draft's areas of focus, and action plans by the groups that formed out of the straw polls.">W4</abbr>, <abbr title="The Bamboo Program Document (drafts published March-April 2009) was a an outline for a possible 7-10 year vision for the Bamboo Community, discussed at Workshop 4.">Program Document</abbr> Section 5, Q&A) <h3>Distribution and prioritization of work</h3> "Scholarly network is important, overlap with the 'build' side; clear description of work and what parts need to be planned/built (incl services, scholarly networking, stories, exploratory labs), clear description of resource requirements, clear description of what the different roles are that are possible in the consortium to do that" (<abbr title="Workshop 3 (January 12 - 14, 2009) built off the progress of the Working Groups. A straw consortial model for Project Bamboo was also introduced and discussed.">W3</abbr>, Details of Straw Consortial Model, <abbr title="David Greenbaum, Director of Data Services at the University of California, Berkeley, was a Co-Director of the Bamboo Planning Project.">David Greenbaum</abbr>) "That kind of mismatch of local timelines, how local groups would be able to match their timelines with their projects up to larger group being able to do it is a question. Also, aligning priorities-- suggestion that whatever inst might think it's gonna do, proportion to how we'll they can show their local priorities can be aligned with larger priorities." (<abbr title="Workshop 3 (January 12 - 14, 2009) built off the progress of the Working Groups. A straw consortial model for Project Bamboo was also introduced and discussed.">W3</abbr>, Table Discussions of Consortial Model 2, Table 1) "Started out with feeling that we're confounding project and consortium, it's all intertwined. Important to tease them out to be more articulate about needs. Important to have assessment mechanisms in each layer to know we're on track." (<abbr title="Workshop 3 (January 12 - 14, 2009) built off the progress of the Working Groups. A straw consortial model for Project Bamboo was also introduced and discussed.">W3</abbr>, Table Discussions of Consortial Model 2, Table 7) "Project phase and project, community, consortium, what's beyond the project phase. What comes after, continuum is more important? We're on the cusp of having to make decision if we're a commune or constitutional assembly - one requiring more resource to sustain and manage than the other"." (<abbr title="Workshop 3 (January 12 - 14, 2009) built off the progress of the Working Groups. A straw consortial model for Project Bamboo was also introduced and discussed.">W3</abbr>, Table Discussions of Consortial Model 2, Table 8) ""Exploration lab" - what is it? Concept of lab resonated w/ members of leaderships council. Place with interesting experimentation. Where people solve problems at large scale/small scale. Cluster around getting something done. Think about work that needs to be done in PB as a collection of labs. Not a grand, big project of developing something like Kuali. New possibilities, existing possibilities for research/scholarship/learning, etc. Cluster around particular areas of common interest; promoting idea of innovation; if you want something done, you work towards that goal. By keeping activity in smaller clusters, you can react more quickly to particular problems. For any of this to work, there has to be some structured activity/effort. Focus on getting things done: "let's get started with something!"" (<span class="glossary-term" title="Workshop 4 (April 16 - 18, 2009) included conversations about the discussion draft of the Bamboo Program Document, straw polls about interest in the program draft's areas of focus, and action plans by the groups that formed out of the straw polls."><abbr title="Workshop 4 (April 16 - 18, 2009) included conversations about the discussion draft of the Bamboo Program Document, straw polls about interest in the program draft's areas of focus, and action plans by the groups that formed out of the straw polls.">W4</abbr>, <abbr title="The Bamboo Program Document (drafts published March-April 2009) was a an outline for a possible 7-10 year vision for the Bamboo Community, discussed at Workshop 4.">Program Document</abbr> Section 5, <span class="glossary-term" title="Chad J. Kainz, Senior Director for Academic Technologies in Networking Services & Information Technologies at the University of Chicago (later, Asst. Chief IT Officer and Executive Director, Campus & Academic Services in IT Services) was a Co-Director and subsequently Principal Investigator for the Bamboo Planning Project."><abbr title="Chad J. Kainz, Senior Director for Academic Technologies in Networking Services & Information Technologies at the University of Chicago (later, Asst. Chief IT Officer and Executive Director, Campus & Academic Services in IT Services) was a Co-Director and subsequently Principal Investigator for the Bamboo Planning Project.">Chad Kainz</abbr>) <h3>Tension between administrative control and innovation</h3> "Innovation is when people have an idea and want to act on it quickly. If we really believe our core value proposition about enhancing arts and humanities, we have to allow that to happen. Can't be tied closely with every major administrative move. Some aspects have to operate and move in that lockstep movement. How do you separate the two so you can have activities that move quickly. If things become important for community, they can be moved into and formalized as part of what PB is." (<abbr title="Workshop 3 (January 12 - 14, 2009) built off the progress of the Working Groups. A straw consortial model for Project Bamboo was also introduced and discussed.">W3</abbr>, Details of Straw Consortial Model, <span class="glossary-term" title="Chad J. Kainz, Senior Director for Academic Technologies in Networking Services & Information Technologies at the University of Chicago (later, Asst. Chief IT Officer and Executive Director, Campus & Academic Services in IT Services) was a Co-Director and subsequently Principal Investigator for the Bamboo Planning Project."><abbr title="Chad J. Kainz, Senior Director for Academic Technologies in Networking Services & Information Technologies at the University of Chicago (later, Asst. Chief IT Officer and Executive Director, Campus & Academic Services in IT Services) was a Co-Director and subsequently Principal Investigator for the Bamboo Planning Project.">Chad Kainz</abbr>) "There's also a reality of administrative overhead we have to deal with to get through funding stage, etc. Don't want to wait on BAMBOO to make a big decision - that slows everybody down. Reducing the amount of administrative overhead necessary. Get to the point of getting stuff done." (<span class="glossary-term" title="Workshop 4 (April 16 - 18, 2009) included conversations about the discussion draft of the Bamboo Program Document, straw polls about interest in the program draft's areas of focus, and action plans by the groups that formed out of the straw polls."><abbr title="Workshop 4 (April 16 - 18, 2009) included conversations about the discussion draft of the Bamboo Program Document, straw polls about interest in the program draft's areas of focus, and action plans by the groups that formed out of the straw polls.">W4</abbr>, <abbr title="The Bamboo Program Document (drafts published March-April 2009) was a an outline for a possible 7-10 year vision for the Bamboo Community, discussed at Workshop 4.">Program Document</abbr> Section 5, <span class="glossary-term" title="Chad J. Kainz, Senior Director for Academic Technologies in Networking Services & Information Technologies at the University of Chicago (later, Asst. Chief IT Officer and Executive Director, Campus & Academic Services in IT Services) was a Co-Director and subsequently Principal Investigator for the Bamboo Planning Project."><abbr title="Chad J. Kainz, Senior Director for Academic Technologies in Networking Services & Information Technologies at the University of Chicago (later, Asst. Chief IT Officer and Executive Director, Campus & Academic Services in IT Services) was a Co-Director and subsequently Principal Investigator for the Bamboo Planning Project.">Chad Kainz</abbr>) "Too much governance at this stage. Scalable governance is a good idea, as lightweight as possible at each stage. Avoid a structure that will require all/most time to be dumped into meetings. Use enthusiasm/commitment from so many institutions as the main asset, Bamboo to coordinate, promote interoperability. This is the right time for Bamboo because institutions are already engaged in the work PB proposes to address ... so Bamboo need only coordinate/leverage this pre-existing interest." (<span class="glossary-term" title="Workshop 4 (April 16 - 18, 2009) included conversations about the discussion draft of the Bamboo Program Document, straw polls about interest in the program draft's areas of focus, and action plans by the groups that formed out of the straw polls."><abbr title="Workshop 4 (April 16 - 18, 2009) included conversations about the discussion draft of the Bamboo Program Document, straw polls about interest in the program draft's areas of focus, and action plans by the groups that formed out of the straw polls.">W4</abbr>, <abbr title="The Bamboo Program Document (drafts published March-April 2009) was a an outline for a possible 7-10 year vision for the Bamboo Community, discussed at Workshop 4.">Program Document</abbr> Section 5, Q&A, Martin Wynne) <h3>Specialization</h3> "Mature organizations develop specialization (this is a generalist body), for making progress we might want to develop specialized parts of the organization relatively early." (<span class="glossary-term" title="Workshop 2 (Oct. 15-18, 2008) brought participants together to discuss the Directions that emerged from the data analysis conducted on the wiki. Participants suggested questions and issues for each Direction, and formed groups to delve further into their chosen Direction, including what aspects are within the scope of Project Bamboo, what Demonstrators would be helpful, and what the plan should be for the working group."><abbr title="Workshop 2 (Oct. 15-18, 2008) brought participants together to discuss the Directions that emerged from the data analysis conducted on the wiki. Participants suggested questions and issues for each Direction, and formed groups to delve further into their chosen Direction, including what aspects are within the scope of Project Bamboo, what Demonstrators would be helpful, and what the plan should be for the working group.">W2</abbr>, Plenary Sharing 5, Facilitated Discussion with <span class="glossary-term" title="Greg Jackson, Vice President & Chief Information Officer at the University of Chicago, was a Principal Investigator for the Bamboo Planning Project through September 2009."><abbr title="Greg Jackson, Vice President & Chief Information Officer at the University of Chicago, was a Principal Investigator for the Bamboo Planning Project through September 2009.">Greg Jackson</abbr>) <h3>Wrap-up</h3> "How can Bamboo wither effectively if necessary? Bamboo should be prepared to die or evolve functionally - a sense of its own temporal limitations." (<span class="glossary-term" title="Workshop 2 (Oct. 15-18, 2008) brought participants together to discuss the Directions that emerged from the data analysis conducted on the wiki. Participants suggested questions and issues for each Direction, and formed groups to delve further into their chosen Direction, including what aspects are within the scope of Project Bamboo, what Demonstrators would be helpful, and what the plan should be for the working group."><abbr title="Workshop 2 (Oct. 15-18, 2008) brought participants together to discuss the Directions that emerged from the data analysis conducted on the wiki. Participants suggested questions and issues for each Direction, and formed groups to delve further into their chosen Direction, including what aspects are within the scope of Project Bamboo, what Demonstrators would be helpful, and what the plan should be for the working group.">W2</abbr>, Plenary Sharing 5, Table H)