I'll share how about we fix and revamping our product to increase conversion and gain trust to our agents. We use Design Sprint for validation and Scrum for developing the products. This team consist UX Designer, Product Manager, QA, Android Developer, Web Developer and Back-end developer. For 4 months we are validate and develop the products together.

1. Flight Team 2.0
Our Story

2. Who We Are
Julianto Saputra
Product Manager
Adani Arisy
Tech Lead & Mobile Dev
Umar Rohman
API Developer
Asep Saepulloh
API & CMS Developer
Aristo Oktobrian
Web Front End Developer
Hutomo Sugianto
Web Back End Developer
Ahmad Shokhib
QA Engineer & Analyst
Arnold Saputra
UI/UX Designer

3. Why Team Flight?
1. Improvise
2. Leadership
3. Ownership
4. Focus
5. Big tech company’s product
creation process

4. How We Do
Things
1. Brainstorming
2. Design Sprint
3. Agent Survey
4. A/B Testing
5. Product Requirement
Document
6. Backlog Grooming

5. Brainstorming
Getting ideas out from our brains

7. Google Ventures
Design Sprint

12. Agent Survey
15 KUDO Agents were called
15 Offline Travel Agents were surveyed
Questions:
Who are the customers?
FRIENDS, Colleagues, Relatives
Anything can make you sell easier?
Fixed Price, Better Price & Commission,
Booking Form
Do you have any issues?
Price Change, Email pending, Deposit on
multiple accounts
Understanding user’s wish,
identifying pain points, and
looking for insights

13. A/B Testing
Testing new prototypes against the
old product
5 Agents were A/B Tested
Key points:
Search ticket
Booking process
Agent can add moreCommission
After sales service
Error Handling

14. Vs

15. Vs

16. Vs

19. Gather all the
Data+documentation
before develop the solution...

20. Agile and iterative product development called
Donald - SCRUM

21. Pure Scrum Practice
Roles
Product Owner
Scrum Master
Development Team
Artifact
Product Backlog
Sprint Backlog
Potentially Shippable
Increment
Events
Sprint Planning
Daily Scrum
Demo
Retrospective

22. Flight Scrum-ish
Roles
Product Owner
Scrum Master
Product Manager
Development Team
Artifact
Product Backlog
Sprint Backlog*
Potentially Shippable
Increment
Events
Sprint Planning
Daily Scrum
Demo
Retrospective
* Very flexible to scope changes

23. Product Backlog
PRD as initial requirements
Backlog grooming

24. Sprint Backlog
Task -- not story
Created every Sprint Planning
Refinements of backlog
Very flexible to scope change

25. Complexity Point
Team velocity
Common understanding
Backlog Refinements
Story Point Estimation

26. Retrospective
What went well ?
What can be improved?
Next Sprint Resolution

27. Our Resolutions
Sprint 2:
On time on delivering tasks
More Speak-up
More Proactive
Sprint 3:
On time on delivering tasks: Update on-
progress task by adding comments in JIRA
daily
Sprint 4:
Implementing Checklist by adding comment

28. Accomplishments
Percentage of Requirements fulfilled from PRD
Minimal Scope Changes
Checklist showcase
Daily comment at JIRA to track progress of task

29. Clear Definition
Of DONE
No more misconception or
miscommunication of what is ‘DONE’

30. Happier Developer

31. Our youngest
member
Product by Umar Rohman

32. Special Thanks