Intel introduced the G6951 unlockable CPU consumer product this month. Â Most of the press has been critical. Â Is this new chip / upgrade process a bad product, or a good product with bad positioning?
Monthly Archives: September 2010
Passionate Requirements
Writing passionate requirements is not about writing with passion. Â It is about writing the requirements that cause people to be passionate about your product. Â Find the most important problem, for your most important customers. Â Understand the essence of what is important to solve that problem, for only those people. Â Then write passionate requirements.
Customer-Centric Market Model
A market can be thought of as the collection of contexts in which you might sell your product. You can split your market into a set of market segments. Each of those segments represents a group of customers, each of whom shares a set of problems for which they would pay for solutions.
Atomic Requirements
Each requirement you write represents a single market need, that you either satisfy or fail to satisfy. Â A well written requirement is independently deliverable and represents an incremental increase in the value of your software. Â That is the definition of an atomic requirement. Â Read on to see why atomic requirements are important.
Sprint Backlog – Don’t Solve Half of the Problem
Every team that transitions to agile faces this problem – some stories are too big to fit in a single sprint. Â Most of the teams that I have worked with have the wrong instinct – to solve half of the problem for all users.
The right approach is to first solve all of the problem for a subset of the users.
Latest Articles
Comments on all Articles
