Running an Agile Project with Odoo

Running
an agile project within Odoo.
Backlog Management in Odoo (with brain-tec
backlog Module)
Best Odoo Partner EMEA
Odoo Gold Partner Schweiz, Deutschland & Spanien
Odoo experience 2019 | J.A. Daniel Göppner

● Graduated in business informatics
● Project Manager at braintec Group
● Distributed teams
● Agile advocate
● Daily odoo user
Who am I
J A. Daniel Göppner

Agenda
What will we see in this talk
● Benefits of Running Odoo Project in Agile method
● compare two agile methods
● Introducing of brain-tec backlog Module
● Questions and Answers

Benefits
Of Running Odoo Project in Agile method

What is Agile
In a Sentence
Agile software methodologies value:
● Individuals and interactions over processes and tools
● Working software over comprehensive documentation
● Customer collaboration over contract negociation
● Responding to change over following a plan
“ That is, while there is a value in the items on the right,
we value the items on the left more ”
The Agile manifesto, http://agilemanifesto.org

Benefits
Q: Why Agile methodics A: Risk Mitigation
Requirement
Design
Implementation
maintenance
V
S
Verification
Waterfall Projects Agile Projects

Benefits
Better product quality:
Agile methods have excellent safeguards to make sure that quality is as high as possible by
● Taking a proactive approach to quality to prevent product problems
● Embracing technological excellence, good design, and sustainable development
● Defining and elaborating on requirements just in time so that knowledge of product features is
as relevant as possible
● Incorporating continuous integration and daily testing into the development process, allowing
the development team to address issues while they’re fresh

Benefits
Higher customer satisfaction:
Agile project teams satisfy customers by
● Keeping customers involved and engaged throughout projects.
● Having a product owner who is an expert on product requirements and customer needs.
● Keeping the product backlog updated and prioritized in order to respond quickly to change.
● Demonstrating working functionality to customers in every sprint review.
● Delivering products to market quicker and more often with every release.

Benefits
Higher team morale:
Being part of a self-managing team allows people to be creative, innovative, and acknowledged for
their expertise. Having a scrum master removes impediments and shields the development team from
external interference. Working cross-functionally allows development team members to learn new
skills and to grow by teaching others.

Benefits
Increased collaboration and ownership:
The development team, the product owner, and the scrum master work closely together on a daily
basis. Daily scrum meetings let the development team organize around work completed, future work,
and roadblocks. During sprint reviews the development team can demonstrate and discuss the
product directly with stakeholders.

Benefits
Customized team structures:
Self-management puts decisions that would normally be made by a manager or the organization into
scrum team members’ hands. Because of the limited size of development teams — five to nine
people — agile projects can have multiple scrum teams on one project. Self-management and size-
limiting mean that agile projects can provide unique opportunities to customize team structures and
work environments.

Benefits
More relevant metrics:
The metrics agile project teams use to estimate time and cost, measure project performance, and
make project decisions are often more relevant and more accurate than metrics on traditional
projects. On agile projects, you provide metrics by
● Determining project timelines and budgets based on each development team’s actual
performance and capabilities
● Using relative estimates
● Refining estimated effort, time, and cost on a
regular basis
● Updating the sprint burndown chart every day
to provide accurate metrics

Benefits
Improved performance visibility:
On agile projects, every member of the project team has the opportunity to know how the project is
going at any given time. Daily scrum meetings, sprint reviews, and visible progress charts offer
concrete ways to see progress.

Benefits
Increased project control:
The many opportunities to inspect and adapt throughout agile projects allow all members of the
project team — the development team, product owner, scrum master, and stakeholders — to
exercise control and ultimately create better products.

Benefits
Improved project predictability:
Agile project management incorporates several practices, artifacts, and tools for improved
predictability:
● Keeping sprint lengths and development team allocation the same throughout the project
allows the project team to know the exact cost for each sprint.
● Using individual development team speed allows the project team to predict timelines and
budgets for releases, the remaining product backlog, or any group of requirements.
● Using the information from daily scrum meetings, sprint burndown charts, and task boards
allows the project team to predict performance for individual sprints.

Benefits
Reduced risk:
Agile techniques virtually eliminate the chance of absolute project failure:
● Developing in sprints, ensuring a short time between initial project investment and either failing
fast or knowing that a product or an approach will work
● Always having a working product
● Developing requirements to the definition of done in each sprint
● Providing constant feedback on products and processes through daily scrum meetings and
constant development team communication, sprint reviews and retrospectives, and releases in
which the end user can see and react to new features on a regular basis

Tale of two Agile Teams
More correctly it’s one Agile Teams that splits into two
agile Teams
scrum KANBAN

What’s the difference
Between Kanban and Scrum
You guys are talking about
work
We do work
Ouch!

Scrum Team
M T W T F S S M T W T F S S
Sprint
To do DEV TEST Release
Retrospective

Scrum Team
M T W T F S S M T W T F S S
To do DEV TEST TEST
BACK
LOG
DONE
PILE
AGILE
BOARD
Sprint
Retrospective
SprintPlanning
Daily scrum meeting
release

Scrum Kanban
To do DEV TEST Release

Scrum Team
To do DEV TEST TEST
BACK
LOG
DONE
PILE
AGILE
BOARD
release
Daily Stand-up

What’s the difference
Between Kanban and Scrum
scrum
V
S
KANBAN
Sprintplanning
Sprints
Retrospective
Release 1x after Sprint
(not sure)
Continious
(not sure)
Release 2.5x in the same
perios

Performing Well?

So what’s gone wrong?

What goes wrong
For the Team Kanban
1. 1. Effective translation from Backlog to DEV
1. 2. Hard limit in W.I.P
1. Natural consequence

Introducing
Of brain-tec backlog Module
Live Demo

Q&A
Questions and Answers

Zürich
Technoparkstrasse 1
CH-8005 Zürich
Brig
Saflischstrasse 4
CH-3900 Brig
Basel
Eisengasse 9
CH-4051 Basel
Zürich
Technoparkstrasse 1
CH-8005 Zürich
Böblingen
Otto-Lilienthal-Strasse 36
DE-71034 Böblingen
Madrid
Calle Velazquez 138
ES-28006 Madrid
Castelló
UA1014SD Espaitec 1
ES-12071 Castelló
Thank you,
Vergelt‘s Gott, Merci, Grazie &
Muchas gracias

Running an Agile Project with Odoo

More Related Content

What's hot (20)

Similar to Running an Agile Project with Odoo (20)

More from Odoo (20)

Recently uploaded (20)

Running an Agile Project with Odoo