A look back at the best from a year ago
Continue reading Flashback: A Year Ago This Week on Tyner Blain [2006-06-30]
A look back at the best from a year ago
Continue reading Flashback: A Year Ago This Week on Tyner Blain [2006-06-30]
Each Friday, we highlight some of our favorite articles, bundles or reviews that people have submitted to nexus. Check out this week’s Friday Favorites…
You expect analysis to happen before design, and both to happen before implementation and testing. But how much should these activities be staggered? When a project is being run with monthly releases, it might seem logical to have each group working on a different release. For example, the test team working on the current release (3), the developers on the next release (4), and architects and analysts working on releases 5 and 6 respectively.
If your team is this staggered, you have a problem. It takes four months for a requirement to be released from the time the analyst has documented it.
Continue reading Juggling The Elements of An Iteration
When you plan a release, agile user stories, or classic use cases are the best sized pieces to use in the planning – from the perspective of your customers. Each user story can be further decomposed into a set of specifications, and those into development tasks. Development tasks are the right sized unit to manage your work breakdown structure – communicating the release schedule internally with your development team.
Amy Hilman has written an outstanding article with the boxes and arrows staff about how to get that first UX (User Experience) project started at your company. Most companies don’t include user experience (UX) research as a key part of their product development process. But all companies will benefit from it.
Today we recorded an interview with James Taylor, co-author of Smart (Enough) Systems, How To Deliver Competitive Advantage by Automating Hidden Decisions. This book, written by James Taylor with Neil Raden comes out on Jun 29th (2007), and is available for pre-order from Amazon today. Our interview covers many of the topics in their book, with a focus on the ideas inside and the benefits you can get from applying them, in just under an hour.
Continue reading Smart Enough Systems – Interview With James Taylor
A look back at the best from a year ago.
Continue reading Flashback: A Year Ago This Week on Tyner Blain [2006-06-23]
Each Friday, we highlight some of our favorite articles, bundles or reviews that people have submitted to nexus. Check out this week’s Friday Favorites…
There’s an interesting thread on Seilevel’s requirements forum about why developers don’t read the specs and how to fix this problem. Sometimes the developers throw away the requirements. And that’s bad. But it is a symptom. Something is broken at a higher level.
Continue reading Broken Requirements Ecosystem
But sometimes, it happens anyway.
The Cranky PM started a great thread of conversation asking how product managers deal with the job of telling customers (and sales folks) that a feature is not going to be available in the promised release.