Requirements Gathering

Requirements Gathering

By Harold Quinones www.guaroco.com.au

Summary

• Tools • Documentation • Collaboration • Psychology

Tools

1. Pencil and paper

Tools

2. Wireframing (Balsamiq)

Tools

3. Prototyping (Just In Mind)

Documentation

1. Technical requirements – Programming language – Web Technologies – Server resourcing – Server type – Libraries – Etc...

Documentation

2. Business requirements – Cost – Savings – Income Potential – Return on Investment

Documentation

3. User requirements – Use Cases – User Testing – Focus Groups

Collaboration

• Highly important in any large scale project

• Tools are getting more sophisticated

• Real time collaboration speeds up the process

• Collaborate internally and externally

Psychology

• Customers don’t always know what they want

• You need to help them work it out

• Sometimes best to be a problem solve

Psychology “The most difficult part of requirements gathering is not the act of recording what the user wants, it is the exploratory development activity of helping users figure out what they want.”

-Steve McConnell Author of many software engineer textbooks

Thank you

References • http://www.my-project-management-expert.com/image-files/business-

requirements-management.jpg • http://manwithnoblog.com/2009/11/26/heretical-ideas-stop-using-wireframes • https://balsamiq.com • http://www.justinmind.com • https://rachelbythebay.com/w/2013/04/17/slow • http://www.afa.asn.au/about-us/afa-investment-fund • http://www.limina-ao.com/services/evaluation.html • http://media.photobucket.com/user/mickey110257/media/Teamwork.jpg.html • http://www.cogenit.fr/ressources/livres-bleus/smv-agile-method-for-it-projects • http://www.21stcenturynews.com.au/psychology-stock-market-investing