Summary: From the Editors of StickyMinds.com – Managing an agile project based on uncensored “Very High,” “High,” and “Low Priority” user stories or backlog items used to induce stress on Jeff Patton. So he learned to implement a combination of prioritization techniques to get these lists–and the job–under control. In this week’s column, find out how Jeff utilizes MoSCoW and business goals to make sense of prioritization.
One of the more challenging things about moving
How Kanban-style development gives us another way to deliver on Agile values
Years ago — Feb 25th 2008 to be exact — I wrote this draft article. At the time Kanban development was a cool new thing — bleeding edge Agile. Due to a series of unfortunate events the article wasn’t published in the magazine it was originally target for. I’ve been sitting on it
Building and Usability Testing a Paper
These are big downloads. I’d recommend muting the sound since there’s a lot of background noise, but these short movies clearly illustrate building and testing paper prototypes. In the testing movie, the participants clearly fit into the roles of facilitator, computer, observer, and paired test subjects.
- Building Paper Prototype MPG file
- Testing a paper prototype (currently unavailable)
What the product owner needs to worry about isn’t in the product backlog If you’ve read one of my blog essays before, you know this isn’t going to be a quick thought, but a bit of a long discussion (read “discussion” as “rant”). This particular discussion describes what I see as a problem in agile development – sort of a practice vacuum. One of the most difficult roles in an agile process is the product