APPLAUSE Software Testing with Agile GetYourGuide New Customer Conversion DAIMLER Project briefing Customer Alliance Workshop AB testing

1. Agile Case Studies - Berlin 2016
APPLAUSE Software Testing
1-Understand the main terminology of software testing
2-Compare the different test-strategies
Test-case driven vs. explorative ( scripted tests vs exploratory tests)
Lab-testing/In-House testing vs. In the wild testing
Automated vs. manual testing
3. Case study Changers App vs GoGetDo App
4. Elaboration of a usability study for the car-configurator of Daimler:
Tracking results or data collection
Usability testing
Load testing
5. Viventura - example of a test project with Agile.
GetYourGuide New Customer Conversion
DAIMLER Project briefing Customer Alliance
Workshop AB testing

2. APPLAUSE Software Testing
1-Understand the main terminology of software testing
1. How does In-The-Wild Testing differ from other Test-strategies (Lab / In-House / Beta-Testing)?
Lab environments​ or so called “ sterile environment” are places of perfect connectivity, limited devices and
up-to-date operating systems.
In-the-wild testing​ ensures the apps work well in real world situations in term of range Devices, location
(Connectivity changes with network and location ) and software.
Beta testing​ is a form of external user limited audience acceptance testing outside of the programming team
known as beta testers.
In-The-Lab Testing / In-House :
PROs CONs
● In-house team
professional testers
who are tightly
integrated into
SDLC.
● Better internal
communication.
● Lab environments are places of perfect connectivity, limited devices and
up-to-date operating systems, ​they can not reproduce real world
situations​.
● Capacity constraints; testing may not match user demographics;
maintaining adequate collection of mobile devices is prohibitively
expensive.
Beta Testing :
PROs CONs
No direct costs; ​lives outside the test lab
environment (in real-word environment)​; ​range of
mobile devices, carriers (Vodafone), OS, locations.
Users are not professional testers​; provide
subjective feedback that is not diagnostic, which
raises the cost for the company; also puts
unfinished product in front of customers.
In the Wild Testing (Crowdsourced Testing) :
PROs
Real-world condition : lives outside the test lab across real devices (in real-word environment),
carriers, OS and locations; professional testers who mirror end users; access to range of mobile
devices & connections​.
2. In which stage of the SDLC do our Testing Services come into play?
1

3. (Please note the different testing services: functional testing, usability, security, load and localization testing)
Software Development Life Cycle , (e.g waterfall):
1. Requirement gathering and analysis
2. Design
3. Implementation or coding
4. Testing
5. Deployment
6. Maintenance
Testing phase 4 :
● functional testing​ (unit testing, integration testing, system testing, acceptance testing ).
● non-functional ​testing the quality characteristics of the component. Non-functional refers to aspects of
the software that may not be related to a specific function or user action such as scalability or like
usability, load testing​, ​security testing, localization testing and beta testing.
Software Development Life Cycle , (Agile):
Test Strategy in agile, each Sprint includes :
● Test automation.
● Run automated regression tests.
● Perform non functional testing (load, security, usability etc) – Demo to the stakeholders.
● Estimate tasks (QA input) – Write test cases using stories (QA).
● Unit/ Integration tests: automatic test on code level run every night (​nightly builds​) or after new code
is added (​Continuous Integration​). →​ Continuous improvement.
● Bugs found are logged and prioritized during next sprint planning. After all prioritized bugs are fixed,
the feature is ready for System Test at the end of the project.
Advantages :
● Test in iteration
● Early test
● Testers are more integrated
● Continuous improvement
2

