Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Embracing FLOSS
as a shortcut towards
agility
OpenSouthCode 2019
25 de Mayo de 2019
Málaga, ES
Agustín Benito Bethencourt
...
About the speaker
The speaker: @toscalix
● Consultancy/management about software production and maintenance of
complex Linux based systems/p...
1. Disclaimers.
2. Hypothesis.
3. FLOSS as shortcut to adopt:
a. Agile Values.
b. Agile Principles.
c. Agile Methodologies...
Let’s start!
1.- Disclaimers
Agility = “agile at scale”
instead of the:
● ...brand.
● ...methods.
● … Agile Manifesto definition.
Disclaimer 1
Journey vs destination: “towards agility”
Disclaimer 2
FLOSS instead of Open Source.
Disclaimer 3
2.- Hypothesis
● Most popular Agile methods were designed as
(end-to-end) team-level methods.
● They scale well horizontally across teams...
Synchronization across teams becomes harder as the
number of teams increases in environments like:
● Heterogeneous environ...
● Agile methodologies promote optimizations locally.
● Local optimizations does not roll up easily at scale.
Hypothesis 2
Organizations cannot move towards agility by simply
scaling up team-level methods (agile methodologies).
Hypothesis 2
3.a.- FLOSS as a shortcut to
adopt…
Agile Values
● Individuals and Interactions over processes and tools.
Team?
● Working Software over comprehensive documentation.
Trust?...
Agile vs (subjectives) Open Source key
values
● Community.
● Transparency.
● Co-creation.
● Freedom.
● Team.
● Trust.
● Co...
3.b.- FLOSS as a shortcut to
adopt…
Agile Principles
“5.- Build projects around motivated individuals. Give
them the environment and support they need, and trust
them to get t...
3.c.- FLOSS as a shortcut to
adopt…
Agile Methodologies
Co-located vs remote vs distributed teams.
● Agile: colocation vs. FLOSS: distributed.
● But growing number of doing agile...
3.d.- FLOSS as a shortcut to
develop...
key skills/competences
From project to product mindset:
● Code ownership.
● Maintainable code.
Competences, skills
4.- Takeaways
FLOSS projects are low risk - high return learning
ecosystem.
Takeaway 1
The journey to “become agile” is shorter for FLOSS
professionals than for most.
Takeaway 2
The journey towards agility for those organizations
involved in Open Source is shorter… and easier.
Takeaway 3
Dear agilist,
if you enjoy and learn collaborating openly with your
colleagues, imagine what is like to collaborate global...
Thank you
Agustín Benito Bethencourt
@toscalix
Q&A
You’ve finished this document.
Download and read it offline.
Upcoming SlideShare
What to Upload to SlideShare
Next
Upcoming SlideShare
What to Upload to SlideShare
Next
Download to read offline and view in fullscreen.

0

Share

Embracing floss as_a_shortcut_towards_agility

Download to read offline

Personal stories about how those organizations and professionals who has been involved in FLOSS projects, specially big ones, embrace certain values, follow principles, master practices and acquire some competences that are extremely valuable in transformation processes towards agility at scale.

Related Books

Free with a 30 day trial from Scribd

See all
  • Be the first to like this

Embracing floss as_a_shortcut_towards_agility

  1. 1. Embracing FLOSS as a shortcut towards agility OpenSouthCode 2019 25 de Mayo de 2019 Málaga, ES Agustín Benito Bethencourt toscalix@gmail.com CC-BY-SA 4.0
  2. 2. About the speaker
  3. 3. The speaker: @toscalix ● Consultancy/management about software production and maintenance of complex Linux based systems/platforms/distros/products. ● Experienced manager in open and in distributed environments. ● Contributor in several FOSS communities (KDE, openSUSE…). ● Worked at known FLOSS orgs. like Codethink, Linaro, SUSE, ASOLIF... ● More about Agustín at his site.
  4. 4. 1. Disclaimers. 2. Hypothesis. 3. FLOSS as shortcut to adopt: a. Agile Values. b. Agile Principles. c. Agile Methodologies. d. Key skills/competences. 4. Takeaways. Talking Points
  5. 5. Let’s start!
  6. 6. 1.- Disclaimers
  7. 7. Agility = “agile at scale” instead of the: ● ...brand. ● ...methods. ● … Agile Manifesto definition. Disclaimer 1
  8. 8. Journey vs destination: “towards agility” Disclaimer 2
  9. 9. FLOSS instead of Open Source. Disclaimer 3
  10. 10. 2.- Hypothesis
  11. 11. ● Most popular Agile methods were designed as (end-to-end) team-level methods. ● They scale well horizontally across teams in fairly homogeneous/colocated environments. Hypothesis 1
  12. 12. Synchronization across teams becomes harder as the number of teams increases in environments like: ● Heterogeneous environments. ● Remote/distributed setups. ● Portfolio with strong-hard dependencies. Hypothesis 1
  13. 13. ● Agile methodologies promote optimizations locally. ● Local optimizations does not roll up easily at scale. Hypothesis 2
  14. 14. Organizations cannot move towards agility by simply scaling up team-level methods (agile methodologies). Hypothesis 2
  15. 15. 3.a.- FLOSS as a shortcut to adopt… Agile Values
  16. 16. ● Individuals and Interactions over processes and tools. Team? ● Working Software over comprehensive documentation. Trust? ● Customer Collaboration over contract negotiation. ● Responding to Change over following a plan. Flexibility. Agile values
  17. 17. Agile vs (subjectives) Open Source key values ● Community. ● Transparency. ● Co-creation. ● Freedom. ● Team. ● Trust. ● Collaboration. ● Flexibility.
  18. 18. 3.b.- FLOSS as a shortcut to adopt… Agile Principles
  19. 19. “5.- Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.” 12 Principles behind the Agile Manifesto Agile vs Open Source Principles
  20. 20. 3.c.- FLOSS as a shortcut to adopt… Agile Methodologies
  21. 21. Co-located vs remote vs distributed teams. ● Agile: colocation vs. FLOSS: distributed. ● But growing number of doing agile/DevOps/CD. ● Agile intolerant to asynchronicity and high latency. Agile Methodologies vs FLOSS best practices
  22. 22. 3.d.- FLOSS as a shortcut to develop... key skills/competences
  23. 23. From project to product mindset: ● Code ownership. ● Maintainable code. Competences, skills
  24. 24. 4.- Takeaways
  25. 25. FLOSS projects are low risk - high return learning ecosystem. Takeaway 1
  26. 26. The journey to “become agile” is shorter for FLOSS professionals than for most. Takeaway 2
  27. 27. The journey towards agility for those organizations involved in Open Source is shorter… and easier. Takeaway 3
  28. 28. Dear agilist, if you enjoy and learn collaborating openly with your colleagues, imagine what is like to collaborate globally (FLOSS). Final note
  29. 29. Thank you Agustín Benito Bethencourt @toscalix
  30. 30. Q&A

Personal stories about how those organizations and professionals who has been involved in FLOSS projects, specially big ones, embrace certain values, follow principles, master practices and acquire some competences that are extremely valuable in transformation processes towards agility at scale.

Views

Total views

306

On Slideshare

0

From embeds

0

Number of embeds

7

Actions

Downloads

0

Shares

0

Comments

0

Likes

0

×