The Art of Requirement Gathering
Download as PPT, PDF2 likes757 views
Vikrant Shukla has over 13 years of experience in technology, programming, and delivering successful enterprise Magento projects. He discusses the importance of requirement gathering for ecommerce development projects, including identifying business and design requirements, user personas and flows, acceptance criteria, and analyzing needs, risks, and opportunities through techniques like interviews and workshops. The goal is to understand motivation, success metrics, and stakeholders to build the right solution for the customer.
The Art of Requirement Gathering
- 2. Speaker Vikrant Shukla, CSPO®, is currently a Business Solution Architect (APAC) in (Magento) Adobe. He has been working with the Magento platform since it’s beta version back in 2007 building stores for clients at Magento SI Partners. Vikrant is a Certified Magento Solution Specialist and AWS Certified Solution Architect – Associate. He started his own Magento Agency back in 2015 which got acquired in 2018. Vikrant has been a Solution Architect for companies that are under Fortune 100. He has over 13 years of experience in technology, programming, mentoring and delivering successful Enterprise Magento Projects. Outside of work, Vikrant is a proud father, loves reading, music and spending time with his pets. https://twitter.com/vikrantshukla https://www.linkedin.com/in/shuklavikrant/ https://vikrantshukla.com/
- 5. Understanding Requirements PROJECT OBJECTIVE - Identify the motivation behind the project as well as the success metrics in measuring goal completion. Stakeholder identification is most important.
- 6. Understanding Requirements BUSINESS REQUIREMENTS - Identify the core business flow and modules like Pricing rules, Shipping rules, Order fulfillment workflow, Legal / regulatory requirements. Identify the process/people who have major say in the project. DESIGN REQUIREMENTS - Identify the Core Templates/Designs and Non-Core Templates/Designs. Designs that directly impact sales, CRO, ROI is Core Template and the supporting designs like emails journey, admin interface, reports are Non-Core Designs. FUNCTIONAL REQUIREMENTS - Identify all customer-facing or admin-facing feature or piece of functionality. It's about how a product must behave, what its features and functions. INTEGRATION REQUIREMENTS - Identify all third party systems, extension that the ecommerce platform has to be integrated with. Ensure to jot down minute integration details. CONTENT REQUIREMENTS - Identify the Content strategy your client will have. "Content is the kind, we have heard that always".
- 8. User Persona Identification Components of a Buyer Persona Demographics – age, gender, location, employment, education, etc. Interests – what your target customer is interested in Purchasing motivation – why your target customer wants to buy from you and what they hope to accomplish Purchasing deterrents – things that will hold your customer back from purchasing from you Admin / Business Users – business flow identification for Admin, Backend and Business Users
- 9. Example Customer User Flow
- 10. Probe and Analyze About Requirements Needs Risks Dependencies Assumptions Opportunities How to Probe? Interviews Brainstorming Observation Experiments Workshops About? User and their Goals Data Rules and Decisions Gaps How to Analyze? Thinking Dialoguing Modelling Diagramming Organizing
- 11. User Stories
- 12. Sell Emotions, Sell Stories
- 13. Acceptance Criteria The Definition of Done has to be clearly Specified. Acceptance criteria can be written in different formats. There are two most common ones, and the third option is to devise your own format: • scenario-oriented (Given/When/Then) • rule-oriented (checklist) • custom formats
- 16. Closing Remarks • There is no silly question while doing Requirement Gathering • Don’t Over Engineer • Use a Silly method called “Ask” • Customer is the King, Well but don’t treat them as a King • The psychological ownership of the project is on “You” not your “Client” http://bit.ly/2S4c58l
- 18. Thank You