4. 3. Explain the connection and the cooperation between these roles: Scrum Master, Product Manager,
Developer and QA by using an example (preferably from your own work experience).
Scrum master Product Owner
--> PO :
● Help the product owner choose the right
agile product management techniques and
tools.
● Support the product owner in making
product decisions and fixing issues.
-->Team :
● Help the team collaborate effectively and
manage their work successfully so that they
can make realistic commitments and create
product increments reliably.
● Encourage the team to work with the
product owner on the product backlog.
● Ensure that the team has a productive work
environment.
Vision and Strategy
● Provide a vision to the team.
● Communicate the value proposition and the
business goals of the product.
● Formulate a release goal.
Product Details
● Proactively work on the product backlog.
● Provide direction and make prioritisation.
● Invite the right people and choose the right
techniques to collect feedback and data, for
instance, invite selected users the review
meeting and carry out a ​usability test.
Collaboration
● Be available for the team.
● Attend the sprint meetings.
● Product Owner:​ Manages the ​backlog with an external mindset, represents the interests of the clients
and ensure ROI.
● Scrum Master:​ Manages ​process with an internal mindset, protects the team interests and coaches.
● Development Team:​ Manage ​work.
● QA Management at Viventura ​was part of the Scrum Team, stakeholder, end-users. So everyone could
be responsible for QA. Everyone is accountable and quality is everyone’s responsibility. When a mistake was
encountered, everyone gathers together to see what went wrong and how it can be avoided in future during
the retrospective meeting.
3

5. 4. What are the benefits, from an “everyday business“ point of view, if our clients work in an agile setup?
Definition ​: Agile is a time boxed, iterative approach to software delivery that builds software incrementally
from the start of the project, instead of trying to deliver it all near the end.
Advantages for the client Benefits
1. Quality improves because testing starts from day one.
2. Visibility improves because you are 1/2 way through
the project when you have built 1/2 the features.
3. Risk is reduced because you are getting feedback early.
4. Customers are happy because they can make
changes without paying exorbitant costs.
5. Efficient way for handling change.
● May offer more tests to
the clients.
● More reliability about the
product quality.
● Better client satisfaction.
● Increase Collaboration and
communication.
5. What test strategy / strategies would you generally recommend for a QA-setup that runs parallel to
the sprint(s)?
Parallel QA Process Day-to-Day Sprint Execution
QA should take place in parallel with development
● Stories should be tested as they are
completed during the sprint.
● Prevents overload of the QA team at the
end of the sprint (which is typically what
happens on traditional projects).
● Reduces the risk of surprises.
QA may not be completed by end of sprint – that’s
okay
● QA for stories completed near the end of a
sprint may spill into the next sprint.
● This is not unusual and ought to be
accommodated.
Communication
● Regular interaction with developers and
Product Owner.
● Comments on tracking system items (epics,
stories, bugs, etc.) for historical reference.
Participation in core Agile meetings
● Kickoff, sprint planning, stand-up, demos,
retrospectives, estimations.
Parallel Testing
● On days when user stories are completed,
emphasis is on those using ​manual testing.
● On other days, emphasis is on ​system
regression testing​.
● On some projects, writing of ​automated
regression tests​ is a QA responsibility.
4

6. 6. How does the connection between agile development, continuous integration, “Just in time” and “Stop
the line” look like?
Agile Agile​ is based on ​JIT​. User stories are created when they are needed and not before.
Releases happen when there is appropriate value in releasing, not before and not after.
Agile & CI​ : deliverable = product ready. Improvement process with retrospective meeting -
high value with daily feedbacks.
Continuous
integration
Continuous integration​ is a software development practice specifically designed to improve the
build and test process. Teams integrate their working code early and often, usually daily, so
as to reduce integration issues.
The objective of ​continuous integration​ is to ​eliminate waste​ and rework using rapid feedback.
This approach improves release quality and leads to significantly reduced integration problems.
Thereby accelerating the ​overall release process​, and ​saving time​ and money.
Just in time
JIT​ is vital to produce with zero defects or these defects can disrupt the production process
-->ex from Lean: The right material at the right time at the right place In the exact amount.
Stop the line
Stop the Line​ is that when you find a defect that you stop to build and gather the important
stakeholders together to look for the root cause. A ​Continuous integration​ system is
comparable to the “​stop the line​” culture.
5

