3. Intro
As a technology design company in the modern world, your work is only as good as the foundations your company is built on.
Our philosophy at Leo Tech is simple: To encourage a team’s creativity, to push to produce the most relevant products, to
understand what a client needs to modernize their process, to inspire innovation. We structure ourselves on the following pillars:
GOOD PEOPLE GOOD ENVIRONMENT LEAN METHODOLOGY IN DEPTH KNOWLEDGE
5. Getting the right type of person
The right people make or break your process, your
products and ultimately, your business
• We take the time to get to know and understand each person on our team, see
where their strengths are
• We ensure they are doing what they are good at and we encourage them to
commit to their own personal development at work.
7. Building the right environment
• Leadership is not about being in charge, but
about taking care of those in your charge.
• Traditional View: most leaders think everybody
works for them – no – you work for the people in
your organisation – make them feel valued and
valuable
• Opportunity to fail without fear of reproach
and try again.
• Software development is a creative
process - motivation is key.
• The most important thing in the project is not
only to develop software but also to cultivate
engineers.
In the right environment, everyone works their best, because they feel at their best.
9. • Waterfall insists on a strict, sequential chain of the
different project phases.
• A previous phase has to be completed before
starting the next phase.
• All requirements must be fine grained and as
complete as possible at the start. Studies have
shown that in larger and complex projects, about
60% of the initial requirements are changed
throughout the project.
• Over 80% of investigated failed software projects,
the usage of the Waterfall methodology was one of
the key factors of failure – the larger and more
complex the project, the more risky it is to use
Waterfall.
What is Waterfall?
TIME / COST
10. HealthCare.gov - Epic Waterfall Fail
"I spent $174 million on a website and all I got was this bad press.“
12. The birth of Agile methods
The world of Agile involves self-organizing teams that work in an iterative
fashion and deliver continuous additional value directly to customers.
The practices of Agile include Scrum, XP, Kanban, DevOps and Continuous
Development, grew out of lean manufacturing in Japan in the late 20th Century.
13. Transition to Agile methods
• Instead of those doing the work reporting as individuals to
bosses, the work is done in self-organizing teams: the role
of management is not to check whether those doing the work
have done what they were meant to do, but rather to enable
those doing the work to contribute all that they can and
remove any impediment that might be getting in the way.
• Instead of a preoccupation with efficiency and predictability,
the predominant values are transparency and continuous
improvement.
• Instead of work being coordinated by bureaucracy with rules,
plans and reports, work is coordinated by Agile methods with
iterative work cycles and direct feedback from
customers.
• Instead of one-way top-down commands, communications
tend to be in horizontal conversations.
14. Lean Startup Methodology
Every one of these disruptive start-ups above started with a good concept that was
validated in its simplest form and then pushed into the mega product you know today.
Validated Learning methods help build sustainable businesses - entrepreneurs should run experiments and validate what
customers need. In this way, they reveal current and future business prospects.
“A human institution designed to create a new product or service
under conditions of extreme uncertainty…”
- Eric Ries, on start-ups
15. Minimum Viable Product
MVP - Proving the product works…
• Build-measure-learn – this is the fundamental activity of a
startup.
• MVP is used as a tool to collect customer feedback on the
product.
• Feedback is analysed to improve the product and to
validate the concept
• From this, the team can decide rapidly to pivot, persevere
and scale or dismiss the project altogether.
17. Product Discovery
“Through a series of workshops, Leo Tech ensures that
both the delivery team and client start down the right path
with Lean planning strategies for requirements gathering
and hands-on Agile coaching."
19. Persona Mapping
Analysing the personas of our target users and referring
back to them throughout the process to keep the product user-
led and relevant.
This focuses our intentions on providing the right product
for the particular client or user within a business.
20. Story-boarding
Storyboarding is used to define the core user journeys
that are required for the business model.
Leo Tech attempts to visualise the entire user journey;
before, during and after. In this way, the product
specifications are clarified.
Screens that the software will display are sketched to
illustrate the important steps of the user experience.
21. Story Map
The Story map indicates the relative
priority of product functionality and
features that have been identified by
the story board.