Requirements
 |
It's the Relationships, Stupid Relationships—working and personal—are vitally important to successful business analysis. If you don't have them, nothing else much matters. |
|
 |
Just-in-Time Requirements Analysis All requirements are built on some sort of hypothesis. Just-in-time requirements analysis embodies the idea that you form your hypothesis as late as responsible—not as late as possible. |
|
 |
Is Your Data Deceiving You? Do you know how clean, accurate, and up-to-date your data is? Learn how to increase the quality of your data so that your data never deceives you again. |
|
 |
What Do Our Customers Really Want? Agile teams can create software quickly, but how quickly can they gather and process feedback from customers? Here is one team's experience, with some tips and resources to help you introduce a community of practice in your own organization. |
|
 |
Why the UK Police Are Wrong about IT and Why You Should Care While value for money is always important, a more important question should be “What problem are you trying to solve?” Unless you fully explore the problem, you’ll have no idea if IT is the best solution. |
|
 |
Understanding Context When Designing Products for Users When designing software, you must look beyond simply knowing the goals of your users. It's far more useful to understand the context in which the product will be used. |
|
 |
Are Your Requirements Flying Blind? Of all of the requirements a stakeholder says "must" be done, how do you know which ones "should" be done? Connecting the project vision and goals to the requirements can help your team decide. |
|
 |
Ideas for Eliciting Examples and Specifications In the past few weeks, I’ve been looking for ways to apply the techniques of pull conversations to getting specifications from our customers. Pull conversation techniques advise us to let go of our own assumptions and judgments and to try to put ourselves into our stakeholders’ world. |