7. 2-Compare the different test-strategies
Test-case driven vs. explorative ( ​scripted tests vs exploratory tests)
Exploratory testing​ is any testing where the tester is learning and designing tests on the fly. The tester are not
guided by​ existing scripts​ and they use their skills to explore the product and learn as they test. They are not
constrained by a pre-defined scope.
Lab-testing/In-House testing vs. In the wild testing
Ex : Apple's "Antenna-Gate" fiasco or to ​Rely too heavily on "lab-testing" :
1. An expensive and elaborate lab is still a lab :
No matter how much a company spends to replicate reality, it will never become reality. A lab is still a lab.
2. Need a fresh set of eyes :
Testing was completed by those who were extremely close to the product, who knew the device. Only through
'in-the-wild' testing​ can a company expect to uncover these type of unique issues.
3. Global users so Global testing :
To sum it all ​: the product needs to work where your users are. For 99.9% of apps, this is not in a lab.
Automated vs. manual testing
QA analysts and IT teams are often confronted with the same question when testing a software project --
whether to go with ​manual software testing​ options or to try out new ​automated techniques.
Manual Software Testing ​is the process of going in and running each individual program and comparing the
results to the expectations to find the defects in the program. Essentially, manual testing is using the program
as the user would under all possible scenarios to make sure all of the features act appropriately.
Manual Software Testing Automated Testing
● small company with few financial resources
● to see real user issues
● flexibility
● short-term projects
● usability tests
● big companies
● many system users
● quick and effective tests
● easy process to repeat tests
● better team collaboration
● when the costs of testing <​ ​efficiency gained
Automated Software Testing ​uses automated tools to run tests based on algorithms to compare the developing
program’s expected outcomes with the actual outcomes. If they are aligned, the program is running properly
(likely bug free). If not, IT team edit the code and continue to run tests until the outcomes align.
Sometimes, it’s hard work typing in the same data into the same forms over and over again in manual testing.
When using automated tests, any member of the team can automatically see the results published to the
testing system. This provides for better team collaboration, and a better overall product.
6

8. 3. Case study Changers App vs GoGetDo App
Elaboration of a test concept for two mobile applications starting with the conceptual phase all the
way up until the user-acceptance test prior to the release.
Introduction :​ ​Define test plan objective
Changers GoGetDo
Functional feature to test : tracking and
geolocation.
Functional feature to test : verification user
process (email and ID).
Scope :
(​Defines the features, functional or non-functional requirements of mobile app)
Changers GoGetDo
measures the distance travelled, calculates the amount
of CO2 footprint saved, and rewards you with bonus
points called Recoins.
connects users with people living close by to
help them to get their tasks done.
Methodology :
7

9. 1: Test Framework : Agile
2: Test Approach :
● A mix of manual and automated approach.
● Alternates ​lab and in-the-wild tests
3 : Testing Types
A mix of manual testing and automated testing will implemented in
the following practices.
Labs Testing : Integration testing
Changers GoGetDo
Developers​ write automated tests for story “As an user I
want to calculate distances” using geolocation GPS
emulation.
QA Team​ write automated tests for story “
as an user I want to apply to offers”.
Developers​ will be performing automation testing (​integration tests​) in order to check app specific
functionality ​that could not be tested before in-the-wild testing. QA Team​ will perform manual testing to test
all other features, eventually report bugs.
Labs Testing : Functional testing
Changers GoGetDo
Testers will perform manual testing: sign up,
login, view account, view Recoins.
Sign up, apply process, payment process, contact
process.
In-the-wild testing :
Changers GoGetDo
Crowdsource testers in performing functional &
usability testing on their everyday activities
(going to work, shopping) using modes of CO2
free transport (walking, bike, train...).
Crowdsource testers in performing functional testing
Sign up, verification user, application to offer
process, payment process.
8

10. Usability Testing (examples of feedback received) :
Changers GoGetDo
● Settings -->Visibility , Changers propose
the users name and profile picture to be
displayed, but there is no feature to
upload the picture.
● Amount of calories burnt is not displayed
when user bike/jog.
● There is no records of the journeys.
● There is no explanation about verification process and
any email is sent to explain the user verification.
● When an user sign up, no email is sent to confirm it (
or to welcome the new user, to explain how the App
works or the process to be eligible to apply to the
offers).
● When an user send a feedback through the contact
form, no answer is received after 72h.
Performance testing :
● Check memory, CPU and battery usage, when application is in active state.
● Check memory, CPU and battery usage, when application is running in background.
● Check if data usage is reduced to the minimum.
Regression testing :
Depending on client budget we will plan for the ​QA Team​ either only manual testing or a mix of manual and
automated testing to perform regression tests (insures that basic functionality works using continuous
integration).
Testing Tools :
Use Tools
Automation Tool
(write automated test case)
Experitest
Bug tracking tool Jira
The use of an automation tool as Experitest or equivalent has the following advantages:
● shared by different QA teams or developers.
● reduces device booking issues.
● can connect with other tracking tools as Jira.
9

