2. Agenda
Introduction
What do I mean by “business requirements”
Business requirements for e-commerce
Business requirements tools
Storyboarding / Flowcharts
User feedback
Use case diagrams
SWOT
MoSCoW
Summary
3. Rob Peterkin
About Me
National Diploma in Aerospace Engineering
FdSc Degree in Computing & Internet Technologies
BcSc (Hons) Degree in Business & Information Technology
Project Manager at Screen Pages
4. What do I mean by “defining requirements”
This presentation is tailored towards an ecommerce project/website but the
tools can be used anywhere.
Who are your customers now and in the future?
Do you need this functionality now, later or never?
What does your site need to do to satisfy the users?
Want vs Need
Taking your opinion out of it
Design Functionality Essentials
Branding Gift vouchers Stock management
Colours Search filtering Payment gateway
Responsive 3D product images Content manageable
6. Storyboarding / Flowchart
Drawing the process that the customer will go through to achieve a specific
action on the site.
User Creates an
account
User lands on
homepage
Log In?
Does the User have an
account?
User Logs in
Continue Shopping
Select A Category
Select an item
Does the Item need
configuration?
Configure Item
Add to Basket
Have they
Finished
Shopping?
Do they have a
discount code? Add Discount code
Proceed to
Checkout
Have they
logged in?
User Creates an
account
Does the User have an
account?
User Logs in
YES
YES
YES
YES
YES
YES
YES
NO
NO
NO
NO
NO
NO
NO
Create a list of steps you
require the user to take
and how you would like
that process to fit
together.
This will give you the
basic functionality
elements that you need in
your site and you will be
able to judge future
changes based on their
impact on these journeys.
7. User Feedback
Need to establish what you need for your site?
What is working well and not well on your current site?
Speak to your suppliers, they may have experience with solving these
problems for their other customers.
Ask Your Users!
Customers Staff
Email or on-site surveys like SurveyMonkey Individual meetings
Ask friends and family Group meetings
3rd party services like whatusersdo, User
Testing
Feedback forms
8. Use-case Diagrams
Who does what?
• Integration to your back office system?
• Can a team or member of staff replace
a 3rd party or could a 3rd party replace
a team or staff member?
• Can the processes be streamlined?
Think about user roles!!
Admin
Telephone Clerk
Edit Orders
Manage products
Process Telephone
order
Add Products
Delete Products
Edit Products
Create Customer
Account
<<include>>
<<include>>
<<include>>
<<extend>>
9. SWOT
This is commonly used to determine an organisations good and bad points.
It is broken down into 4 headers:
10. SWOT
As an example, this is a simple SWOT analysis for using web based stock
control system built into your ecommerce platform rather than dedicated
stock control system
Strengths Opportunities
Better customer experience online Save costs from running two systems
One system to manage Quicker go live because of no integration
Weaknesses Threats
Requires staff to manage manually May not be suitable in the future
Not as robust or feature rich Is unavailable if the ecommerce site is down
11. MoSCoW
A tool to help prioritise all of your requirements.
4 heading to group requirements:
Must Have
Should Have
Could Have
Won’t Have (for now)
12. MoSCoW Example
Must Have Could Have
The ability to sell products online BOGOF product promotions
The ability to take payments from customers Email when back in stock
Localised versions for English and German Online/offline gift vouchers
Integration with retail EPOS system Social shopping functionality
Should Have Won’t Have (for now)
Customisable e-gift voucher 3D product images
Integration with delivery courier system A physical store locator
Product reviews Product promotional labels
Multi-select reviews Personalised products
13. Summary
PLAN! PLAN! DOCUMENT! PLAN!
Write down what you need, the brain is not a reliable database
Think about your business processes
Look for improvements
Challenge “we’ve always done it this way”
Who does what?
Understand your user journeys
Think about now first and then future
*****AT THE END*********Example of clothing brand who had an unskippable landing page video (SINGING DUCK) for the homepage because the owner thought it was fun annoyance to people.
These are some of the tools that can help you define your requirements. There is a plethora of information out there and in this presentation I will just give short examples on how they can be used.
The idea for us would be to complete any process as in as few steps as possible, as a thought if you are adding new functionality then work out its impact on the process to see if makes the process more complicated that its worth.
Talk about a bed-linen retailer who did some user testing after launching their new site, not before, it became apparent very quickly that they needed to allow their customers to filter by bed size, which all their customers needed but they didn’t think of because they knew that all their products come in all sizes.
Quick overview about roles in your business, need to identify who does what and why they are the role that do it
Talk about the headings of each part, do not go into detail.
Amount of images relates to the priority of need – Must have 1 image, should have multiple images, could have multiple images and a video