Google's famous for it, Flickr's moved to Gamma, Moo are on an eternal 1.0 -
yet still in institutions we plod on with a tired, slow-moving and opaque process
for developing and enhancing applications. From our closed support lines to official
notices on unread websites and applications mysteriously changing in front of a
user's very eyes we look staid and tedious. But it doesn't have to be like that,
we could be fast faced and interactive - but at what cost? Continuity? Uptime?
Learning Objectives:
At the end of the session attendees should have a better idea of:
why eternal beta is used
where we can use it
technical and personnel processes for adoption of eternal beta status
Rating:
Technical:
Hands on:
Note: Each session is given a rating from 0 (low) to 3 (high). More information
on this is available on the call page.
