---
# System prepended metadata

title: Estimation
tags: [' Estimation', Oneup]

---

---
tags: Oneup, Estimation
---


# Estimation

## What are we estimating ?

- Complexity
- Effort
- Risk or/and Unknowns
- Dependencies

## How can we estimate (Fibonacci) ?

- Having the same way estimating
- Objective measure instead of Subjective measure (use of story points) `can be tried on dev level in a first time and pushed generally later, by taking leverage on the subtasks level`
- Doing relative estimation "if possible" (base on 2 reference tasks, 1 and 13, the team agree on the weight by project/team)

:::info
:bulb: **Hint:** Estimate must include everyting that can affect the effort
:::


## What to care about ?

- Multiple estimates from different people (in order to average errors) 
- Definition of done ?
- Definition  of sprints ? (to have velocity and choose a more representative reference task)




# Roadmap

| Phase                   | Timeframe        | Key Tasks                                      |
|-------------------------|------------------|-----------------------------------------------|
| V1 - Oct23 - Pull       | October 2023      | Las Vegas meeting Demo MA, Visa, C1, Microsoft |
| V2 - Dec23 - Push       | December 2023     | BNPP, SG, C1                                  |
| V3 - Feb24 - Push + Pull| February 2024     | Global Go To Market                           |
| UX                      |                  | - Integration of Karl in OneUp V1           |
|                         |                  | - Specification of V1 interface design       |
|                         |                  | - Implementation of V1 specification         |
|                         |                  | - Implementation of V2 specification         |
|                         |                  | - Implementation of mobile and desktop notifications (for push) |
| PULL                    |                  | - Memorization flow step                     |
|                         |                  | - Acceptance testing                         |
|                         |                  | - Definition of prompts for users and administrators |
|                         |                  | - Improvement of exact matching in search engines (Milvus / ElasticSearch) |
|                         |                  | - Implementation of Data Insight and Business Consultancy APIs (Karl) |
| PUSH                    |                  | - Building the list of questions and answers |
|                         |                  | - Development of prompts for each category of advice |
|                         |                  | - Implementation of GQL endpoints for tips    |
|                         |                  | - Implementation of the Smart Advices API (Oneup) |
|                         |                  | - Setting up a rejection system (to be determined if separate) |
|                         |                  | - Implementation of the notification worker |
|                         |                  | - Implementation of the Tips API on the assistant |
| ML USER TRACKING        |                  | - Unlock tracking for BNPP, OneUp (similar to what we do for Lloyds) |
|                         |                  | - Data information, database exploration     |
|                         |                  | - Data extraction                            |
| Questions and Discussions |              | - Open to questions and comments             |
|                         |                  | - Discussion on priorities, concerns, and suggestions |
| Next Steps              |                  | - Reminder of next steps                    |
|                         |                  | - List immediate next steps                  |
|                         |                  | - Responsibilities and deadlines            |

---