Comments on: Subject to Change Book Review http://www.afhill.com/blog/subject-to-change-book-review/ Reflections on online strategy, social media marketing, web accessibility and interactive design. Sun, 04 Jul 2010 23:28:10 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Andrea Hill http://www.afhill.com/blog/subject-to-change-book-review/#comment-158804 Andrea Hill Tue, 10 Mar 2009 13:50:26 +0000 http://www.afhill.com/blog/?p=992#comment-158804 At LexisNexis we tried to integrate UX/HF into the month-long sprints, which was tough as it created little mini-dependencies within the sprints. At the Web Directions North conference the other week I spoke with <a href="http://www.wait-till-i.com/" rel="nofollow">Christian Heilmann</a> and he said they did a design cycle every three sprints, where that was the main focus. It's not entirely "scrum by the book", but it seems a decent compromise. At LexisNexis we tried to integrate UX/HF into the month-long sprints, which was tough as it created little mini-dependencies within the sprints. At the Web Directions North conference the other week I spoke with Christian Heilmann and he said they did a design cycle every three sprints, where that was the main focus. It’s not entirely “scrum by the book”, but it seems a decent compromise.

]]> By: Melissa http://www.afhill.com/blog/subject-to-change-book-review/#comment-158799 Melissa Tue, 10 Mar 2009 13:23:30 +0000 http://www.afhill.com/blog/?p=992#comment-158799 Ah, I like that you have a Twitter ID field! But that's neither here nor there. My company is currently moving towards an agile development framework, and one of the birthing pangs that we're going through now is identifying how and where and what kind of artifacts UI/HF fits in and needs to bring to the table. The conversations that we're having are equal parts interesting and difficult, and there's going to be a lot of iterations (ha!) on how UI/HF plays to get it right. Ah, I like that you have a Twitter ID field! But that’s neither here nor there.

My company is currently moving towards an agile development framework, and one of the birthing pangs that we’re going through now is identifying how and where and what kind of artifacts UI/HF fits in and needs to bring to the table. The conversations that we’re having are equal parts interesting and difficult, and there’s going to be a lot of iterations (ha!) on how UI/HF plays to get it right.

]]>