tag:blogger.com,1999:blog-33322509.post2310161223154930238..comments2023-10-30T14:56:20.392+01:00Comments on Software Engineering - Best Practices: [Arch] Requirements?!Alexander Schattenhttp://www.blogger.com/profile/02580484314696408186noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-33322509.post-53729051562326831462008-09-18T22:14:00.000+02:002008-09-18T22:14:00.000+02:00Yes, Kevin, I believe that you made this experienc...Yes, Kevin, I believe that you made this experience, however the underlying question is: does this speak against the agile process or against the customer?<BR/><BR/>I would say, of course, the latter.<BR/><BR/>I knew a company that did RUP crap documentation in bunches for the customer (a telko) but actually internally they did scrum because they said this is the only process that works for them.Alexander Schattenhttps://www.blogger.com/profile/02580484314696408186noreply@blogger.comtag:blogger.com,1999:blog-33322509.post-4424794040390907582008-09-18T16:58:00.000+02:002008-09-18T16:58:00.000+02:00This speaks to the overall inadequacy of the Agile...This speaks to the overall inadequacy of the Agile process for many web based, non-product oriented organizations. I have recently written my own blog speaking to this issue. I was recently in a development organization that was “market driven” the marketing business owners demanded a very detailed specification of a feature before implementation. They did not want to participate in any iterativeAnonymoushttps://www.blogger.com/profile/12684118277386038574noreply@blogger.comtag:blogger.com,1999:blog-33322509.post-7158753592783055482008-09-17T14:30:00.000+02:002008-09-17T14:30:00.000+02:00You are of course right; this is why I wrote the s...You are of course right; this is why I wrote the second part mentioning that we should not fall into an agility trap insofar as to believe agile or any other methodology works for all projects. I brought the example where a waterfall-like approach is still in 2008 working perfectly fine.<BR/><BR/>Safety critical dependable systems are definitly a type of projects that demand specific treatment.<Alexander Schattenhttps://www.blogger.com/profile/02580484314696408186noreply@blogger.comtag:blogger.com,1999:blog-33322509.post-82568968926513736442008-09-17T11:55:00.000+02:002008-09-17T11:55:00.000+02:00This is a really interesting post Alex! Requiremen...This is a really interesting post Alex! <BR/><BR/>Requirements elicitation and requirements management is one of the major cornerstones for a successful software project. Most of the projects do not fail because of technical issues! In best case technical details should be avoided at the requirements elicitation stage (depends on the project type). For the details there is a design and Szabolcs Rozsnyaihttps://www.blogger.com/profile/08456689888173131222noreply@blogger.com