On-boarding

Get Started. It's Free
or sign up with your email address
Rocket clouds
On-boarding by Mind Map: On-boarding

1. Overview

1.1. This is High Jump

1.1.1. Who: Of VISA

1.1.2. Where: Olympics Tokyo 2020

1.1.3. Why: To showcase Visa abilities of

1.1.3.1. Digital banking

1.1.3.1.1. Digital card issueing

1.1.3.2. Customer Engagement

1.1.3.2.1. User can play game to earn coin/medal

1.1.3.3. Historical Transaction

1.1.4. What:

1.1.4.1. Mobile app

1.1.4.1.1. User to add the card, verify card

1.1.4.1.2. As an athlete, user makes transaction to play game, then earn medal

1.1.4.1.3. View the leader board of the "Visa Olympics"

1.1.4.1.4. View the historical transactions of the linked card

1.1.4.2. Back end

1.1.4.2.1. Manage user

1.1.4.2.2. Manage card

1.1.4.2.3. Leaderboard

1.1.4.2.4. Activity

1.1.4.2.5. Integrate with Visa back end

1.1.4.3. Webpage

1.1.4.3.1. Leaderboard for country

1.1.5. When:

1.1.5.1. Alpha: 25-Oct-2019

1.1.5.1.1. iOS

1.1.5.1.2. Backend

1.1.5.2. Beta:15-Jan-2020

1.1.5.2.1. iOS

1.1.5.2.2. Android

1.1.5.2.3. Backend

2. Checklist

2.1. mobile

2.2. BE

2.3. QC

2.4. PO

3. Process

3.1. DoR

3.1.1. User Stories are clear

3.1.2. Client approved

3.1.3. AC (Acceptance Criteria)

3.1.4. UI/UX

3.1.5. Estimated

3.2. DoD

3.2.1. Unit test (coverage >= 80%)

3.2.2. Code Review

3.2.3. Self Testing

3.2.4. Buildable

3.2.5. QC tested

3.2.6. Bugs?

3.2.6.1. Depend on what is the kind of bug

3.3. Sprint Planning

3.3.1. Monday morning every 2 weeks

3.3.2. 10:00 AM - MR2.1

3.3.3. Team make a commitment base on

3.3.3.1. Velocity

3.3.3.2. Capacity

3.4. Sprint Retrospective

3.4.1. What went well?

3.4.2. What didn't went well?

3.4.3. How to improve?

3.5. Sprint Demo

3.5.1. Every first Tuesday of the Sprint, demo for the last Sprint

3.5.2. prepare the data

3.5.3. Transparency => build TRUST

3.6. Daily meeting

3.6.1. 10:00 AM - MR2.1

3.6.2. What did you do yesterday?

3.6.3. What are you going to do?

3.6.4. Any Blocker?

3.7. Fine rule

3.7.1. Late for meeting

3.7.1.1. 1-10 mins: 10k

3.7.1.2. more than 10 mins: TBD

3.8. Jira

3.9. Confluence

4. Grooming

4.1. Story Point includes

4.1.1. Include

4.1.1.1. Effort Time

4.1.1.2. Risk

4.1.1.3. Complexity

4.1.2. Base on Fibonacci

4.1.2.1. Easy (1, 2)

4.1.2.2. Medium (3, 5)

4.1.2.3. Hard (8, 13...)

4.1.3. Break the ticket to smaller if it has a large Story Point (Hard)

4.2. Estimation's effort must include (DoD)

4.2.1. Devlopment

4.2.2. Unit Testing

4.2.3. Code Review

4.2.4. Document

4.3. 3 Amigos: The least group of grooming session

4.3.1. PO (1)

4.3.2. QC (1)

4.3.3. DEV (2)