requirements
|
Debate: The Danger of "Negative" Requirements Is it advisable to define a system by stating what it shouldn’t do, or should “negatively-framed” requirements be avoided? |
|
|
It's the Relationships, StupidRelationships—working and personal—are vitally important to successful business analysis. If you don't have them, nothing else much matters. | 
|
|
Just-in-Time Requirements AnalysisAll 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. |
|
|
Agile Codelines and Shared Traffic SpaceHow an agile team works with their codeline is analogous to a shared space traffic model, in which most traffic signals and markings are removed; drivers, cyclists, and pedestrians are guided by a small set of rules. | 
|
|
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. |
|
|
What Is DevOps All About? DevOps is an umbrella concept that serves as a response to the "wall of confusion" that sometimes occurs when the communication between development and operations becomes unreliable. How does this confusion come about? What are some of the elements that fall under the DevOps umbrella? |
|