release cycles

4 May 2010 - 8:00am
6 years ago
7 replies
jeff noyes

Agile release cycles: every three weeks bad?

My company releases software after each iteration. The result is a constantly changing platform. I suspect this is really bad for the user experience. Anyone have usage data, case studies, etc on this topic?

-- Jeff Noyes Director of User Experience | Acquia 978.296.5237 | @jeffnoyes

1 May 2008 - 12:52pm
8 years ago
2 replies

the release cycle

Hi everyone,

This question is a little outside the scope of IxD but is closely
related to one of our goals: getting our work in front of real people.

What I'm interested to know is - in the web world, how do your
companies approach new releases?
How much time is spent on QA, and how often do you release improved
versions of your product - be it fixes, or new features?
What's your release criteria?

I know this tends to be different for different types of companies...
but would love to hear what works for you.


31 Jan 2007 - 12:43pm
9 years ago
13 replies

Anyone succeeded in getting a usability-only release?

Have any of you ever succeeded in getting a software release dedicated solely to usability fixes? I guess I'm primarily addressing in-house specialists... presumably consultants are often engaged to address solely usability.


Syndicate content Get the feed