11. Example :
Changers CO2 fit
● Functional : Geolocation doesn’t work properly
● Bugs —> Apps restarted frequently, consume extra battery power
GoGetDo
When an user want to apply for a job, a message is displayed “ You need to verify your email first”
without any further action.
10

12. Where : Test Environment
Mention in detail about the devices, Firmware, Emulators, OS, Browsers & corresponding versions to be used
while testing.
Devices Firmware Emulators OS
Iphone 9.1 Experitest IOS
Google Nexus 6.0.1 (Marshmallow) Experitest Android
Ipad 9.1 Experitest IOS
When : Test Schedule
With Control Procedures
● Reviews and Inspections
● Bug Reviews (prioritize ranking)
● Change Request
Who
Roles and responsibilities
QA Manager: Sébastien Donné QA Analyst: <tester(s) name>
Automation Engineer: <engineer(s) name> Developers: <developer(s) name>
Business Analyst: <business analyst name> Installation team: <integrator name>
Testing summary
Test Execution Summary and Coverage Analysis
Ex :
Total defects found
Total defects closed
New stories implemented
Comments
Risks
Each project group is responsible for identifying, reducing, and tracking
risks. Risks can be technical, management, personnel and requirements
– like Device unavailability, lack of expertise or changes in functional
requirements.
Open items and version history
● Mentions all the items that are still opened.
● Maintains a history version of the document.
11

13. 4. Elaboration of a usability study for the car-configurator of Daimler:
Link to the test
Known problems:​ Few users complete the car configuration; most users quit at some point. High degree of user
dissatisfaction!
Tasks:
○ Explain the process of how you would set up / elaborate a test concept with the client.
Continuous improvement plan :
1. Assessment of current situation​: Findings, root causes and remedies
2. Rationale:​ Why will you implement the improvement?
3. Objective​: What will success look like for the client?
4. Timeframes for Improvement Initiatives:​ When will the improvement take place?
5. Responsible Group:​ Who will be accountable for implementing the improvement?
6. Activities that will be engaged in to support the improvement:​ Who will do what by when?
7. Overcoming obstacles
8. Communicating the improvement effort:​ What will you say and to whom?
9. Monitoring plan progress​: How will you chart your progress? What methods/tools will you use?
10. Sustaining the improvement effort:​ How will you ensure the improvement effort
11. Continues to be implemented?​ What methods will you use for accountability?
12. Budget and resource implications
What could the setup for the test potentially look like?
Tracking results or data collection
Usability testing
Load testing
AB testings
Implementation
Results
12

14. ○ Which qualitative and quantitative questions would you ask? What are your
hypotheses? What UX-metrics would you use (e.g. SUS)?
Questions : ​The Attitudinal vs. Behavioral Dimension "what people say" versus "what people do"
Main quantitative Marketing Metrics :
● Conversion rates.
● Page views for each “ build your car” step ( each steps of the car building process, devices)
● Bounce rates ( each steps of the car building process, devices).
Qualitative question : ​I would ask Daimler to provide all individual interviews, feedbacks and ​satisfaction survey
the company get about the online car building tool from the users.
Hypotheses :
1- RWD is not optimized.
2- Loading time is too long.
3- Design & copywriting issues.
What UX-metrics would you use (e.g. SUS)​ :
Objective measurements Subjective measurements
Usability : (analytics tool & clickstream)
● time on task
● success rate
● navigation use
Engagement : (VoC tool)
● flow state
● data entry
Conversion : (analytics tool)
● conversion rate
SUS​: ​System Usability Scale​ is a Test Level
Satisfaction questionnaire given at the end of the
session. It measures their overall impression of the
usability and experience.
Contextual user interviews ​: a researcher meets
with participants one-on-one to discuss in depth
what the participant thinks about the “Build your
B-Class”.
13

