Defining Requirements When the Time Frame is Short

Member Submitted

Recent industry studies show that modern software projects on average spend 40 percent of their effort on rework. As a result, over 60 percent of software projects overrun budgets, miss schedules, and substantially reduce delivered functionality. This article describes how to define requirements in an Agile environment, including a survey of the most popular methodologies used.

About the author

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.