As you know, I think an understanding of your customer is a key succes factor for a project professional. And that applies to both your project sponsor and main stakeholders on the "project as an organisation" dimension, and to the real "end user" or beneficary of your project's outcome.
Something we always find challenging, for example, is how much is enough? At what point do the requirements or features stop being meaningful? If you have applied Kano analysis to your requirements how do you understand which features are going to delight your customers, and which are merely mundane mandatory features?
To be able to get to this level of understanding you'll need to understand your product's customer segements and what matters to them. Start the proces by breaking down your customers into various segments.
Here are some tips;
8 February 2009
Subscribe to:
Post Comments (Atom)
Popular Posts
-
Due to popular demand I have aggregated some information on User Stories and created a simple template. If you feel this would be useful to...
-
I have been having a bit of a discussion over at the IIBA blog with Kevin (VP BOK) and Julian (Chief architect.) It’s migrated over to ...
-
Better Projects Templates I am uploading a couple of project document templates to Google Docs. As I add more I'll post them up here. You...
-
You've heard many reasons why project fail. Here is a discussion hosted by BCS on why projects work. The discussion covers four dimensio...
-
The Precedence Diagramming Method ( PDM ) was developed in the early 1960s by H.B. Zachry in cooperation with IBM. It has largely repla...
-
In the below video some of the #10yrsagile participants discuss the role of the Business Analyst. A question for you; Do you agree or di...
-
This is a guest post by Jeff Hobbs. Jeff is a project manager at ActiveState Software who provide pm and collaboration software. Email, ...
-
In one of the Carnivals of Business Analysts the theme was “ Requirements Analysis ." I searched the web far and wide and came up with a n...
-
I'm a massive Lord of the Rings fan. Every year, I spend part of my holiday vacation rewatching the 12 hours of the blu-ray extended edit...
-
The definition of a stakeholder is controversial. For example, project team members are generally not considered stakeholders, but in virtua...
0 comments:
Post a Comment