15. Exemple SUS :
SUS
Strongly
disagree
Strongly
agree
1 2 3 4 5
I found the “Build your B-Class” unnecessarily complex.
I thought the “Build your B-Class” was easy to use.
I would need the support of a technical person to be able to use it.
I found the various functions were well integrated.
I thought there was too much inconsistency.
I would imagine that most people would learn to use it very quickly.
I found the “Build your B-Class” very cumbersome to use.
I felt very confident using the “Build your B-Class”.
I needed to learn a lot of things before I could configure my car.
○ How would you analyze the data in order to show it / visualize it in a report?
Create a dashboard with objectives measurement, heatmaps extracts from analytics tool
SUS :​ calculate the SUS score, first and then convert the ​SUS scores to Grades (A+ to F)​. SUS scores have a
range of 0 to 100. Average is 68.
Contextual user interviews​ : ​report. (usability)
Solution AB testing : ​report with AB testing tool like Optimizely or AB Tasty.
Satisfaction Survey :​ give result from the survey with a significative number of answers.
○ Show 3 UX-problems the car configurator has and propose possible solutions.
UX-problem 1 : ​Responsive Web Design is not optimized for Mobile devices.
Proposal : ​craft ​site to provide an optimal viewing and interaction experience across a wide range of devices.
UX-problem 2 : ​loading time to update the data is too long.
Proposal : ​Loading test.
UX-problem 3 : ​Design or copywriting issues.
A
14

16. B
C
D
E
15

17. 5. Viventura - example of a test project with Agile.
Context :
● Build a new software/backend CRM, Booking, Suppliers Management, Finance Tools and Marketing
Tools with Symfony using AGILE methodology SCRUM. We built mostly 40 modules/admins.
● International platform with 100 users across 15 countries (remote supervision in different timezone
and languages English, Spanish)
● Migration project with data from legacy system (e.g.10 000 clients)
Requirement gathering and analysis :​Collecting data from old client admin, End users - Sales team
Design :​ ​Client Admin design​, I have provided “the design document”
Implementation​ : 25 sprints
Example​ : Client Admin, one user story
Testing : ​Method - Manual testing ( exploratory & user case scenarios) --> IT developpers, Product Owner,
Head of sales, Sales Agents.
IT developers :​ unit test/ integration test (migration).
Product Owner:​ functional test, acceptance user test.
Maintenance : improvement and Fixing bugs
Deployment - Result : CLIENT EDIT Deployment - Result : CLIENT Admin
16

18. Design document
17

19. GetYourGuide Case Study
Scenario :
You are responsible for the “New Customer Conversion” mission at GYG. Our vision for the New Customer
experience is:
● Connection with the Destination
● Easy to use
● Worry free
Please create a short presentation that you might deliver to other leaders in Product and Technology about
how you would expect to evolve the experience for first-time Customers unfamiliar with GYG over the next
4 months assuming you have 3 developers working with you.
Important topics to include :
● KPIs:
○ Please detail the KPIs that you would track to measure progress towards achieving your vision
of converting more visitors in New Customers.
● Roadmap:
○ Please outline a roadmap with the name and description of features or initiatives you expect
to focus on over the 4 months.
18

20. Canvas
Problems :
lack of trust
1- prospect get some
difficulties to
achieve their
payment
2- Lack of trust about
product quality &
price value vs
competitors
Solutions :
record customer’s mode
of payment for next
bookings (optional)
include/ not include
must be highlighted in
the product page
get better customer
feedbacks
user requests must
match with search
results page
USP :
Payment
achieved when
booking is
completed
from supplier
book with
confidence : if
your activity is
cancelled after
confirmation,
we offer the
tour or refund
Unfair advantage :
customer DB
feedbacks DB
Customers
segment :
People who plan
to travel or
currently
travelling
Key metrics :
Sales/Unique visitors
Tour page
Tours quality
Channels :
organic : SEO, Blog
paid : SEM
referral programs
Problems :
1- 1% of the new
customer revenue
come come the App
vs 4% from existing
client
2- time to confirm
the booking is too
high
Solutions :
confirm the booking
within a hour when
activity take place the
same day, d+1 or d+2
otherwise confirm the
booking within a day
App : display only
available activities
according to the chosen
date
USP :
confirmation
booking within a
day
Unfair advantage :
Product & supplier
DBs
Customers segment :
Traveller with a
smartphone
Key metrics :
Length of booking
confirmation
Number of App
downloadings/ sales
Channels :
GYG App
19

