http://www.awidernet.com/2009/10/26/agile-development-user-experience-and-the-two-week-myth/ Cool New Marketing Technologies: Caught and Served Fri, 06 Jan 2012 02:46:01 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://www.awidernet.com/2009/10/26/agile-development-user-experience-and-the-two-week-myth/comment-page-1/#comment-86555 Judith Robichaud Thu, 29 Oct 2009 15:47:16 +0000 http://www.awidernet.com/?p=1906#comment-86555 Thanks, Robert. You hit the nail on the head with the notion that Agile is a framework that is meant to provide guidelines and not hard and fast rules. The very term "agile" means to be nimble so if release cycles need to be tweaked, that flexibility is built into the process. Thanks, Robert. You hit the nail on the head with the notion that Agile is a framework that is meant to provide guidelines and not hard and fast rules. The very term “agile” means to be nimble so if release cycles need to be tweaked, that flexibility is built into the process.

]]> http://www.awidernet.com/2009/10/26/agile-development-user-experience-and-the-two-week-myth/comment-page-1/#comment-86544 Robert Dempsey Thu, 29 Oct 2009 13:36:58 +0000 http://www.awidernet.com/?p=1906#comment-86544 Great post Judith. You present a great answer to a common question. I've had the same experience - that people get hung up on the timeframe of creation. Thus far the best way I've seen teams handle UX work is to have it in separate sprints and then incorporate the work with code in later sprints. Agile and Scrum are frameworks and philosophies, meaning we can change them to suit our needs as necessary. Great post Judith. You present a great answer to a common question. I’ve had the same experience – that people get hung up on the timeframe of creation. Thus far the best way I’ve seen teams handle UX work is to have it in separate sprints and then incorporate the work with code in later sprints. Agile and Scrum are frameworks and philosophies, meaning we can change them to suit our needs as necessary.

]]>