Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Open Source in a Lean Environment

Open Source in a Lean Environment

Jöran Vinzens talks about how sipgate handles open source software in lean scrum and kanban teams. What did we learn in the past and what is the goal in the future for maintenance and development?

Lean DUS

June 10, 2015

More Decks by Lean DUS

Other Decks in Programming


  1. open source? icinga, nagios, cacti, asterisk, kamailio, yate, RTP proxy,

    RTP engine, homer, captureagent, pacemaker, jenkins, ansible, DRBD, nginx, ganeti, qemu / KVM, net-snmp, quagga, puppet, tshark, postfix, squid, vim, sox, linux kernel, apache, firefox, gnome, KDE, freeradius, bind, percona, open LDAP, HA proxy, pound, lighthttpd, bacula, php, python, gcc, cups, perl, openjdk, exim, foreman, git, ecplipse, stun, libre office, imagemagick, lame, mpg123, ruby, redis, memcache, beaver, casperjs, pahntomjs, mongoDB, note.JS, openAFS, openSSH, openVPN, openSSL, samba, syslog-ng, vs-ftpd, spandsp, wireshark, bootstrap, jquery, requireJS, wildfly, elasicsearch, logstash, kibana, iTerm, atom, meteor, virtualBox, vlc, calibre, keepass, observium, as-stats, ntop-ng, osmocomBB, osmoBTS, BIRD etc...
  2. why? pros: security reason financial reason flexibility (own improvements) benefit

    from community cons: no company to blame bugs in software no one cares short release cycles
  3. software maintenance - security fixes operations team using kanban next

    story to be done delay everything else often at night (downtime)
  4. software maintenance – minor release operations team using kanban normal

    story, no delay help from development rollout no downtime
  5. software maintenance – major release temp team of developers Only

    one task to do rollout by temp team or operations team
  6. software maintenance – what can we improve? less manual work

    get faster less failure potential more automatic tests