Child pages
  • Blue Sky Committee...Portfolio Identity, Development, and Evangelism

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Overall Motivation

Some notes about overall motivation from the 7/6/2007 phone call. Please edit/expand/remove as you see fit.

The overall motivation for the Blue Sky group comes out of the 2.5 planning meeting in Amsterdam. At that meeting, some major out of the box thinking surfaced about future OSP development. Below are some buzz words recalled from that meeting:

  • "why can't you reflect anywhere on anything?"
  • "portfolio"
  • "assessment"
  • "light publishing"
  • "instructional design"
  • "integrated learning"

One agreed goal from that meeting was to be more effective within Sakai community. The role of the Blue Sky group, then, is to figure out concrete steps that will accomplish that goal.

Specific Goals

Some notes about specific goals from the 7/6/2007 phone call. Please edit/expand/remove as you see fit.

  • Stuff that's related to Sakai software infrastructure that needs to change.
    • Rethinking the relationship between "pedagogical services" and tool based design
    • Possibly balancing user experience changes between user-centric and site/context-centered
    • Best way to effect change is to immerse ourselves in the UX community
    • Concentrate on "helpers" in the software
    • Share/reflect on anything with anyone from anywhere
    • Stop having closed conversations with portfolio only folks--include mainstream Sakai developers, etc.
  • Stuff that's related to the overall pedagogical use of OSP and Sakai.
    • There are recurring themes that are needed across tools and could be implemented as service level widgets, embedded into all parts of Sakai so that ideas that are core to teaching and learning are always present for users across tools
    • User-centered
    • Reflection focused
    • Ease of sharing
    • Goal aware
    • Transformational (for individual, institution, education)
    • Focus more on how we use the available tools than what the tools do
    • Stop having closed conversations
    • New name: should we expand out identity beyond portfolios to pedagogy?
    • Conference proposals under pedagogy, except for tool demos, etc.
  • Stuff that's related to the development of truly specific portfolio tools.
    • This should stay in the smaller community
    • The question surfaces: what are the portfolio tools?
    • Are we a portfolio community?
    • What are we focused on in terms of future development?
    • Emphasis on transformational functionality?
    • Emphasis on user-centered?
    • Emphasis on integrated learning?
  • Stuff that's related to Sakai's identity and processes overall as a project/product
    • Be more effective (in Sakai community/framework)
    • The question surfaces: how is the focus of the OSP community perceived? We all know of people on our campuses who need the functionality of portfolio, but don't know anything about portfolio, so don't ask. Is this happening in the Sakai community as well? Are we the best kept secret in Sakai? And how can we spread the word about the transformational, pedagogical value of OSP without alienating, while being a part of the team?
    • Emphasis on transformational functionality?
    • Emphasis on user-centered?
    • Emphasis on integrated learning?

General Strategy

  • To expand the development discussion beyond "tools" and to have a broader conversation about what services would have broad utility across the environment. This generally will require discussion between framework developers, tool designers and pedagogy experts.
  • To find like minded people to collaborate outside of OSP and inside of Sakai
  • To unpack concepts like "pedagogy", "transformative" and "integrated learning" for ourselves so we can spread a common message as we integrate into the wider Sakai community

Specific Tactics

Note
titleNote

One thing that hasn't been discussed in relation to the Blue Sky Committee is the need for specific roles and governance as we move forward. Since we are, in some ways, talking about blending more into the pedagogy group, setting up roles and governance may seem counter-intuitive. But our Blue Sky goals call for a sea change in how we function, as a community, and I believe firmly that without designated leaders to keep that change moving forward, we will not see real progress any time soon. -Wende Morgaine

  • Stuff that's related to Sakai software infrastructure that needs to change.
    • Developers might want to chime in here. Things addressed at the goal aware BOF in Amsterdam and thoughts about how (architecturally and at the code level) "reflecting anywhere on anything" would be accomplished seem to go here.
  • Stuff that's related to the overall pedagogical use of OSP and Sakai.
    • Part of this will involve submitting some OSP conference sessions at Newport under the Pedagogy track to lessen the sense in the Sakai community that portfolios are an island, etc.
    • We might even want to develop a postcard sized handout touting some fo the portfolio functionality that would appeal to a wider audience: what OSP brought to the Sakai Assignments tool with the Goal Aware functionality, OSP for P&T, OSP for disseminating research findings, OSP for administrative processes like curriculum review, freeform portfolios, etc. ???
  • Stuff that's related to the development of truly specific portfolio tools.
    • This list might be filled in by visionaries about the future of portfolio functionality and Web 2.0 realities
  • Stuff that's related to Sakai's identity and processes overall as a project/product
    • This might be the collapsing of the portfolio list into the dev list and the pedagogy list
    • Part of this will involve submitting some OSP conference sessions under the Pedagogy track to lessen the sense in the Sakai community that portfolios are an island, etc.

Code/Functionality Goals Discussion Agenda

Conceptual/Identity Discussion Agenda

  • Sakai Community Perception Action Items: name, conference, etc.