Kudo Team flight 2.0 process

Post on 12-Apr-2017

136 views 0 download

transcript

Flight Team 2.0Our Story

Who We Are

Julianto SaputraProduct Manager

Adani ArisyTech Lead & Mobile

Dev

Umar RohmanAPI Developer

Asep SaepullohAPI & CMS Developer

Aristo OktobrianWeb Front End

Developer

Hutomo SugiantoWeb Back End

Developer

Ahmad ShokhibQA Engineer &

Analyst

Arnold SaputraUI/UX Designer

Why Team Flight?1. Improvise2. Leadership3. Ownership4. Focus5. Big tech company’s product

creation process

How We Do Things

1. Brainstorming

2. Design Sprint

3. Agent Survey

4. A/B Testing

5. Product Requirement Document

6. Backlog Grooming

Adani Arisy
war room

BrainstormingGetting ideas out from our brains

Google Ventures

Design Sprint

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

A/B TestingTesting 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

Vs

Vs

Vs

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

Agile and iterative product development called

Donald - SCRUM

Pure Scrum PracticeRoles

Product Owner

Scrum Master

Development Team

Artifact

Product Backlog

Sprint Backlog

Potentially Shippable Increment

Events

Sprint Planning

Daily Scrum

Demo

Retrospective

Flight Scrum-ishRoles

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

Product Backlog PRD as initial requirements

Backlog grooming

Sprint BacklogTask -- not story

Created every Sprint Planning

Refinements of backlog

Very flexible to scope change

Complexity PointTeam velocityCommon understandingBacklog Refinements

Story Point Estimation

Retrospective

What went well ?What can be

improved?Next Sprint Resolution

Our ResolutionsSprint 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

“Sudah sesuai dengan Checklist / DoD”

Sprint 5: Implementing Checklist by adding

comment “Sudah sesuai dengan Checklist / DoD”

AccomplishmentsPercentage of Requirements fulfilled from PRD

Minimal Scope Changes

Checklist showcase

Daily comment at JIRA to track progress of task

Clear Definition Of DONE

No more misconception or miscommunication of what is

‘DONE’

Happier Developer

Our youngest member

Product by Umar Rohman

Special Thanks