University 2.0

The Eternal Beta - Can it Work in an Institution?

creativecommons

What is it?

What it's not

tagging

blogs

wikis

(or CMS either!)

underpants gnome model

1) beta

2) ?!??!

3) profit!!!!

What it is

incremental improvements, all the time

it's about the people, stupid

moo

invitations

closed audience (but infinite)

feedback channels

viral popularity

favoured release model

Gmail

Dopplr

Joost (The Venice Project)

invitations rule

quiet development process

user feedback

you can break stuff!

expectations

lower quality

not finished

can give public feedback

who to invite

your bloggers

facebook group founders/active members

previous contacts

active members

a community?

yikes!

probably not

implementation woe

integration problems

scarcity of feedback

scarcity of tester time (seeding matters!)

development

can be hard

authority vs. conversation

management structure critical

release early, release often

easy to say

agile/XP development

excellent internal communication

continuous resource

vital tools

continuous integration

real bug tracking

version control

this seems basic, but without these things it's pointless to even try. None of them are optional.

when to go public?

up to you

flickr's move to gammastable reliable serviceinvitation count over a % thresholddeployment loop slowswhere possible a community developsrate of improvement suggestions dropslist of wanted changes stablises (and you won't/can't do them)

how to fail

don't respond

don't act

lie about everything

Good luck!

Klicken Sie, um das Format des Titeltextes zu bearbeiten

Text