How the requirements process differs in agile

How the requirements process differs in agile

Date: Aug 04, 2009
How is the requirements process different in an agile environment as opposed to waterfall or any other methodology?

Software requirements consultant Robin Goldsmith plays devil's advocate as he discusses his experiences with gathering requirements in traditional and agile environments.

More on Agile Software Development (Agile, Scrum, Extreme)

  • canderson

    Agile 2013: The project management process for baking a cookie

    VIDEO - At Agile 2013 Sujey Edward, vice president of Salient Solutions, Agile Center of Excellence, gave a demo on the project management process for baking a cookie.
  • canderson

    Matt Johnston at STPCon2011: uTest and Mozilla release CaseConductor

    VIDEO - Matt Johnston of uTest discusses the release of the beta version of CaseConductor, an opensource test case management system created by uTest and Mozilla. This is uniquely suited for distributed Agile teams. Users can now access CaseConductor and offer feedback.
  • canderson

    Carl Shaulis on Kanban at STPCon2011

    VIDEO - Carl Shaulis from HomeAway.com gave a presentation at STPCon 2011 on how testing can work in the world of kanban. Watch this video for a brief overview of the processes his company identified for expediting testing in an Agile setting using kanban.
  • Tackling the whole-team Agile approach

    Opinion - Achieving a whole-team Agile approach is hard. Here's how one coach took unusual measures to get her team members talking, asking each other for help and tackling each issue as a team problem.
  • Continuous delivery benefits the business side

    Tip - Continuous delivery emerged as a way to reduce risks around software releases. Now continuous delivery benefits business executives by facilitating fast feedback on products and strategies under development.
  • Explore the benefits of continuous delivery

    Tip - An outgrowth of Agile, continuous delivery lets organizations release small, incremental updates constantly. What's more, it keeps the codebase stable and boosts quality over time.
  • How can Agile methodologies be used with other methods?

    Answer - How can software testers best combine Agile with other development methodologies? Software QA expert Gerie Owen describes how developers at organizations that don't formally use Agile can still benefit from the methodology.
  • specification by example (SBE)

    Definition - Specification by example (SBE) is a user-driven contextual approach to defining software requirements. This approach encourages communication between a project's business owners and the software development team while also aligning software specifications with user acceptance testing.

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: