<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Chris Otta on Medium]]></title>
        <description><![CDATA[Stories by Chris Otta on Medium]]></description>
        <link>https://medium.com/@otta_chris?source=rss-309918c41678------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Uqf-6cZln9mKdr-Z.jpg</url>
            <title>Stories by Chris Otta on Medium</title>
            <link>https://medium.com/@otta_chris?source=rss-309918c41678------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:10:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@otta_chris/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Mozilla’s Global Sprint 2017 Kisumu, Kenya]]></title>
            <link>https://medium.com/@otta_chris/mozillas-global-sprint-2017-kisumu-kenya-38dc488ec1a1?source=rss-309918c41678------2</link>
            <guid isPermaLink="false">https://medium.com/p/38dc488ec1a1</guid>
            <category><![CDATA[mozilla-festival]]></category>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[mozilla]]></category>
            <category><![CDATA[open-leadership]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Chris Otta]]></dc:creator>
            <pubDate>Wed, 07 Jun 2017 10:17:26 GMT</pubDate>
            <atom:updated>2017-06-07T10:35:23.284Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*vJ1K19WoUGCXNaB4YCRlow.jpeg" /></figure><p><a href="https://ti.to/Mozilla/global-sprint-kisumu-kenya">2017 Mozilla Global Sprint - Kisumu - Kenya</a></p><p>Every new day leads me to a path of self-discovery, a path more clear than yesterday’s with a greater desire to change not only the person within, but also the surrounding external environment, with the community being at the core. Community is who I am. It’s what I do on a daily basis, revolving around open technology. Thanks to Mozilla, this is becoming truer than true. What began as a Mozilla Campus Club is now growing into a large regional community of open source contributors with its base in Western Kenya. Nothing could have presented a better platform to make this more evident than Mozilla’s Global Sprint that took place on June 1 and 2.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fj-5UOXssIdXRxIVQDMBag.jpeg" /><figcaption>Sprinters shortly after the hacker’s party</figcaption></figure><p>I had the privilege of hosting the event, the first of its kind in the region and you can probably guess the level of anxiety. This was a 2-day hacking party to develop for a healthy Internet. To do so, contributions were to be made to over 40 open source projects listed as GitHub issues and which can still be found <a href="https://github.com/mozilla/global-sprint/issues">here</a>. In addition to being a host for the Sprint, I was (and still is) also an open project lead for the <a href="https://github.com/mozilla/global-sprint/issues/25">Git Push Freshman</a> project which is an open curriculum that is an introductory course to distributed version control and collaborative software development using Git and GitHub.</p><p>The Sprint brought together web developers and mobile developers who worked closely to build the <a href="https://github.com/mozilla/global-sprint/issues/70">Baraza</a> app, a mobile application for online conflict resolution. What stood out was the overwhelming presence of the Mozilla Maseno team; this is the campus club referred to in the starting paragraph of this story. They were among the most prolific contributors of the open source projects listed on GitHub. Traveling to and from campus for both days of the event was indeed exemplary of determination.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WVC3oDycQVnI7OR2-u2HJw.jpeg" /><figcaption>Part of the Mozilla Maseno team after the Sprint</figcaption></figure><p>My appreciation goes to the Mozilla team; Abigail Cabunoc Mayes, Julia Vallera, Zannah Marsh, Stephanie Wright for your insights in organizing for the event. I’d also like to thank <a href="http://lakehub.co.ke/">LakeHub</a> for offering the space to host the event, Edoardo Viola and again Abigail for the mentorship and training in the <a href="https://mozilla.github.io/open-leadership-training-series/">Open Leadership Training Series</a>, Peter Omondi Ochieng and the Mozilla Maseno team for the cooperative work in ensuring the event was a success.</p><p>Let’s keep on connecting and growing the open source community.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38dc488ec1a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lean Software Development]]></title>
            <link>https://medium.com/@otta_chris/lean-software-development-a0e563d35efa?source=rss-309918c41678------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0e563d35efa</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Chris Otta]]></dc:creator>
            <pubDate>Wed, 23 Nov 2016 10:20:59 GMT</pubDate>
            <atom:updated>2016-11-23T10:20:59.280Z</atom:updated>
            <content:encoded><![CDATA[<h3>No. 1 Principle</h3><h3>&gt; Eliminate Waste</h3><p>If something does not directly add value as perceived by the customer, it is waste. Every step in the <strong>waterfall process </strong>except analysis and coding is waste.</p><p>You must first learn to see the waste before you can perform any elimination. Common wastes in software development include:</p><ol><li><em>Partially done work: </em>Partially done software tends to become obsolete, and it gets in the way of other development that might need to be done. You never know what problems lurk until the software is integrated into the rest of the environment, and until the software is actually in production, you don’t really know if it will solve the business problem.</li><li><em>Extra Processes: </em>Many software development processes require paperwork for customer sign-off, or to provide traceability, or to provide approval for a change. The fact that paperwork is a required deliverable does not mean that it adds value. If you must produce paperwork that adds little customer value, <strong>keep it short, simple, and do it off-line.</strong></li><li><em>Extra features: </em>“I’ll put some extra features into a system just in case they are needed.”, or “I’ll add a new technical capability just to see how it works.” Sounds fancy. Right? Wrong; if code is not <em>needed now, </em>putting it into the system is waste.</li><li><em>Task switching: </em>Assigning people to new multiple projects is a source of waste. Every time software developers switch between tasks, a significant switching time is incurred as they get their thoughts and get into the flow of the new task. Belonging to multiple teams usually causes more interruptions and thus more task switching. This task switching time is waste.</li><li><em>Waiting: </em>Delays in starting a project, delays in staffing, delays due to excessive requirement documentation, delays in reviews and approval, delays in testing, and delays in deployment are waste. Waiting for things to happen is waste. Delay keeps the customer from realizing value as quickly as possible. On arrival of a critical customer need in your development organization, the speed with which you respond is directly related to the system delays in your development cycle.</li><li><em>Motion: </em>For a<strong> developer</strong> having a question, how much motion does it take to find out the answer? Are people at hand to help with a technical problem? Is the customer or customer rep readily accessible to answer a question about features? Can the developer find out the results of tests without walking down the hall? What is the length of hand-off of <strong>artifacts, </strong>e.g. for requirements to move from analysts to designers, design docs from designers to programmers, code from coders to testers, and so on? Each hand-off of an artifact is fraught with opportunities for waste. <em>A team should work in a single workroom where everyone has access to developers, testers and customers or customer reps.</em></li><li><em>Defects: </em>The amount of waste caused by a defect is the product of the defect and the time it goes undetected. Thus, a critical defect that’s detected in three minutes is not a big source of waste compared to a minor defect that goes undiscovered for weeks.</li></ol><p>Thanks for reading. Hope you’ve gained.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0e563d35efa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Thank you LAKEHUB, Kisumu]]></title>
            <link>https://medium.com/@otta_chris/thank-you-lakehub-kisumu-c644ac4681f2?source=rss-309918c41678------2</link>
            <guid isPermaLink="false">https://medium.com/p/c644ac4681f2</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Chris Otta]]></dc:creator>
            <pubDate>Thu, 17 Nov 2016 20:52:03 GMT</pubDate>
            <atom:updated>2016-11-17T20:52:03.256Z</atom:updated>
            <content:encoded><![CDATA[<p>I’d never thought of delving deep into the world of computing technology until <a href="https://medium.com/u/5e6ad4b947e2">LAKEHUB</a> thought it otherwise. It’s true that it was my sole decision to join this ever-growing community, but the story of my experience at the lakeside technology innovation hub is beyond publication in this platform.</p><p>Thanks to <a href="https://medium.com/u/5e6ad4b947e2">LAKEHUB</a>, I’ve come to harbor the conviction that I’m in the right path to not only my career and professional development, but my calling too. I can now not only speak with confidence, the technical computing language that I’d previously reserved for ‘gurus’, but also employ the writing of the same; I walk my talk. Call it ‘geek culture’.</p><p>I’m passionate, more than ever, about Computer Science and how its application in the real world, especially in Africa has, and still is making life better. Talk of code9ty and the Mozilla Movement, just to mention a few.</p><p>Big up to <a href="https://medium.com/u/c93118b21336">sigu</a> for the code9ty program, to Chandi Tome for the more than wide heart and to James Odede for the exemplary leadership. Not to forget my fellow intern JayB Otieno and the entire LakeHub community. You all are a great inspiration.</p><p>God bless <a href="https://medium.com/u/5e6ad4b947e2">LAKEHUB</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c644ac4681f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>