Sunday, May 11, 2008
In Association with:


Proud Media Sponsor of:

ProjectWorld & World Congress for Business Analysts regional conference



Our Sponsors


Business Analyst & Systems Analyst Community

Want to Shine as a Business Analyst or Systems Analyst?

Join the Community that Will Make You Succeed (it's FREE)!

This community and resource portal is…
“The One-Stop-Shop for the Business Systems Analyst!”

Featured ArticleExplore the Site
Developing Requirements in Agile Projects

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 practices.

In truth, agile development processes are based on good practices. Most of them are not new but are being reconfigured, along with good product development, engineering, and project management practices. In my work with agile teams, I’ve noticed a number of key practices.

Author: Ellen Gottesdiener, Principal Consultant, EBG Consulting, helps business and technical teams get product requirements right so their projects start smart and deliver the right product at the right time.

Recent ArticlesRecent Forum PostsRecent Blog Entries
The Business Case for Business Analysis
Project Management and Business Analysis: Dependencies for Success
Why We Resist Planning
Enterprise Architect for Business Analysts
Developing Requirements in Agile Projects
Interview QuestionsExternal SitesTraining Courses