21. Backlog orders by priorities
1. as a Customer, I want a booking confirmation within a day to organise my journey
backend : for each activity, GYG and the supplier get in the same time the booking as a ticket in the reservation
software, when the booking is confirmed by the supplier, GYG records the duration between the booking
& the confirmation time
2. as a customer, I want a booking confirmation within an hour if my activity takes place today to organise
my day
backend : if the activity booked takes place the same day or D+1, the supplier has to answer with high priority,
so the ticket move up on the “ booking waits to be confirmed” list
3. as a visitor, I want an answer to my question about the product within 1 hour if my activity take place
today to org. my day
backend : when the activity booked takes place the same day, the supplier receive a ticket “message from
client” with high priority to answer
4. as a visitor, I want that my request matches exactly with the search result page to choose quickly my
activity
5. as a visitor, I want to have the possibility to receive a call back from the activity’s organizer before I made
my choice
backend : in the form sent to supplier from the client “​Ask a question about this activity”. Add a checkbox
above : want a call back when it checked, the Ph. number field become mandatory. the supplier receive
the ticket with tag “phone”
6. as a Product manager, I want to know what the users look for in the GYG search engine to better
understand theirs needs
backend : create a new Database that record all client requests with filters ( user’s country, request, date of
request) and sent a monthly report the product manager responsible
7. as a visitor, I want to read tour’s feedbacks on the GYG App according to the ranking evaluation to
determine my choice
8. as a visitor, I want to be displayed on my GYG App/website/tablet/mobile only activities bookable to
avoid waste of time/energy
backend : add a field in the activity admin “ limit time to book” with duration in hour filled by the supplier,
when the time limit is reached, the activity disappear from the result search page.
9. as a product manager, I want the tour guide be evaluated ( when applicable ) to better evaluate the
20

22. product
backend : add in the feedback form sent to the customer in the “​Could you tell us a little more about it?”
section”, a tour guide evaluation with stars ratings
10. as a visitor, I want myself to set up the language on the GYG App regardless of my phone settings
11. as a visitor, I want to know who is the supplier responsible for the activities I am interested in
12. as a visitor, I want to know the discounted activities with according to my desire holiday location
backend : create a secure DB with the credit card customer data
13. as a visitor, I want to know how much do “what is not included” costs to determine my budget
14. as a customer, I don’t want to fill again my personal datas each time my make an order
backend : for each activity page backend page add a field next to each “what is not included” service with price
filled by the supplier
15. as a product manager, I want only best tour pictures displayed in the tour page
backend : only publish verified by GYG pictures with high rate connected with the product
16. as a visitor, I want to read the entire answer in the help center rubric without additional click
17. as a visitor, I want to read feedbacks by clicking from the customer review chart on the product page
18. as a visitor, I want to know what is a “Guidy award” without a click on the seal
19. as a visitor, I want to understand what is a bestseller tour to choose the right activity
20. as a visitor, I want to understand what is a featured tour to choose the right activity
21. as a visitor, I want to be able to print out one page activity’s program details
22. as a customer, I don't want to fill in my payment method each time I book an activity
23. as a customer, I don’t want to worry if I lose my printed voucher in order to be relax before it
24. as a costumer, I want to have the opportunity to chat with my fellows when the activity ends
25. as a customer, I want to be able to share with the social network the excursion I’ve participated
26. as a product manager, I want to ensure that the supplier data ( phone, email) is up to date
backend : send a cronjob reminder email to the supplier every 2 months with a link to his backend page profile
to update it if necessary
21

