Pre-Beta (was What sets the 'best' interaction designers apart?)
4 Feb 2007 - 7:10pm
6 years ago
On Feb 4, 2007, at 11:56 AM, Jared M. Spool wrote:
> > On Feb 4, 2007, at 12:42 PM, David Malouf wrote: > >> The future is a project being work on now in a closed beta > > Serious question: What's the difference between a "closed beta" and > an "alpha"?
Probably only a mental separation, I would think.
Myself, I despise "alpha" releases to select customers. I'm used to
milestone point of "alpha" being "good enough for QA to deal with it
and post bugs against it" and "beta" being "good enough for people
outside of engineering to deal with it", sometimes with a "second
beta" for select people outside the company. With today's "public
beta", I guess three beta milestones is too much, so they push things
back into alpha.
I'm sure that valuable info can and does come back from these push
outs, but my experience says they are mostly beneficial for
marketing, to get select, important customers signed up for the next
version months before it's actually released. For QA, they end up
being a headache: development gets pushed to respond mostly to the
feedback from the "alpha customers", making QA wonder what the heck
they are being paid for as they see their bugs sidelined to keep
schedules clear for future customer feedback, only to see that
feedback come in weeks later marking the same issues QA found back
when it could have been addressed more effectively. Sigh.