A Simple History
Background
- Some of our hopes for Sakai collaborations
- Efficiencies for few development resources
The Requirements
- Timed Release
- Reordering
...
- Jim Eng (project lead)
- UNISA (Usability Design and QA)
- Whitman College (Design Mockups and Development)
- Boston University (Design and QA)
...
Coming out of the Requirements Process
- the ranking of our requirements mattered little - we just needed thisthese things
- the articulation of these requirements helped little - we had to
rework that anyway, once we got down to brass tacks - however, we may not have come together in quite the same way otherwise
- it did make it easier for us to talk about what we were doing
- it did make it easier to approach Jim with what we wanted to do
Preparatory Work
- early email discussions
- Jim put some DB work into 2.2.0 release in preparation for us needing it
- Chuck helped make the connection with Jim, and an initial meeting at Sakai conference
...
Choosing the Right Project
- find a tool you have a long-term interest in (understand what your
users want and need) - an area of Sakai that you want to develop an expertise with, and
be responsive with - a project lead you can work with
- local requirements that are not otherwise being met by other teams
- find a project of a suitable scope and kind for the resources you can commit
- developing it for broader use makes others more willing to contribute
- understand the incentives and limitations of your collaborators