23. 27. as a visitor, I want to see pictures on the search results page which tempt me to explore it
28. as a customer, I want to fill just the useful fields in the checkout page to make my booking faster
29. as a customer, I want to fill in faster as possible the feedback form without thinking about the meaning of
the questions
30. as a customer, I want to be able to load my own avatar to recognize instantly my accoun​t
First sprints (Duration 2 weeks per sprint)
Sprint # 1 focus on :
● Confirmation booking delay
● Visitor’s request matches with the results displayed in the search results pages
User stories from 1 to 4 as proposal for sprint #1
Sprint # 2 focus on :
● Visitor activities interest
● Improve App user experience
● Relation between the supplier & the customer
User stories from 5 to 11 as proposal for sprint #2
Sprint # 3 focus on :
● Help the visitor to find quickly his/her activities : Product infos
User stories from 12 to 21 as proposal for sprint #3
Sprint # 4 focus on :
● Facilitate the payment
User story # 22
KPIs
KPIs​ for the next 12 month
22

24. DAIMLER
Project briefing Customer Alliance
Methodology
I choose the SCRUM framework to make a proposal to implement the new feature.
As a product manager, it makes sense to create workflow only for one month. During that period and thereafter, the
backlog is continuously fed/supplied with new user stories.
I designed one use case, 2 user flows, propose some key metrics and wrote user stories that may be used as support
documents.
Opportunity
● Send the invoice to guests after they have checked-out by E-mail.
● If the booking process is quicker, more sales will be made.
USP
● Simplicity, usability and responsive design.
Benefits
● Increases sales.
● Keep the customer invoice into Booked Application.
Solution Overview - Backlog​ - ​General use case
Estimated development Timeline : 1 monthTeam : In-house Development
Checkpoint :
● End of Sprint #1 first week , AB test user story #1
● End of Sprint #1 first week ​New design ​user story #3 ​ready & approved
● End of Sprint #2, according to AB test ​user story #1​ results → decision for the next release
User story 1:
Estimated Story Points (​Fibonacci)​: 3
Business Value (​Fibonacci​ ): 5
As a guest web user, I want to choose my accommodation as quick as possible in order to gain time.
User flow concept
23

25. 2 benefits :
● The page looks easier to fulfil.
● The client can see the additional services offered without scrolling down.
Acceptance criteria :
● Configure room page : delete the Guest identification part ( no need to fill in this data when the room choice is
not already made). It's still a product page.
Book form step 2 : Your personal details
● By default, don’t ask for the name of all the guest fields.
● By default, only show 4 mandatory fields ( Salutation, First name, Last name, E-mail).
Responsive design :
● Valid for Android ​7-inch and 10-inch tablet​ user.
● Valid for iOS ​7.9-inch and 9.7-inch tablet​ user.
● Valid for Android smartphone user.
● Valid for iPhone user.
User story 2 :
Estimated Story Points : 3
Business Value : 0
As a Host user, I want to test the feature (user story #1) in order to validate it.
Acceptance criteria :
● Design a AB test with 5 hosts dealing with more than 10 bookings per day.
User story 3:
Estimated Story Points : 5
Business Value : 3
As a host, I need some additional data from the client in order to complete the booking.
Acceptance criteria :
● When a room is confirmed by the host, send an Email to the customer with the status of the reservation and the
receipt.
● Create a form asking for additional personal data to complete the reservation.
First name, Last name, Company name, Full Address ( Street, #, Postal code, Country)
● Export the personal data into Bookings & Guest Information with a new design.
Personal data to be exported :
First name
24

26. Last name
Company name
Full Address ( Street, #, Postal code, Country)
User flow concept
To-do before user story ready to start :
Ask for a new design - Guest Information with new design.
User story 4 :
Estimated Story Points : 3
Business Value : 2
As a host, I need to print out the invoice with the address of the clients information exported from Booked application.
Acceptance criteria :
● Export the data according to the invoice design : ​Example invoice
● User can send/print out the invoice when the checkout is done.
User story 5 :
Estimated Story Points : 2
Business Value : 3
As a host, I need to send a copy of the invoice to the client by email after the check-out.
Acceptance criteria :
● Send the invoice to client from Booking : ​Example
● Email subject : Your invoice/​Booking confirmation number #invoice number#
● Email recipient : #email-contact-client#
● Email from : #email-contact-host#
Sprint (2 weeks each)
Sprint # 1 focus on ​user stories #1 and #2 as proposal for sprint #1.
Sprint # 2 focus on ​user stories #3 #4 #5 as proposal for sprint #2.
KPI’s
25