bestrequirements.blogspot.com
PRODUCT REQUIREMENTS: Practical advices by Karl Wiegers
http://bestrequirements.blogspot.com/2016/03/practical-advices-by-karl-wiegers.html
If you've been working at anything, just to realize at the end that the customer wanted it another way. you might find this useful. March 31, 2016. Practical advices by Karl Wiegers. I am reading the beautiful book "More About Software Requirements: Thorny Issues and Practical Advice" by Karl E. Wiegers. I'd like to share with you two of the most important points of his "10 cosmic truth",. That to me are #6 and #9. 6 The requirements might be vague, but the product will be specific.
bestrequirements.blogspot.com
PRODUCT REQUIREMENTS: January 2016
http://bestrequirements.blogspot.com/2016_01_01_archive.html
If you've been working at anything, just to realize at the end that the customer wanted it another way. you might find this useful. January 29, 2016. 2 The four causes. Aristotle's was often thinking which were the four causes of. anything: the material, formal, efficient, and final cause. To my own risk, I'll try to apply these causes, to the very limited scope of software requirements. To build a software that works well and is efficiently used by customers. Well I still have to think about this one.
bestrequirements.blogspot.com
PRODUCT REQUIREMENTS: February 2016
http://bestrequirements.blogspot.com/2016_02_01_archive.html
If you've been working at anything, just to realize at the end that the customer wanted it another way. you might find this useful. February 24, 2016. There are many steps between the real needs, the requirements you write, how the thing is made. What the user really needs. What the user knows. What the user thinks. What the user actually says to you. What you write down. What the developer will read. What the developer will understand. Links to this post. February 6, 2016. All the questions you forgot.
bestrequirements.blogspot.com
PRODUCT REQUIREMENTS: Don Estes
http://bestrequirements.blogspot.com/2016/03/don-estes.html
If you've been working at anything, just to realize at the end that the customer wanted it another way. you might find this useful. March 3, 2016. We do like Don Estes' blogs: we always find something to learn. Is about Business Rules, but you will find many interesting concepts abut requirements. I think this two images are very important, too. Subscribe to: Post Comments (Atom). Practical advices by Karl Wiegers. People and blogs we like. Gathering business or technical requirements since 1996.
bestrequirements.blogspot.com
PRODUCT REQUIREMENTS: 5. The funnel
http://bestrequirements.blogspot.com/2016/02/5-funnel.html
If you've been working at anything, just to realize at the end that the customer wanted it another way. you might find this useful. February 24, 2016. There are many steps between the real needs, the requirements you write, how the thing is made. What the user really needs. What the user knows. What the user thinks. What the user actually says to you. What you write down. What the developer will read. What the developer will understand. Subscribe to: Post Comments (Atom). 4 Questions, questions, questions.
bestrequirements.blogspot.com
PRODUCT REQUIREMENTS: Another hint
http://bestrequirements.blogspot.com/2016/03/another-hint.html
If you've been working at anything, just to realize at the end that the customer wanted it another way. you might find this useful. March 10, 2016. Something we should never forget:. Some people use the products, some OTHER people gathers requirement for those products. So, to gather requirements is as easy as. walking on water. When it's frozen. Subscribe to: Post Comments (Atom). Practical advices by Karl Wiegers. People and blogs we like. Gathering business or technical requirements since 1996.
bestrequirements.blogspot.com
PRODUCT REQUIREMENTS: 3. Simple, Complicated, Complex... Chaos !
http://bestrequirements.blogspot.com/2016/02/3-simple-complicated-complex-chaos.html
If you've been working at anything, just to realize at the end that the customer wanted it another way. you might find this useful. February 1, 2016. 3 Simple, Complicated, Complex. Chaos! A few words about the different kind of systems, just so you know in which kind of trouble you are when you start gathering requirements :-). What it is: you can see clearly all the connections between cause and effect . How to handle it: it is usually easy. How to handle it: run away! Subscribe to: Post Comments (Atom).
bestrequirements.blogspot.com
PRODUCT REQUIREMENTS: November 2016
http://bestrequirements.blogspot.com/2016_11_01_archive.html
If you've been working at anything, just to realize at the end that the customer wanted it another way. you might find this useful. November 24, 2016. Crash course - 2. The more I think about it, the more "why" is the. Word when it comes to requirements gathering. Has two different meanings:. You ask questions to understand the cause, what has happened in the past. We ask questions to understand what the user will need in the future, what he wants to do. Links to this post. Subscribe to: Posts (Atom).
bestrequirements.blogspot.com
PRODUCT REQUIREMENTS: A small hint
http://bestrequirements.blogspot.com/2016/03/a-small-hint.html
If you've been working at anything, just to realize at the end that the customer wanted it another way. you might find this useful. March 8, 2016. In writing requirements, synonyms do not exist. An example is "tree" and "plant". The two words seem similar, but they have different meanings. Tree: "a usually tall plant that has a thick, wooden stem and many large branches". Plant: "organism belonging to the vegetable kingdom". Subscribe to: Post Comments (Atom). Practical advices by Karl Wiegers.
bestrequirements.blogspot.com
PRODUCT REQUIREMENTS: September 2016
http://bestrequirements.blogspot.com/2016_09_01_archive.html
If you've been working at anything, just to realize at the end that the customer wanted it another way. you might find this useful. September 12, 2016. I found in my library the "Mastering the Requirements Process" book. That some might know as the " Volere. After many years I still find it very useful. I don't think the good Robertsons. Invented anything really new, but I do believe that this book covers 90% of the "how to" solve requirements problems in software development. And 90% is a lot!
SOCIAL ENGAGEMENT