Tag Info

Hot answers tagged

11

Answering your questions in order: The mindset going into this in terms of preparation, is to ask the right questions so that the user knows exactly what they want. This is much more difficult than it seems. I need to emphasize asking the right questions. Be specific, if there is any ambiguity, ask another question. Usually during these meetings one answer ...


4

Users most times know exactly their daily work and which problems they have to solve. What they typically don't know is a) how the software exactly has to look like to support that process. b) how they can explain their process to you. So focus on questions to understand what the user really want (their goals, their working process), and not if a button ...


3

What I try to emphasize when doing requirements gathering is that if this is for replacement for an existing system, to not think of how you do things in the existing system but rather what would be the ideal way to accomplish what you need to do. So often users are stuck with the way things are done they can only describe their needs in that manner. The ...


2

Many agile experts recommend starting new projects by thinking about what they call the "Minimal Viable Product". What this means is we stop thinking about all of the features an application should have, and instead ask "what is the smallest possible thing I can build that would be useful". Given your example above, I would suggest starting by forgetting any ...


2

Most of our Lean knowledge comes from the work that Deming did at Toyota. There are two main ways in which I look at Lean: Lean Product Development Lean Production. Lean Product Development is the equivalent to designing new cars, and is more like software development than production is. We're busy creating new things, not producing the same old thing ...



Only top voted, non community-wiki answers of a minimum length are eligible