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 […]
Agile / Product Management / Project Management / Requirements / Requirements Models / Software development / Use Cases
Posted on:
Benefits of Agile Story Decomposition
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 […]
Software development / UX
Posted on:
The First UX Project
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 […]
Book Reviews / Business Analysis / Expert systems / Process Improvement / Reviews
Posted on:
Smart Enough Systems – Interview With James Taylor
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 […]
Flashback
Posted on:
Flashback: A Year Ago This Week on Tyner Blain [2006-06-23]
A look back at the best from a year ago.
Uncategorized
Posted on:
Nexus Friday Favorites
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…
Business Analysis / Product Management / Requirements / Requirements Models / Software development / Software requirements specification
Posted on:
Broken Requirements Ecosystem
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.
Communication / Consulting / Product Management / Project Management
Posted on:
Failure To Deliver Is Not An Option
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.
Prioritization / Product Management / Requirements / Slightly off-topic
Posted on:
Gadgets And Goals
What makes the best gadgets great? An understanding of goals and attention to design details. When we take a step back from writing requirements about software, and think about gadgets and goals – the perspective can help us write better requirements and make better prioritization decisions.