In a short time we will be on our way to Geneva to run our first requirements elicitation workshop with representatives of the International Organization for Migration (IOM), the United Nations High Commissioner for Refugees (UNHCR), the United Nations Office for the Coordination of Humanitarian Affairs (OCHA) and the International Committee for the Red Cross (ICRC).
We spent the last few weeks preparing for the workshop, including finding a meeting room where we could spend two days discussing system features and user stories. Fortunately the canton of Geneva has made it easy for NGOs to search and book affordable meeting rooms. You can access a list of possible meeting rooms here.
With regard to the method, we settled on the Agile Software Development methodology to elicit our stakeholders’ needs by means of brainstorming sessions and user stories. The latter will constitute our preliminary backlog of features which we’ll use to develop the PI system in iterations. First coined in 2001, this methodology is now widely in use alongside similar approaches such as Extreme Programming and Scrum. We copied below its core principles.
Manifesto for Agile Software Development
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
That is, while there is value in the items on the right, we value the items on the left more.
Source: Beck, Kent; et al. (2001). “Manifesto for Agile Software Development”. Agile Alliance. Retrieved 14 June 2010.
Stay tuned for our next post where we’ll share the preliminary results of our first workshop as well as a series of lessons learned based on the feedback from the workshop participants.
(This is a cross-post from HIF’s PI blog.)
HIF is a programme managed by the ELRHA (Enhancing Learning and Research for Humanitarian Assistance).