Writing Agile Requirements

The beginning of a project generates a lot of great ideas. But until a structure or cohesion is applied to these ideas, they end up being a loose collection of separate ideas with no direction. Writing agile requirements brings cohesion and direction to the noise. We've been continually improving user driven agile for a while now. Click through the presentation below to see the approach that works for us.

Related posts:

  1. Integrating Design and Agile Development
  2. Upcoming Talk at RIApalooza: Fast. Smart. Agile. User Experience Driven Agile Development
  3. Wireframing with incomplete requirements
  4. What makes a good requirement document for an agile project
  5. Writing Technical Requirements: The Third Commandment

Comments: 1 so far

  1. [...] out of agile and user experience design best practices, and includes lightweight, just in time requirements gathering and design, test-driven development, pairing, daily scrums, weekly demos, two week development [...]

    Pingback by Ten Keys to Successful Software Development: #9: Respect the Process | Pathfinder Software Development | Blogs, Monday, August 17, 2009 @ 3:15 pm

Leave a comment

Powered by WP Hashcash

Launch: Pathfinder Newsletter

    Get a monthly update on best practices for delivering successful software.

    Subscribe via email


    Subscribe via RSS      RSS icon

Topics

Search

WordPress

Comments about this site: info@pathf.com