Thursday, July 03, 2008
Resources   »   Articles    

Business Analysis Articles & Systems Analysis Articles
Resources


Article Archive


Articles and White Papers

Current Articles | Categories | Search | Subscribe (RSS)

Articles from Elicitation (BABOK KA)

» Rapid Requirements Engineering – Does a Specification Always Need to Come at the Start?
(34 Views) (0 Comments)
Requirements and the way they are dealt with are decisive to the success of a project. This statement is never really questioned in modern software engineering circles. Why is it, then, that a systematic requirements engineering (RE) system is so rarely established? Where do the problems lie when it comes to implementing such a system? This p...

» FEATURED: Agile Requirements, in Context
(1018 Views) (0 Comments)
"As I discussed my May article for Modern Analyst, there's a lot of hype about the role of requirements in agile projects. Many people think you don’t “do” requirements on an agile project. Hogwash. Indeed, agile projects use requirements—but just enough requirements at just the right time." In this article Ellen covers a number of agile requireme...

» The Business Rules Approach
(308 Views) (0 Comments)
“The biggest risk to your company is not being able to change fast enough… Business Rules are the answer.” …Ron Ross I am a great appreciator of Mr. Ross. He has written extensively on the topic of Business Rules, offers excellent training on the subject, and is the keynote speaker at each year’s International Business Rules Forum. I would like...

» FEATURED: Developing Requirements in Agile Projects
(1425 Views) (0 Comments)
The latest progression in software development methods is the agile approach. Its growing popularity proves how effective it is. But two extreme—and even dangerous—views have arisen about agile development. One is that you don’t do requirements at all when you’re working on an agile project. The other is that you don’t need good requirements practi...

» Requirements for My New Car: a Fable (A Case for gathering and eliciting requirements collaboratively)
(998 Views) (8 Comments)
A lot of IT folks and or BA’s believe that if you create the requirements without the business, and then review the requirements with the business for confirmation, you can save a lot of time. After all, creating requirements collaboratively just takes too long, and the business doesn't know what they want, anyways. In addition, we (IT or BA) k...
Syndicate  


Privacy Statement  |  Terms Of Use
Copyright 2006-2008 by Modern Analyst Media LLC