Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
pablowilks
Starting Member
6 Posts |
 Posted - 2012-05-25 : 11:22:58
|
| Hi there,My initial hunch is yes absolutely. surely the more feedback from users the better right?Was interested in people's thoughtsThanks |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2012-05-25 : 12:06:14
|
| Yes. You should however be aware that users do not always know what they want, or ask for things that are not always reasonable. You should definitely get their input, but be sure to filter their requirements to things that are absolutely essential.If in doubt, Joel has a fairly good methodology here (it's a series): http://www.joelonsoftware.com/articles/fog0000000036.htmlHe also described a way to prioritize features that I like (but never used): http://www.joelonsoftware.com/articles/SetYourPriorities.htmlHe mostly focuses on software development over database design, but it's good to have both sides use similar processes and work together as much as possible. |
 |
|
|
pablowilks
Starting Member
6 Posts |
Posted - 2012-05-25 : 18:42:32
|
great thanks for your inputquote:
Originally posted by robvolk
Yes. You should however be aware that users do not always know what they want, or ask for things that are not always reasonable. You should definitely get their input, but be sure to filter their requirements to things that are absolutely essential.If in doubt, Joel has a fairly good methodology here (it's a series): http://www.joelonsoftware.com/articles/fog0000000036.htmlHe also described a way to prioritize features that I like (but never used): http://www.joelonsoftware.com/articles/SetYourPriorities.htmlHe mostly focuses on software development over database design, but it's good to have both sides use similar processes and work together as much as possible.
|
|
|
|
|
|
|
Database design