Un percorso nel valore dei 'secondi', quelli che non vedi mai: il batterista del gruppo, il cuoco della nave, il project maneger ecc. Quelli che stanno sempre dietro le quinte. Non c’è storia che non li contempli, che senza il loro apporto evaporerebbero in un solo istante.
E che storia di secondi è quella che parte con una dotazione da 1 miliardo di dollari? E che ruolo l’AMBIZIONE? La conoscenza? Come si può affrontare e gestire un progetto, noon appunto, per attaccare Amazon, Alibaba, ebay? Come si possono pensare di coordinare 620 persone di 25 nazioni diverse che per più di due anni, hanno realizzato e vissuto la globalizzazione senza intermediari riscrivendo concetti, ormai logori, legati alla progettualità, alla leadership e all'integrazione di valori e competenze.
13. 2015 2016
Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Concept Design
• Strategy
• Business plan
• Initial roadmap
• Funding
Agile
Waterfall
16. HOW DO WE MAKE CUSTOMER CENTRICITY HAPPEN?
"NEXT"
Customer centricity
Proprietary technology
→ seamless customer experience
Large assortment
→offering wider than off-line
In-house E-payment
→ easy and secure payment
In house warehousing
→ controlled service quality
Big data intelligence
→ personalized offering/ promotion
In-house express logistics
→ 3h & high quality delivery
After Sales
→ best in class service
20. TECHNOLOGY
Developed in house Hybrid Off the shelf
Degree of control & effort
Achieved advantages
Scalability
Customization
Agility
Innovation
21. 22
When an industry faces disruption, companies often fail to
appreciate quickly enough the nature, extent, and velocity
of the changes taking place.
WHY? Disruptions start at an industry’s edge, among
small companies that provide specialized value to
emerging customer segments
They bring new business models.
They leverage new technologies.
They are highly disruptive.
27. 28
Customer centricity
99.99% uptime - 200 pps - 100 ms response - 1s ready for interaction
20 M to 100M skus in the first year
Intelligent data driven backend
Cost effective in the long term
Mobile first
Alfa1st november - Beta in January - Launch July
Goal
30. 31
..e gli ultimi 15
Nobel?
A 40 persone
(14 gruppi / 1
singolo)
LA COLLABORAZIONE EFFICACE E LA
CONDIVISIONE DI PROCESSI E
INFORMAZIONI E’ IL MOTORE
DELL’INNOVAZIONE
33. GEOGRAPHIES
Become a global player3Expand in the region21 Win local markets
e-Commerce
In-house logistic
Sourcing
Fulfillment center
Core market
Light coverage
2016 2017 2018 2019 2020 2021 2022 2023 2024 2025
KSA &
GCC
KSA
China
Morocco & other
Africa
Morocco
Indi
a
Egypt
EU
London
EU
New York
UAE
UAE
Egypt
Asian
Countries
34. Right Types of diversity + Right Amounts …
=
Good outcomes
SUCCESS: WHY?
42. Depeche Mode - Composition of sound.
Casablanca - Comes to Rick.
E prima di pubblicare il romanzo Casa desolata, una feroce critica del sistema
giudiziario britannico, Charles Dickens prese in considerazione altri undici
titoli, tra cui
La casa solitaria sempre chiusa e mai illuminata
43. noon
Is a palindrome – you can read it from left to right, and right
to left
Means the middle of the day in English
Symobilses victory in Arabic – it’s literal meaning is ‘sword’
The ‘oo’ in the middle can be interpreted as infinity
• of selection
• of choice choice for the customer
44. 2015 2016
Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Implement UAE
• Marketing
• Consumer platform
• Commercial
• Warehouse & Logistics
• E-payment
• Customer support
• Central support functions
ImplementPlan KSA
Plan UAE
• Road mapping
• Org. Structure
• Governance
Resourcing
• Hiring core team
• Budgeting
• Prepare Project Plan
Concept Design
• Strategy
• Business plan
• Initial roadmap
• Funding
GrandPa
Agile
Waterfall
54. People - Hiring process
● Cv sourcing - pipeline
● Test from coditily or project
● Paring code session or project discussion
● Senior developer interview
● Head of engineering interview
● Stpm interview
Hiring Process
55. • Visa, travel and immigration
• Introduction to Dubai
• Everything you need to know about us
• Organisation chart and directory
• Slack and Atlassian accounts
• Information about your team
Before noon
Best day of your life (aka
Day One)
At noon
• We’re so excited to see you
• Manager introduction
• IT set up
• HR Pop Quiz
• Introduction to the team
• Who we are and Leadership
Principles
• Role clarity & objectives
• Meet your key stakeholders
• Fun bus to the CFC
• Spend some time with our customers
• Deliver a parcel
Week One
59. No longer the scope as a fixed element but time and costs.
QUALITY
TIME COST SCOPE
D
SCOPE TIME COST
QUALITY
RI
Agile changes the paradigm:
pyramid is reversed, times and costs are in the foreground
Traditional Agile
The change of paradigm
64. If you have more than 3 priorities,
then you don’t have any.
-
Jim Collins
Author, Good to Great
65. Focus
Leaders focus all the time. Focus is about choosing the top priorities and about saying no
to everything else. It’s a very difficult exercise that helps you achieve a lot in a short period
of time. Being focused means you focus every single minute.
66. Great Customer Experience
Leaders focus on their customers, they win their heart and their trust. Creating a great
customer experience is about knowing what customer wants before they know it.
While looking at our competitors, Leaders learn from all industries and keep re-inventing
customer experience.
67. Anticipate
Leaders see things coming and anticipate every single possibility.
They think about all the scenarios and prepare themselfes.
68. Invent, Re-Invent and Simplify
Leaders require Innovation and re-invention from their teams. They challenge the status
quo all the time and accept to be misunderstood for a long period of time. They also find
the simplest way to do things both internally and for the customers.
69. “No one likes to get criticized. But in the dressing room, it’s necessary that you point out
your players’ mistakes. I do it right after the game. I don’t wait until Monday, I do it, and
it’s finished. I’m on to the next match.”
Alex Ferguson
Feedback
70.
71. Sappiamo che subito dopo il calcio, avvenuto a una
distanza di 27 metri dalla porta, il pallone aveva una
velocità di 129 chilometri orari; in fase di volo si è
spostato lateralmente a causa dell’accelerazione subita,
quindi ha rallentato improvvisamente fino a 67,5
chilometri orari durante la seconda metà del volo e infine
è entrato in rete all’incrocio dei pali. L’improvvisa
decelerazione si registra nel momento in cui cambia il
flusso dell’aria intorno al pallone (da turbolento a
laminare) facendo aumentare la resistenza aerodinamica
di oltre il 100 per cento.
73. Three retrospective reviews were carried out
with the product development teams to
understand:
What is working well for us?
What is not working well for us?
What actions can we take to improve our
process going forward?
This allows us to inspect and adapt, so we can
improve team velocity and culture.
Overview
74. At the end of the session, we asked the team to vote on which themes were most important. Items are mapped
against their difficulty and impact value. The bubble sizes depict how much the team values the item.
Feedback map
Less difficultMore difficult
Lower
impact
Higher
impact
Sprint planning
sessions
Unproductive late
night working
Last
minute
demos
Continue
Start
Stop
Great team humour
*Size denotes no.
of votes
Speaking English
Improved
facilities
Dev
environment
Bug process with
QA
Celebrate
success
R&D time for
developers
Timebox standup
meetings
Update JIRA
more
Unnecessary
interruptions
Locked sprints
Prioritised
stories
Long standups
+2 code reviews
78. Great Customer Experience
Focus
Invent, Re-Invent and Simplify
Hire and Develop the Right People
Ownership
Anticipate
Attention to Detail
Feedback
Think big
Disagree and be courageous
Honesty
Excellence
Tenacity
79.
80. • Proverbio Zen
Il centesimo colpo
C’è uno scalpellino che picchia sulla roccia: al centesimo
colpo la roccia si spacca in due. Il centesimo colpo è un
colpo
83. Three separate sessions were led with the development teams and product owners to understand how we can improve
as a team. There were 24 themes from the sessions with the top 5 recommendations listed below:
1. Introduce backlog refinement and sprint planning, lock the scope of sprints to focus on priorities
2. Reinforce that late night working should be productive and only when necessary
3. Regularly Demo features that are ready, instead of derailing plans when preparing for ad-hoc demos
1. Improve motivation by making milestones clearer, and celebrate success more when we hit them
2. Continue facilitating a friendly, humorous and sharing work environment
Executive summary
84. Retrospective Notes (1/5)
Item Potential actions Owner
No sprint & release planning, user story breakdown, or mapping out
dependencies with POs, tech leads and scrum masters
Hold planning sessions to prepare for sprints, and involve tech
leads in splitting out user stories to stories that are manageable in
one sprint.
Tech Leads, Scrum M
PO’s
Late night working culture: pressure to stay late at night, or celebrating late
nights, late night deployments
Individuals to take responsibility for leaving the office when
unproductive / not needed
Leadership to clarify that late night working should be the
exception, not the rule
Individual and Tech Le
Noise and interruptions to the team
Keep interruptions to a minimum. Facilities - require silent working
space, or dedicated silent working time
Whole Team
Surprise demos, and pressure to demo unfinished features / polish taking time
away from development and refocusing sprints
Reduce the demo preparation time on developers.
Only demo functionality that is ready.
Whole Team
87. In a nutshell
A product owner creates a prioritized requirements list (product backlog) presented as user stories
During sprint planning, the development team selects a number of items from the top of the product backlog and
creates a sprint backlog containing the tasks to implement the selected user stories
The scrum team has a fixed duration sprint to complete the tasks and meets each day at a daily stand up to review its
progress
At the end of the sprint, the work should be in a state where it could go live. Typically this means that code is complete,
tested, integrated and demonstrable
The sprint ends with a sprint review and sprint retrospective
As the next sprint begins, the team selects another subset of the product backlog and repeats the cycle
The cycle repeats until enough items in the product backlog have been completed to launch the product or a deadline
arrives.