arlene trimbleAssistant IT Director| Local GovernmentAlamo, Ca, United States
How did you gather, document, and manage requirements in the Agile world?
What worked best? Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
First of all take into account that agile is not a method or methodology neither software or IT related only. Second, take into account that no matter the approach you are using you never gather requirements, you ever elicit needs/wants/desires/wishes that you will transform into requirements. The process and method is determined (most of the times) for the methodology you decide to use. Former agile software development methods become agile solution delivery methods today and you can find a great offer from SCRUM to DSDM. Agile is "constant value delivery to the customer and quality" so you can use agile in "traditional" approach (like waterfall for example) to do any type of thing inside the approach. For example, manage requirements Saving Changes...
Steven ZacharyDirector| Alberta Health ServicesCalgary, Alberta, Canada
I'd have to echo Sergio here. Processes and tools are not important, rather the supporting framework that guides your actions.
I would highly recommend you read up on user stories, epics, backlogs and read one of the thousands of articles debunking the "agile means no documentation" myth.
