<?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[Be the Revolution - Medium]]></title>
        <description><![CDATA[How every business is now a software business - Medium]]></description>
        <link>https://medium.com/be-the-revolution?source=rss----4cba98d132d8---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Be the Revolution - Medium</title>
            <link>https://medium.com/be-the-revolution?source=rss----4cba98d132d8---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 16:33:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/be-the-revolution" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The 15 Minutes Rule To IT Success]]></title>
            <link>https://medium.com/be-the-revolution/the-15-minutes-rule-to-it-success-7f18a0392783?source=rss----4cba98d132d8---4</link>
            <guid isPermaLink="false">https://medium.com/p/7f18a0392783</guid>
            <category><![CDATA[fiction]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[INGENO]]></dc:creator>
            <pubDate>Wed, 10 Oct 2018 13:54:02 GMT</pubDate>
            <atom:updated>2018-10-10T13:58:16.646Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mNCiLJHUx_pTq6nJFKHTog.jpeg" /></figure><p>Are you puzzled by the ability of small tech startups like <a href="https://www.frankandoak.com/">Frank and Oak</a> to out-innovate their competition? What’s their secret?</p><p><strong>These new leaders play by the 15 minutes rule!</strong></p><blockquote>If you are waiting more than 15 minutes for anything, someone broke your ability to turn cash into code, to productize this code into features, and to convert those features into value.</blockquote><p>These newcomers are much quicker at improving their digital platforms, delivering new features almost daily. Many well-known brands, which have been in business for longer, are way more prominent and have more money, all seem stalled in a previous era.</p><p>We can confirm, from the technical audits we perform for our customers, that inertia is usually the primary cause of late or over budget projects. You can <strong>quickly get bogged down</strong> by accepted practices, which often introduce lead times in your delivery process. Some of the most common causes of delays are:</p><ul><li>Stampings from the architecture committee</li><li>Controlled access to restricted documents, VPNs, production servers</li><li>Provisioning of hardware and accounts by a dedicated team</li><li>The centralized release of core libraries by the framework team</li><li>Jim, the hero, who’s the only one on your squad who knows how to configure or build or deploy that critical microservice</li><li>Gatekeepers such as PR reviewers</li><li>Procurement authorization for licenses and tools</li><li>Corporate credit card numbers are necessary to create a new account somewhere</li></ul><p>Lost velocity is terrible but <strong>delayed time to market is worst</strong>. It can kill your product if the competition gets there first. Your startup could also merely die from lack of cash flow.</p><p>A customer of ours, who had tenures as director, VP, and CTO of many high tech companies, including Amazon, once told us that his main focus has always been to <strong>reduce friction</strong>. Delays are often introduced by middlemen with little-added value today, once they get replaced by automated processes such as continuous integration, configuration as code, automated testing or autonomous DevOps teams.</p><p>Be on the lookout for anyone saying that they have been waiting for something or someone for more than fifteen minutes. These are <strong>opportunities for change</strong>. More often than not, this will require a cultural shift, even if processes or technologies are involved.</p><p>I’ll stop here. Someone has been waiting for me to finish this blog post for the past 15 minutes!</p><p>Be the Revolution!</p><p>by Remy Gendron, founder at INGENO</p><p>Learn more about us at <a href="http://ingeno.ca/">ingeno.ca</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f18a0392783" width="1" height="1" alt=""><hr><p><a href="https://medium.com/be-the-revolution/the-15-minutes-rule-to-it-success-7f18a0392783">The 15 Minutes Rule To IT Success</a> was originally published in <a href="https://medium.com/be-the-revolution">Be the Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agility and TCO]]></title>
            <link>https://medium.com/be-the-revolution/agility-and-tco-b4e412999cb8?source=rss----4cba98d132d8---4</link>
            <guid isPermaLink="false">https://medium.com/p/b4e412999cb8</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[tco]]></category>
            <dc:creator><![CDATA[INGENO]]></dc:creator>
            <pubDate>Thu, 27 Sep 2018 14:34:50 GMT</pubDate>
            <atom:updated>2018-09-28T14:05:12.408Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SuEg1n8aZ4tUcmPmJlfcZg.jpeg" /><figcaption>We all agree that agile software development practices are a good thing. I presented here <a href="https://www.ingeno.ca/blog/2018/6/22/the-five-ingredients-for-true-agility-in-software-development">The Five Ingredients for True Agility in Software Development</a>, so now here is my top things to avoid when you want to implement agility in your organization.</figcaption></figure><p>As I said, agility has a positive impact on companies, but there is danger lurking. We have to be careful not to use the agile springboard and jump head first into code construction. This applies to all projects, big and small.</p><blockquote>The experienced carpenter considers the task three times, measures twice and cuts only once!</blockquote><p>Agility is no pretext to completely forgo requirements gathering, planning and designing. The thinking phase needs to precede each iteration. Your urge to code could prevent you from exploring often overlooked but very powerful options at the initial stages…</p><h3>LET’S BUILD A DOG HOUSE</h3><p>Jack, your new dog, needs a house. So your partner asks you to build one and goes out for the day. Building a dog house is not that complicated: leftover materials, a few tools, and the job can be done quick and easy. The result; however, is not what was expected, as you find out when your partner checks out your day’s work.</p><p>You could choose to adopt an agile approach and consult with your partner every step of the way. When the day is done, the new dog house will be completed and everybody will be happy, including Jack.</p><p>The general belief is that waterfall projects are doomed to fail, while agile projects have a much greater chance of being successful.</p><blockquote>OUR NEW FOCUS ON AGILE PROCESSES CAN PROMOTE THE NOTION THAT OUR ABILITY TO DELIVER IS THE END GOAL.</blockquote><p>That’s where we may be misleading ourselves.</p><blockquote>IN SOFTWARE DEVELOPMENT, BENCHMARKS FOR SUCCESS SHOULD NOT BE BASED ON UNDER-BUDGET AND ON-TIME DELIVERY. THE REAL MEASURE OF SUCCESS IS A POSITIVE RETURN ON INVESTMENT.</blockquote><h3>THE POWER OF SIMPLICITY AND COMPROMISE</h3><p>Happy carpenters would probably be surprised to know the TCO (total cost of ownership) of the new dog house. From the cost of building materials to the tools, without forgetting the labor of ALL the people involved. Considering a $50 hourly rate, your dog house may very well cost you $750. At $50/hour, the dog house may very well end up costing $750!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c3eF_LcPoOLD-lZaCRJVhQ.png" /></figure><p>That’s a sizeable amount. What’s the return on investment here? That’s the real question we need to ask.</p><p>Whether it’s for a dog house, a new application feature or a complex development project, I always start by asking:</p><ul><li>What if we just didn’t do it? Can our users live without it?</li><li>If not, can we repurpose existing artefacts or buy some off-the-shelf components and achieve a baseline of capabilities?</li></ul><p>How did we come up with the need for a dog house in the first place? The dog certainly didn’t ask for it. The house will certainly get some use once in a while. But Jack is never left outside at night. There is not an absolute need for it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZkctaALA3bwgFPfL9QvpOA.png" /></figure><p>But what if you have a bigger dog that effectively spends a lot of time outside? Well, I’ve seen incredibly good looking dog houses on Walmart’s Web site for $150. Factor in the time to go and pick it up, and you’re looking at $200 vs our original $750.</p><p><strong>Seems obvious ? Those decisions are still not the norms where some businesses stubbornly choose to develop everything in-house. They develop their own CRM, CMS, online store instead of paying a small monthly with a SaaS 100 times more powerful than what they will ever achieve.</strong></p><h3>TAKE IT A STEP FURTHER</h3><p>The biggest gain here is not that you saved some money. Rather, you could be doing something else of value with the time saved.</p><p>If there is effectively a need for a dog house and building the dog house is not really perceived as a great way to spend your time, what could you do instead? If you’re an entrepreneur, you could work on something your customers are waiting for and willing to pay. By buying the dog house you’re left with 7 available hours that you can use to build value and bill your clients for it. At the end of the day, you’ll have the dog house and $150 more in your bank account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4-j42Nhr4mtGCA4zGXs7uA.png" /></figure><p><strong>Let’s go back to our online store example. Instead of wasting months on building your own solution, why not be up and running as soon as possible with an existing solution so you can put all your efforts in selling your product? Isn’t that where you really create value?</strong></p><p><strong>Is any solution going to fit 100% of your needs? Probably not. But, it will satisfy 98% of them while being 10X cheaper and 100X quicker to set up.</strong></p><p>Being agile should not distract us from the need to constantly ask about business needs and question the ROI. Moreover, we have a strong tendency to overdesign when most users of our solution would be content with a baseline of functionalities.</p><p>Agility is not the ability to do more or more complex software.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qTk8Jkx8t5OOQYKqpem61g.jpeg" /></figure><p>Keep it simple and be open to compromise. You’ll be more agile than ever!</p><p><em>Originally published at </em><a href="https://www.ingeno.ca/blog/agility-and-tco"><em>www.ingeno.ca.</em></a></p><p>Be the Revolution!</p><figure><a href="http://bit.ly/2IPGHIk"><img alt="" src="https://cdn-images-1.medium.com/max/200/1*sCaxqManJbAbgpZCA1suGQ.png" /></a></figure><p>by<a href="http://bit.ly/2IPGHIk"> Remy Gendron</a>, founder at INGENO</p><p>Learn more about us at <a href="http://ingeno.ca/">ingeno.ca</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4e412999cb8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/be-the-revolution/agility-and-tco-b4e412999cb8">Agility and TCO</a> was originally published in <a href="https://medium.com/be-the-revolution">Be the Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Never Ending MVP]]></title>
            <link>https://medium.com/be-the-revolution/the-never-ending-mvp-c8e2814618e5?source=rss----4cba98d132d8---4</link>
            <guid isPermaLink="false">https://medium.com/p/c8e2814618e5</guid>
            <category><![CDATA[agile-development]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[mvp]]></category>
            <dc:creator><![CDATA[INGENO]]></dc:creator>
            <pubDate>Tue, 25 Sep 2018 20:12:57 GMT</pubDate>
            <atom:updated>2018-09-25T20:12:57.438Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VgHxr4vJGXJSfOOpq4UQQA.jpeg" /></figure><p>I’m writing this while on a road trip in my camper. It’s amazing how I can see so many places and do so many things in such a short time.</p><p>Interestingly, my ability to move fast is provided by the same concepts that can make your IT projects much quicker:</p><ul><li>Minimalism</li><li>Simplicity</li><li>Reuse</li><li>Flexibility</li><li>Evolution.</li></ul><p>I guess that’s a pretty good definition for a true MVP!</p><h4>What is a MVP (Minimum Viable Product)?</h4><p>The minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. — Eric Ries, The Lean Startup</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*OxHjbfeA6aFb_vWMpGXUZQ.jpeg" /></figure><p>Two years ago, we built mobile and kiosk survey platforms for a restaurant chain. One of our full stack developers did it over the weekend. It came entirely Cloud-based, with APIs, user geolocation, analytics and export capabilities. The infrastructure and licensing came under $50/month.</p><p>How could this be done in only two short days and such a low budget?</p><ul><li>By using a Bootstrap template without any custom modifications to create some simple HTML pages.</li><li>By using Wufoo to build a survey engine and to provide basic analytics.</li><li>By embedding the Wufoo survey into the HTML pages with some Javascript.</li><li>By buying iPads and the Kiosk Pro iOS app to provide in-store kiosk versions of the survey.</li><li>By using a simple to remember URL to access the web version, or by scanning a QR code on the menus or by texting the survey phone number.</li><li>By connecting Zapier to export each new survey entry to Dropbox as a text file, to Google Sheet as a new line item and to emails and SMS notifications sent to branch managers.</li><li>By deploying the static survey app to Site44 CDN connected to a Dropbox development folder.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q8NW3NBAZrkuRX2qFsOYTQ.png" /></figure><h4>Minimalism</h4><p>Product owners always ask for too many features. Just say no to most of them.</p><p>Think camper. Not hotel</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*K3B2vd20qW3zZvCleUEqXQ.png" /></figure><p>Deliver a super minimal product first. Don’t be afraid to rely on manual interventions, such as customer acquisition, payment or exports.</p><p>However, those initially delivered features must be impressive and game changers.</p><h4>Simplicity</h4><p>The application must be as simple as possible. Don’t do paging, column sorting or client-side validations. Keep each feature as clean and straightforward (Clean Code) as possible. Features should themselves be small MVPs.</p><p>So please, don’t architect to millions of users when you still don’t have any.</p><h4>Reuse</h4><p>Don’t code something that already exists. The only code needed for an MVP is usually the glue that binds all those external components and the small bits of necessary, domain-specific business logic.</p><p>In our case, we needed to select the restaurant location from the user’s geo-location (not provided out of the box by Wufoo) and to compute store, region and chain-wide satisfaction metrics.</p><h4>Flexibility</h4><p>You should be willing to let go of a feature if it is too costly or if it pushes your launch date too far. You should accept that the UX may not be distinctive enough to win an award. You may launch only for iOS and target Android later if the app is successful.</p><p>The goal is to acquire your first users, not to build the perfect application.</p><h4>Evolution</h4><p>Deliver to your customers as soon as you have something that is usable and brings them value. You can add the next feature tomorrow, tune performance next week and add scalability when and only when you need it.</p><ul><li>With our survey app, we added a simple backend, and we replicated the survey results in our datastore when new metrics not available natively in Wufoo were needed.</li><li>We migrated to AWS S3 when we got reliability issues with Site44.</li><li>We later added some machine learning capabilities to identify specific survey entries based on emotions expressed within the comment field.</li><li>Also, when new restaurants open or store managers change, we must do the updates manually in code and redeploy as this feature has yet to be implemented.</li></ul><p>A motorhome provides you with the minimal living requirements when traveling, but each of these is a game changer (think shower and toilet). Every amenities is kept simple. Items transform into something else (sofa into a bed) in different contexts.</p><p>There are tradeoffs for sure but, by being flexible on your comfort (camper vs. hotel), you get mobility and velocity. Flexibility allows you to start with a vague outline of your trip and evolve it as you go, adapting to changing weather, interests or personal mood.</p><p>Be like the camper geek and get velocity by adopting the true MVP mindset.</p><p><em>Originally published at </em><a href="https://ingeno.ca/blog/never-ending-mvp"><em>www.ingeno.ca</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*sCaxqManJbAbgpZCA1suGQ.png" /></figure><p>by <a href="https://goo.gl/K2UUZ5"><strong>Rémy Gendron</strong></a><strong>,</strong> founder at INGENO</p><p>Learn more about us, how we build software and how we help companies deliver business value at <a href="http://ingeno.ca/">ingeno.ca</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8e2814618e5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/be-the-revolution/the-never-ending-mvp-c8e2814618e5">The Never Ending MVP</a> was originally published in <a href="https://medium.com/be-the-revolution">Be the Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Software R&D as a Service Can Save Your Tech Startup]]></title>
            <link>https://medium.com/be-the-revolution/software-r-d-as-a-service-can-save-your-tech-startup-19d5433dc563?source=rss----4cba98d132d8---4</link>
            <guid isPermaLink="false">https://medium.com/p/19d5433dc563</guid>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[investors]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[INGENO]]></dc:creator>
            <pubDate>Thu, 14 Jun 2018 15:54:13 GMT</pubDate>
            <atom:updated>2021-01-27T18:28:58.084Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rQ7RHC4fK-2tWkO6_b6cwg.jpeg" /></figure><p>If you’re a tech startup, bootstrapping your own R&amp;D may be a bad idea. The current IT landscape makes it a risk that may doom your company. Really!</p><p>As a founder, you are surrounded by challenges and need all the help you can get. Your technical team cannot be a source of concern.</p><p>You should think about your R&amp;D the same way as most companies now think about their infrastructure. You have a choice between on-premise or ‘As a Service’ (aka Cloud) compute options. I believe these options also exist and need to be considered for your R&amp;D if you want your startup takeoff telemetry to be firmly in the green.</p><h4>Scarcity of Talent</h4><p>Talent has never been as scarce as today. The big FAGA (Facebook, Amazon, Google, Apple) type players can and will acquire all available top talent. The few remaining A players will choose well-funded startups that can pay top dollars and offer an equity plan. If you are still early with only love money to spend, these people are out of reach. You’ll be left to choose amongst below average candidates. To successfully launch a tech startup, you need senior, multi-talented, creative and high throughput developers who will make the right decisions and can attract other developers through their own networks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PBZoLsjIv8-RBL5dUg3nfg.png" /></figure><h4>Immediacy and Cohesion</h4><p>Even if you are the lucky one and have deeper pockets, finding and hiring this team of initial developers will take time. Time your investors may not care for. You are probably asked to deliver your MVP over the next 3 to 6 months. And if you have the network or attractiveness to create this core team of 3 to 7 members, cohesion will initially be low and may never emerge. In a professional sports league, the annual all-star game players would not be able to defeat the best team in the league.</p><h4>Post MVP Transition</h4><p>After the MVP phase, you will need to do things differently. You proved that your business model makes sense. Now, you need a solid solution to accelerate your growth.</p><p>You may want to divert R&amp;D budget toward marketing and sales. If you then let go of developers, you will loose your internal IP.</p><p>Moreover, the creative types you relied on to wrap together an early MVP may not be the best profiles to scale the business and optimize the operational aspects of a technical product.</p><h4>The Advantages of a Trusted Technical Partner</h4><p>Startups now universally opt for a public Cloud provider over an on-premise infrastructure. The availability, diversity, immediacy, quality and costs are unbeatable.</p><p><strong>Could you approach your R&amp;D needs the same way?</strong></p><p>Partnering with a specialized R&amp;D provider can kickstart your startup with access to an elastic pool of high-quality DevOps teams. When you factor in all the hidden costs required to build your own teams, a R&amp;D partner makes a lot of sense. You can get, for a fraction of the costs, a workforce with:</p><ul><li>A proven track record at launching a startup</li><li>An immediate availability</li><li>Team developers with an 18 months life expectancy that stay with the company when they are rotated off your project</li><li>A team that can rely on other, nearby experts instead of an isolated team of internal developers</li><li>A team that can benefit from constant exposition to other projects and technologies</li><li>The flexibility of temporarily offloading team members after the MVP phase</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/589/1*pau69lyYmlC729LnGUGMLg.png" /></figure><ul><li>Part-time profiles such as CTO, chief architect or security officer</li><li>Access to other talented developers who can provide temporary help or expertise on specific architectural, scalability or performance problems</li><li>Operational human expertise, located in a secured environment, that can easily launch and manage your MVP</li></ul><p>Established companies are now doing the same and cooperate with external partners when tackling new technologies they are not familiar with, such as mobile, Cloud or AI development projects.</p><h4>How to Mitigate the Risks</h4><p>As a manager, you must ensure that this partnership will incur less risks than having your own R&amp;D. In fact, part of what you will be paying goes toward this specific benefit.</p><p>You should therefore look for the following:</p><ul><li>Autonomous, cohesive teams… do not go with a body shop that only provides ‘people’</li><li>Technical AND business leadership, from a partner that will coach you toward a successful outcome</li><li>Internal oversight on your side to learn from your partners instead of managing them</li><li>Instant exit clauses with knowledge transfer protocols</li><li>Company history including success stories and low employee churn rates</li><li>References to past and current customers</li></ul><h4>What About Investors?</h4><p>How this will be perceived by investors will vary but is generally well-received if:</p><ul><li>They are well educated on this approach</li><li>Your partner complies with the risks management checklist above</li><li>You have a plan on when and how to migrate to your own internal developer teams</li></ul><p>I have been involved in a number of technical audits and seen a lot of companies fail at reaching the MVP stage or negotiate the post MVP transition. Lack of technical leadership, including operational acumen, is often to blame.</p><p>Investors can quickly become wary of the startup ability to execute on the business plan. The perceived lower costs of the initial, in-house development team eventually made the costs of reaching MVP status misaligned with the expected pre-money valuation of the next round.</p><p>A stable and mature R&amp;D, provided by a trusted business partner, can alleviate many insecurities from current and potential investors.</p><h4>Can You Answer YES to These Pre-Flight Checklist Items?</h4><ul><li>Will your R&amp;D department rapidly provide you with a team of 2 to 7 developers?</li><li>Will your team be composed of experts 10X more productive than the average developer?</li><li>Will the team be proficient at DevOps and<a href="https://medium.com/be-the-revolution/https-medium-com-be-the-revolution-the-five-ingredients-for-true-agility-in-software-development-ee73aa5ddb95"> true Agility</a>?</li><li>Will the team have strong expertise at SaaS, scalability, code quality, evolutionary architectures and net security?</li><li>Will the team be senior enough to make product and <strong>business decisions?</strong></li><li>Will the team be trustworthy enough to be given administrative access to all the development tools and production environments?</li><li>Will the team get you to MVP status and beyond?</li><li>Will the team be considered an asset instead of a liability when you pitch to investors?</li></ul><p>Be the Revolution!</p><figure><a href="https://goo.gl/K2UUZ5"><img alt="" src="https://cdn-images-1.medium.com/max/200/1*sCaxqManJbAbgpZCA1suGQ.png" /></a></figure><p>by <a href="https://goo.gl/K2UUZ5">Rémy Gendron</a>, founder at <a href="http://ingeno.ca/">INGENO</a></p><p>P.S. Learn more about us, how we build software and how we help companies deliver business value at <a href="http://ingeno.ca/">INGENO.ca</a></p><figure><a href="https://medium.com/be-the-revolution/https-medium-com-be-the-revolution-the-five-ingredients-for-true-agility-in-software-development-ee73aa5ddb95"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cq2g2P7rg0-gkB2u4Yw3iQ.jpeg" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19d5433dc563" width="1" height="1" alt=""><hr><p><a href="https://medium.com/be-the-revolution/software-r-d-as-a-service-can-save-your-tech-startup-19d5433dc563">Software R&amp;D as a Service Can Save Your Tech Startup</a> was originally published in <a href="https://medium.com/be-the-revolution">Be the Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Evaluate your IT culture in five questions]]></title>
            <link>https://medium.com/be-the-revolution/evaluate-your-it-culture-in-five-questions-d6d5ae792426?source=rss----4cba98d132d8---4</link>
            <guid isPermaLink="false">https://medium.com/p/d6d5ae792426</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[cto]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[INGENO]]></dc:creator>
            <pubDate>Wed, 18 Apr 2018 17:31:03 GMT</pubDate>
            <atom:updated>2018-04-19T19:26:46.387Z</atom:updated>
            <content:encoded><![CDATA[<p>or the five questions you should ask to your CTO</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N0kTeSf7bR6oznp4UWVSaw.png" /></figure><p>I was invited to address a group of CFOs on the new challenges of IT and its effect on them. At the Q&amp;A period one of the attendants came up to me and asked,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f43L7xmuKctwpO_xf_jcEA.png" /></figure><p>I don’t quite remember what I answered on the spot, but the question stayed in my head and kept nagging at me. Obviously, there would be different answers for different business cases. However, whenever writing software is key to an organization, these next questions should definitively be high up on the list.</p><h4>Is technology an enabler of innovation in your organization?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/121/1*pO4jMB8p7jcshDcjUwjUJg.png" /></figure><p>Many companies are finding out the hard way that <em>innovate or die</em> is more than a catchphrase. Just ask a traditional taxi company what they think about Uber! In today’s business landscape, you can literally wake up one morning with a new competitor you never saw coming. No business is immune to this reality. If innovation is not just about technology, it is often a key component.</p><p>The business ecosystem is changing and IT must adapt. The fundamental issue here is not to determine if IT is slowing down the business — in which case red flags should already be clearly visible to your top executives. The less obvious question is to ask how IT contributes to supporting or even fuelling innovation.</p><ul><li><em>Technology should allow a business to innovate faster, not hold back innovation.</em></li><li><em>Technology moves at an exponential pace and software architectures need to be “evolution ready”.</em></li></ul><p>Software is often the key element to the technology puzzle. Actually, very seldom is software not involved. At Ingeno we believe that every business is a software business. We also believe that every line of code should be about the business!</p><h4>How confident are you about the new software released in Production?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/121/1*oQX1wavkAlnyalpQLQuCQw.png" /></figure><p>When new software is released into Production, what do you think are the honest expectations of your users or customers… Confidence? Apprehension? Although your customers badly need the new functionalities you are providing, do they push back on upgrades until others have had it in Production for months to “iron out” the issues? What about the actual mindset of your own developers? Confidence or apprehension?</p><p>Lack of confidence is not just a symptom; it can be a real showstopper for business innovation because it will prevent you from rapidly delivering innovation. Imagine the competitive advantage of new features in the hands of all your key customers immediately versus a long deployment cycle of months or even years! There are so many things you can’t even begin to consider as a business, so many lost opportunities, so high costs incurred when you can’t guarantee the quality of the code being delivered.</p><ul><li><em>If developers aren’t ready to support their code in Production 24/7 it might be a sign they don’t fully trust it.</em></li><li><em>Automated testing should be front and center in any IT strategy.</em></li><li><em>Models like DevOPS are key to IT and organizational performance, but require a shift in mindset.</em></li></ul><h4>Can new code be pushed into Production in a matter of minutes?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/121/1*6AH4ATfYIHlku2cBlXslXQ.png" /></figure><p>Let’s assume that your code is of the utmost quality and you are confident that it will not break current functionality or cause any type of regression once in Production: you’re off to a terrific start. Now you have to make sure that your testing and deployment processes are sufficiently automated to deploy it in Production rapidly? If not, then you have to rethink you approach to software development. Many successful innovating companies of diverse business domains have adopted the concept of a <em>continuous delivery pipeline</em> and have implemented it at the art of their development approach.</p><ul><li><em>New code is useless if it’s not in the hands of your users/customers. Unless it is it’s not creating value.</em></li><li><em>Expectation is now for very short, high quality, no-downtime releases.</em></li><li><em>Pressure to shorten release cycles and increase quality is incompatible with traditional delivery approaches.</em></li><li><em>Agile development is not synonym of short release cycles. Agile development is one ingredient. Other key ingredients such as application architecture, automated delivery pipeline, adequate infrastructure and development culture are also required.</em></li></ul><h4>How competitive is your TCO?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/121/1*KLUC6u8sIytvf9Lav-v1AA.png" /></figure><p>CFOs especially need to consider technology investments with a view of true cost over time. This is usually when SaaS solutions or Cloud computing in general, unavoidably come up in the discussion. Not that a Cloud option is necessarily the right choice, but when you consider <em>all</em> the costs associated with self-hosted, capitalized options, it is sometimes very difficult to justify them when compared to cloud based approaches. The key here is exactly that; properly considering ALL the costs of the different options. This is not easy to do. But this is definitively now part of the combined responsibility of the CFO-CTO team, no doubt about it!</p><ul><li><em>CIOs and CTOs are more than ever accountable for the cost effectiveness of IT solutions.</em></li><li><em>Innovative companies inevitably turn to the Cloud, not only to increase agility, but to leverage cost benefits.</em></li><li><em>No CTO today can claim to have a valid IT strategy if it doesn’t consider the potential benefits of Cloud technologies.</em></li></ul><h4>Do you have confidence your IT is secure &amp; compliant?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/121/1*iykayS1QMAxVUajLb09hng.png" /></figure><p>In today’s world, every business needs to be able to answer “yes” to this question. Lack of vigilance on the topic of security or adhesion to industry standards can obliterate your business overnight. I won’t bore you with the usual gloomy statistics of survival probability following a major security incident; we all know it’s something we would rather avoid. IT security requires access to the right expertise and the right processes, and it’s not cheap. I’m always surprised that among the first arguments <em>against</em> Cloud approaches is security; in my opinion, it often should be an argument <em>in favor</em>of it! Again, that’s a topic in itself, but think about all the knowledge and investment Amazon, Google and Microsoft are allocating to security? Not sure many companies can compare favourably. I think all agree that the CTO obviously needs to be on top of this one!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yZFrYxdqNRvNazI57EEtqQ.png" /></figure><ul><li><em>Skill sets, best practices, massive investments CAN be leveraged by a Cloud approach.</em></li></ul><p>I hope that this was valuable food for thought.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y8t3n8rnbUP3OS9eRizraQ.png" /></figure><figure><a href="http://bit.ly/2J7BTLN"><img alt="" src="https://cdn-images-1.medium.com/max/254/1*E0T9bAD3QW75OqcGvTmKGg.png" /></a></figure><p>by <a href="http://bit.ly/2J7BTLN">Denis Brochu</a><strong>,</strong> founder at INGENO</p><p>Learn more about us, how we build software and how we help companies deliver business value at <a href="http://ingeno.ca/">ingeno.ca</a>.</p><figure><a href="http://bit.ly/2GXibBu"><img alt="" src="https://cdn-images-1.medium.com/max/845/1*8R8MWKOWt3DCrnEeUih07Q.png" /></a></figure><figure><a href="http://bit.ly/2Gn54Zh"><img alt="" src="https://cdn-images-1.medium.com/max/845/1*l26rc5-FnAiHRT612hPNyw.png" /></a></figure><figure><a href="http://bit.ly/2J82vfu"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cdkYqsvo_H07N-BBoURZDQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6d5ae792426" width="1" height="1" alt=""><hr><p><a href="https://medium.com/be-the-revolution/evaluate-your-it-culture-in-five-questions-d6d5ae792426">Evaluate your IT culture in five questions</a> was originally published in <a href="https://medium.com/be-the-revolution">Be the Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Docker Birthday #5 — Quebec City]]></title>
            <link>https://medium.com/be-the-revolution/docker-birthday-5-quebec-29ad5ea1546e?source=rss----4cba98d132d8---4</link>
            <guid isPermaLink="false">https://medium.com/p/29ad5ea1546e</guid>
            <category><![CDATA[meetup]]></category>
            <category><![CDATA[workshop]]></category>
            <category><![CDATA[dockerqc]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Julien Maitrehenry]]></dc:creator>
            <pubDate>Thu, 05 Apr 2018 13:12:49 GMT</pubDate>
            <atom:updated>2018-04-05T15:29:06.374Z</atom:updated>
            <content:encoded><![CDATA[<p>Bonus : Free Docker workshop</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R1nlmkJFPmA2jPbts3FVOg.jpeg" /></figure><p>A huge thank you Docker Quebec Community for this annual event!</p><p>But this wouldn’t have been possible without the support of our sponsor for the place and the cake <a href="http://ingeno.ca/">Ingeno</a> and the support of our mentors!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6d9BvXFJFsSzbxRcWww1zg.jpeg" /></figure><p>During the event, participants had the opportunity to work on the following workshops:</p><h3>Workshop still available</h3><h4>Docker 101 — Linux</h4><p><a href="https://training.play-with-docker.com/dev-stage1/">Workshop link</a></p><blockquote><em>An introduction to Docker on Linux that takes you through the basics of the platform, building your first containers, and deploying them in an orchestration system. People taking these labs will come out understanding the basics of Docker and orchestration.</em></blockquote><h4>Kubernetes on Docker for Mac and Docker for Windows</h4><p><a href="https://github.com/dockersamples/docker-fifth-birthday/blob/master/kubernetes-desktop.md">Workshop link</a></p><blockquote><em>This lab will cover the basics of using Kubernetes on Docker for Mac and Docker for Windows. People taking this lab will gain an understanding of basic concepts of Kubernetes and how to create your cluster on your desktop.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ERH8yA_8fsxvOWjJz7itw.jpeg" /></figure><h3>Workshop only available during the meetup</h3><h4>Docker 101 — Windows Containers</h4><blockquote><em>An introduction to Docker on Windows that takes you through the basics of the platform, building your first containers, and deploying them in an orchestration system. People taking the lab will come out understanding the basics of Docker and orchestration.</em></blockquote><h4>Modernizing Traditional Java Apps</h4><blockquote><em>This lab will take a traditional, Java EE monolithic application and show you how to containerize it, and then break out a few pieces to have a more modern, modular deployment of the application built on Docker EE. People taking this lab will understand the basics of application modernization and Docker EE.</em></blockquote><h4>Modernizing Traditional .NET / Windows Apps</h4><blockquote><em>This lab will take a traditional, ASP.NET monolithic application and show you how to containerize it, and then break out a few pieces to have a more modern, modular deployment of the application built on Docker EE. People taking this lab will understand the basics of application modernization and Docker EE.</em></blockquote><h4>Deploying Multi-OS applications with Docker EE</h4><blockquote><em>In this workshop, you will deploy and refactor a traditional Java application on Linux, into a microservice application, some of the services in Java on Linux, some in .NET on Windows, and deploy the application on a hybrid Docker Enterprise Edition cluster with Linux and Windows nodes.People who take this lab will learn the basics of the Docker EE platform including security and orchestration using both Swarm and Kubernetes.</em></blockquote><h3>Some pictures from the event</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lY6Q5i48yzaobDHqEr-sbA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hjm9NyvyTfwoWvSCfpWKHA.jpeg" /></figure><p>Thanks all for celebrating the Docker 5th birthday and see you soon!</p><p><em>Originally published at </em><a href="https://jmaitrehenry.ca/2018/03/30/docker-birthday-5-quebec/"><em>jmaitrehenry.ca</em></a><em> on March 30, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29ad5ea1546e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/be-the-revolution/docker-birthday-5-quebec-29ad5ea1546e">Docker Birthday #5 — Quebec City</a> was originally published in <a href="https://medium.com/be-the-revolution">Be the Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Five Ingredients for True Agility in Software Development]]></title>
            <link>https://medium.com/be-the-revolution/https-medium-com-be-the-revolution-the-five-ingredients-for-true-agility-in-software-development-ee73aa5ddb95?source=rss----4cba98d132d8---4</link>
            <guid isPermaLink="false">https://medium.com/p/ee73aa5ddb95</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[human-capital]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[INGENO]]></dc:creator>
            <pubDate>Thu, 08 Mar 2018 13:51:23 GMT</pubDate>
            <atom:updated>2018-03-08T13:51:22.953Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s2rXPsi0OMHRXwTOt82CYQ.jpeg" /></figure><p>Businesses gargle themselves on their individual-driven culture, the importance of their values and the deep respect they have for their employees. Sadly, the messages sent are quite different when you see the plethora of processes put in place to ‘enable’ the workforce.</p><p>Let’s find out what should be considered when you are looking to improve your velocity through an agile strategy.</p><h3>Where Are You Starting From?</h3><p>While visiting enterprises, I am often asked what additional processes must be put in place to ‘drive’ agility in an upcoming project. Few will take the time to look at their current work environment and reflect on the foundation they want to build agility over. Agility cannot thrive in a culture of control.</p><ul><li>If the department entrance is controlled by a time clock or if you ask employees to fill in timesheets, are you implying that they are time thieves?</li><li>If you’re preventing your software developers from accessing production environments directly, are you telling them they’re a bunch of incompetents and may set your servers on fire?</li><li>If analysts are the only ones allowed to design the product, it is because your developers are mentally challenged and can’t understand the business domain and propose good solutions themselves?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*DPwQs8z7tmiRhtTfHrvkJg.png" /></figure><p>Challenge yourself with these types of ‘What then?’ questions:</p><ul><li>Could you do without a DBA?</li><li>Could you have developers directly interacting with customers?</li><li>Could anyone review pull requests?</li><li>Could you do without a dress code?</li></ul><p>I’m not telling you that these suggestions can be implemented everywhere. In fact, in many places this would not make sense. What I’m saying is that you have to ask yourself these questions. You cannot accept guidelines or directives without understanding the motivation behind them. <a href="https://goo.gl/YGQLAc">Be an original</a>!</p><h3>Removing Friction</h3><p>Low friction is the explanation that comes up most often when we analyze the dazzling successes of the likes of Netflix, Google or Tesla. These companies trust the person closest to a problem to make quick decisions and apply the most appropriate solutions. Can we live by this philosophy and progressively adapt our teams where applicable?</p><h3>A Recipe for True Agility</h3><p>The ideas supporting an agile strategy may be so simple that many will predict this cannot bring the intended results.</p><p>You do not impose agility. You need to create an environment where true agility will be allowed to naturally emerge. Hence, the ‘agile process’ oxymoron needs to be challenged. Strategies promoting agility have a higher chance of success and are based on the following principles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i-uWPFCCNb8unSd1KyOYKw.png" /></figure><h4>Goal</h4><p>If you do not explain to someone why they are tasked with something, it will be difficult for them to ask the right questions and independently make the right decisions. Worse, it could be impossible for your developers to detect changes in the requirements and quickly pivot to other solutions.</p><h4>Human Capital</h4><p>To build a great product, you need a team composed of great people. A common mistake here is to invest in processes and strict supervision rather than selecting great contributors based on their characters traits and technical excellence. Take the time to build an autonomous team rather than infantilize your workforce.</p><figure><a href="https://goo.gl/CwcKNM"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qJR6Pu4Np9JxtfYK0WZOQA.png" /></a></figure><h4>Direction</h4><p>Forget the big Hollywood styled missions with infrequents deployments and stressful milestones. Today, everything changes too fast. The concept of destination has been replaced by that of a constant, accelerated and endless evolution. Set a general direction instead and steadily progress toward it while adjusting for a moving target. Experience one-day sprints with the simple goal of being in a better position tomorrow than you were today. Repeat 365 times.</p><h4>Empowerment</h4><p>Setup your teams so that no one needs to ask permission to execute on something if they think that’s the right thing to do. If they have the expertise and are close to the issue at hand, they have to take action themselves. If they feel uncertain in their abilities, they should feel encouraged to ask for help. Here, the concept of appointing decision committees, technology custodians and process managers must be eliminated. You must remove single points of knowledge. It’s no longer your code, your server or your architecture. All can intervene anywhere to accomplish the mission.</p><p>At INGENO, we have adopted the DevOps model where teams of 2 to 5 highly skilled full stack developers will handle everything. From daily talks with the customer, architecture and design, test driven development and continuous deliveries to production, they do it all. These teams have all the necessary administrative accesses to all environments and tools required to support their daily activities. They to not need permission from anyone to make decisions and move forward immediately.</p><h4>Liability</h4><p>With great powers come great responsibilities. Being liable in a DevOps model is not synonymous with being the one who will be blamed when something bad happens. Being liable simply means you will be called upon to correct a situation if the broken item is managed by your team. When a developer has to support his code, his application, his architectural choices and his clients in production, he quickly develops an understanding of what works well and is not too risky.</p><blockquote>There are no kings inside the Gates of Eden. — Bob Dylan</blockquote><p>Do not spend efforts building barriers… Those who still defend their territories by creating processes and permission systems should instead focus on human capital.</p><p>Invest all your energy in promoting autonomy, team spirit and direct actions from people in the best position to solve a problem. If you believe that innovation is key to the future success of your business, value the simplicity of being able to make a decision and act on it quickly.</p><p>At your own company, how are you addressing the 5 principles of true agility?</p><p>Be the Revolution!</p><figure><a href="https://goo.gl/K2UUZ5"><img alt="" src="https://cdn-images-1.medium.com/max/200/1*SVFTY2tRLSTW3_8xSJ8E8A.png" /></a></figure><p>by <a href="https://goo.gl/K2UUZ5"><strong>Rémy Gendron</strong></a><strong>,</strong> founder at INGENO</p><p>Learn more about us, how we build software and how we help companies deliver business value at <a href="http://ingeno.ca/">ingeno.ca</a>.</p><figure><a href="https://goo.gl/EZg9QG"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2rP4OoX5TMqlIt-Ykjg1BQ.png" /></a></figure><figure><a href="https://goo.gl/q4gegy"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JKxhdiiJo-40xNSel6Y3sA.png" /></a></figure><figure><a href="https://goo.gl/RjA1gR"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7EYaIMHaKgWBJe_0F5kvog.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee73aa5ddb95" width="1" height="1" alt=""><hr><p><a href="https://medium.com/be-the-revolution/https-medium-com-be-the-revolution-the-five-ingredients-for-true-agility-in-software-development-ee73aa5ddb95">The Five Ingredients for True Agility in Software Development</a> was originally published in <a href="https://medium.com/be-the-revolution">Be the Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SCRUM Alone Cannot Save You]]></title>
            <link>https://medium.com/be-the-revolution/scrum-alone-cannot-save-you-722f360e95a7?source=rss----4cba98d132d8---4</link>
            <guid isPermaLink="false">https://medium.com/p/722f360e95a7</guid>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[INGENO]]></dc:creator>
            <pubDate>Wed, 04 Oct 2017 19:01:48 GMT</pubDate>
            <atom:updated>2017-10-04T19:13:08.861Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZrCoJ0RhKpfKQbH5UWxRsg.jpeg" /></figure><p>Many will jump on the agile bandwagon with the hope of solving their software development challenges. This often ends in terrible failures. Processes are adept at scaling good and bad practices indiscriminately.</p><p>Let’s understand why this frequently happens and what can be done differently to prevent it.</p><h4>What Was Working Before</h4><p>At the start of my career, almost 25 years ago, things were a lot simpler. The Web, SaaS, mobility, hacking and security, scalability, accessibility, zero downtimes and whatnot were simply out of the requirements list. Moreover, users were willing to accept buggy, incomplete and unfriendly software.</p><p>This meant that anyone with basic coding skills, some intuition, a simple development process and enough time could produce acceptable results.</p><p>Then what customers wanted started to change…</p><h4>Recipes Can Provide a False Sense of Transformation</h4><p>The industry and the art of software development did not evolve as fast as the requirements and expectations of technology consumers. We pushed back for a while by working harder and relying on senior talented developers, until people started creating software development processes.</p><blockquote>Processes are popular because they are seen by management as one-size-fits-all shortcuts that require little prior investments.</blockquote><p>When auditing projects, we too often see companies who think they have transformed themselves by stating that their next endeavors would use an agile approach. They retain the services of an agile coach, hire a SCRUM master and send their project managers on 3 days of agile training. They then immediately embark on a sizable, strategic 18 months project… and see it fail after 12 months.</p><p>Others are further along their transformation to a <a href="http://ingeno.ca/">Modern Software Culture</a>. They got through some initial stages (basic automation and testing) but are struggling to reach the next level. And they are looking for pointers and possibly external, temporary help to stay on the right path and prevent costly mistakes.</p><h4>Back to the Basics</h4><p>At our company we have, over the past years, transitioned away from exclusively hiring senior developers. We are now only hiring talented full stack <a href="https://medium.com/be-the-revolution/we-are-coders-d02b643d6ff0">Clean Coders</a>, TDD practitioners, explorers obsessed by automation and Continuous Delivery, Uncle Bob and Martin Fowler fans. We select individuals who are excited about learning new skills that can allow them to be the principal contributors and promoters of quality. The number of years of experience is no longer as relevant as before… to the contrary, some of our best new employees come to us straight out of school. But a sure thing is that we are not looking for process-oriented people.</p><blockquote>We now see that the gap in abilities and productivity between newly hired junior and senior developers is drastically less than before.</blockquote><p>The good news is that when onboarding is an active, group-oriented cultural concern applied through real training and mentoring, it takes a surprisingly short amount of time to get someone to an acceptable level of capabilities. Quality and production ready code, along with great velocity, is then the natural outcome if developers are paired with an environment that promotes autonomy.</p><h4>The Next Steps</h4><p>I believe that the only way to get to quality software is to start with the people themselves and their skills as individuals. Only then can you scale this foundation with agile processes and architectures that promote a <a href="https://medium.com/be-the-revolution/it-s-all-about-friction-8bfad59e8635">frictionless development process</a>.</p><blockquote>As an executive, RED FLAGS should be raised if your people are talking about SCRUM and Micro Services when you are NOT already operating in a culture obsessed by Clean Code, automation, and TDD.</blockquote><p>You also need to <a href="https://medium.com/be-the-revolution/the-pitfalls-of-agility-in-software-development-1d989c5b23ff">reconsider what needs to be built</a> and how will this new piece of software bring value to your customers. Although no methodology is one-size-fits-all, for all the reasons above we strongly prone KANBAN + DevOps in our development projects over traditional approaches like SCRUM.</p><p>Your checklist to a Modern Software Culture should include:</p><ul><li>Quality</li><li>Automation</li><li>Simplicity</li><li>Autonomy</li><li>Accountability</li></ul><p>These concepts are powerful drivers of velocity, innovation, and business value. Different solutions will apply but they all start with people.</p><p>Be the Revolution!</p><p>by Rémy Gendron, founder at INGENO</p><p>P.S. Learn more about us, how we build software and how we help companies deliver business value at <a href="http://ingeno.ca/">ingeno.ca</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=722f360e95a7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/be-the-revolution/scrum-alone-cannot-save-you-722f360e95a7">SCRUM Alone Cannot Save You</a> was originally published in <a href="https://medium.com/be-the-revolution">Be the Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On the Importance of Software Quality]]></title>
            <link>https://medium.com/be-the-revolution/on-the-importance-of-software-quality-205621e771c0?source=rss----4cba98d132d8---4</link>
            <guid isPermaLink="false">https://medium.com/p/205621e771c0</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[continuous-deployment]]></category>
            <category><![CDATA[test-driven-development]]></category>
            <dc:creator><![CDATA[INGENO]]></dc:creator>
            <pubDate>Fri, 05 May 2017 12:10:25 GMT</pubDate>
            <atom:updated>2017-05-03T14:52:03.228Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Why does it matter ?</em></h4><p>Well, those “Agile” methods are great, and even though nowhere in the agile manifesto does it say something about <a href="https://medium.com/be-the-revolution/software-quality-ec09dae64023">software quality</a> and development methods, one can quickly find their necessity. If a team follows the agile tenets and delivers value constantly, and it doesn’t have any tests nor perform any refactoring, it may start out great, but quickly the code base will deteriorate into an ugly mess, and the team productivity will drop to nearly zero.</p><p>Why ? Because it will become harder and harder to keep the pace in adding new features, let alone refactoring the existing code to support those new features while avoiding breaking existing ones.</p><p><strong><em>And that leads to what is, I think, one of the most important advantages of TDD : it gives a safety net.</em></strong> Suddenly, you can refactor the code without fear of breaking anything, and the feedback loop for doing so is very short. From a developer’s viewpoint, it’s much more satisfying to work in this way : you get the feeling to go forward, to build something durable. Because bugs you fix will never reappear : a test covers them and is added to the suite, so when a new developer later does something completely unrelated and breaks your thing by accident, he will know right away and fix his mistakes. What could have been yet another bug will have been fixed directly at the source, instead of reappearing at the end of the development process and taking hours to spot, debug and fix (yet again). Without any guarantee it won’t break again in the future.</p><blockquote>So, much like a mountain climber who places anchors in the rocky wall to prevent him from falling down too much if he slips, test coverages prevents us from going backwards by introducing regression bugs.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P11WMo27irSX6CludH9euA.jpeg" /></figure><p><strong><em>And that leads to my other point, software quality increases product quality.</em></strong><em> </em>It ain’t no silver bullet that will fix everything, as there could still be edge cases that have not been covered, misunderstandings in specifications and such, but the vast majority of what could have ended up as bugs will simply not be there.</p><p><strong><em>Tests also have another substantiable benefit : live documentation</em></strong>. How many have stumbled upon an old comment or spec that does not reflect at all what the application really does ? Probably too many. When avoiding almost entirely “traditional” documentation and focusing only to have the most readable and exhaustive tests possible, it turns out you don’t really need much traditional documentation. And this new documentation will always be in sync with the application. And it won’t be just flat, static text. They will serve as a “demo” of what the code is supposed to do. Think of the implication for future developers (future being yourself in 2 months or a new developer), how easy it could be to “grasp” the system.</p><h4><strong>Continuous integration / continuous deployment</strong></h4><p>If there is one constant in the universe, it’s that humans tend to make mistakes. And they’re not very good at repetitive tasks. But machines are. So we should try to automate as much as possible. If deploying the code into production takes a dozen of manual steps, chances are you won’t want to do it often (so it will impact negatively your release schedule/response time) and easy, stupid errors may slip up from time to time. Like messing a step up, copying a wrong file, at the wrong place, or forgetting it entirely.</p><p>So what if this step could be taken off the developer’s shoulders, and entirely automated ? There are tools doing just that, and they should be used.</p><h4><strong>Conclusion</strong></h4><p>From a business standpoint, if software gets released, it’s all that matters, right ? Well, the smoother and faster that process is, the better. So, to sum up those points :</p><ul><li>Software quality increases, bugs fixed once and for all;</li><li>Live documentation, for future developers to quickly grasp the system;</li><li>Release cycle shortened, response time decreased.</li></ul><p>Be the Revolution!</p><p>by François Roseberry, Software Developer at INGENO</p><p>Learn more about us at <a href="http://ingeno.ca/">ingeno.ca</a>.</p><p>Related Story: <a href="https://medium.com/be-the-revolution/software-quality-ec09dae64023">Software Quality</a> by Denis Brochu, founder at INGENO</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=205621e771c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/be-the-revolution/on-the-importance-of-software-quality-205621e771c0">On the Importance of Software Quality</a> was originally published in <a href="https://medium.com/be-the-revolution">Be the Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pride over Money]]></title>
            <link>https://medium.com/be-the-revolution/pride-over-money-412c2b93fd2?source=rss----4cba98d132d8---4</link>
            <guid isPermaLink="false">https://medium.com/p/412c2b93fd2</guid>
            <category><![CDATA[ncaa]]></category>
            <category><![CDATA[golf]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[sports]]></category>
            <category><![CDATA[pride]]></category>
            <dc:creator><![CDATA[INGENO]]></dc:creator>
            <pubDate>Wed, 29 Mar 2017 00:34:23 GMT</pubDate>
            <atom:updated>2017-03-29T00:34:22.631Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UAAt_yoRxcQkY_vq7GWn_Q.jpeg" /></figure><p>It takes an incredible amount of effort and good decisions to build a successful athletics program. Some have accomplished what was initially perceived as unconceivable and have succeeded in becoming influencers and leaders in their market. Others have literally became an inspiration for their local communities.</p><p>What does it take to build such a successful environment?</p><p>Here at Athlex, we are lucky to be working with such incredible organizations and one relationship that makes us particularly proud is our association with Université Laval’s Rouge et Or, one of the most successful athletic program in Canada.</p><p>My partners and I have had the opportunity to be part of their golf program during our college years, which definitely makes it extra special for us. The Rouge et Or program is respected across the country and has become a great source of pride in Quebec City. They’ve been able to build and sustain a structure and an atmosphere that allows them to attract talent and character year after year.</p><blockquote>The Rouge et Or Football is one of the youngest team on the Canadian university circuit. Founded in 1996, Laval won their first national championship in 1999 and have won 9 Vanier Cup championships over the last 20 years.</blockquote><p>This success naturally contributed to an amazing, faithful fan base. Obviously, money and tradition cannot explain how this came to happen so quickly. What was and still is the magical ingredient to this team success?</p><p>This is a tough question with several variables involved, but everything seems to start with leadership and passion. When the people in charge are ready to go where others won’t, when you are willing to put everything on the table, the resulting pride of being part of the program becomes an incredible trademark, funnelling quality in the recruitment stages and then promoting athletic success.</p><h3>My Own Story</h3><p>From my perspective as a former college athlete at Laval and as the consecutive winner of the 2009 and 2010 university provincial golf championship, there is one thing that clearly stands out. I remember how proud my coaches and the program managers were to represent the school in tournaments and in their everyday life. Looking in their eyes when they would talk about their team or program, you could tell how inspired they felt to be representing the Rouge et Or.</p><p>Having our coaches being able to communicate that passion played a huge role in inspiring my teammates and I and that it’s one of the reasons we felt so compelled to compete for our program.</p><blockquote>We were forgetting our own personal gains and instead working hard to honour and perpetuate the successes obtained before us.</blockquote><p>My time with the Rouge et Or golf program felt different than anything else I had the opportunity to experience before. While we’re used to mostly think about ourselves in golf, our coaches had the ability to make us feel like we were more than golf players. We were the faces of the Rouge et Or program. In all honesty, I can tell you that I miss this feeling a lot. Never had I felt that I could have such an impact for an athletic group before and it made me play the best golf of my life.</p><blockquote>Good teams become great ones when the members trust each other enough to surrender the ‘me’ for the ‘we’.</blockquote><blockquote>– Phil Jackson, Basketball</blockquote><p>A lot has changed since I’ve graduated from university. But it still seems like the pillars of a successful program are still found in leadership, pride and common goals.</p><p>As I’ve personally evolved from a student-athlete to starting my own business in technology, I’m proud today that Athlex is helping such a successful program as the Rouge et Or continue to honour its tradition of greatness by promoting efficient collaboration through real-time communication and chat-based technologies.</p><p>Be the Revolution!</p><p>Guest post by Mathieu Bélanger, founder at ATHLEX</p><p>Learn more about us at <a href="http://getathlex.com/home/">getathlex.com</a> and at <a href="http://ingeno.ca/">ingeno.ca</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=412c2b93fd2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/be-the-revolution/pride-over-money-412c2b93fd2">Pride over Money</a> was originally published in <a href="https://medium.com/be-the-revolution">Be the Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>