Agile requirements analysis

Malcolm Bronte-Stewart

    Research output: Contribution to conferencePresentationpeer-review

    Abstract

    Imagining systems may help us to explore and investigate situations. Systems thinking creates and encourages questioning. In requirements analysis some of the most useful of these questions are concerned with purpose. If a situation is viewed as a system we may be prompted to ask about its
    perceived purpose(s) and parts, which are themselves systems with purposes. User Stories capture requirements in a succinct and straightforward way. The aim of this paper is to explain, and provide a worked example of, an approach to Agile information systems (IS) requirements analysis. Based on
    systems thinking principles this approach has been an important part of a number of IS consultancy projects. It depends on System Pictures as vehicles for inquiry, communication and systems analysis. The process of constructing System Pictures involves stakeholders and roles. The participatory nature of this investigation process seems to focus the discussion of IS project objectives, existing problems, desired improvements and the need for change. Requirements that emerge from this analysis can be
    recorded as User Stories.
    Original languageEnglish
    Pages21-21
    Number of pages1
    Publication statusPublished - 2017
    EventInternational Information Management Association Conference 2017 - Paisley, United Kingdom
    Duration: 11 Sept 201713 Sept 2017

    Conference

    ConferenceInternational Information Management Association Conference 2017
    Abbreviated titleIIMA/ICITED UWS Joint Conference
    Country/TerritoryUnited Kingdom
    CityPaisley
    Period11/09/1713/09/17

    Keywords

    • System Thinking
    • User Stories
    • System Pictures
    • Requirements analysis
    • IS project
    • Investigating problems and opportunities
    • Roles

    Fingerprint

    Dive into the research topics of 'Agile requirements analysis'. Together they form a unique fingerprint.

    Cite this