<?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 José Roniérison on Medium]]></title>
        <description><![CDATA[Stories by José Roniérison on Medium]]></description>
        <link>https://medium.com/@joseronierison?source=rss-ff7be9ece56------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*3-YoJ5c3gTBVCDya.</url>
            <title>Stories by José Roniérison on Medium</title>
            <link>https://medium.com/@joseronierison?source=rss-ff7be9ece56------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:23:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@joseronierison/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[How TDD helps software architecture to be clean]]></title>
            <link>https://medium.com/stonetech/how-tdd-helps-software-architecture-to-be-clean-1f38cd0c5aad?source=rss-ff7be9ece56------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f38cd0c5aad</guid>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-testing]]></category>
            <dc:creator><![CDATA[José Roniérison]]></dc:creator>
            <pubDate>Mon, 07 Jan 2019 12:40:14 GMT</pubDate>
            <atom:updated>2019-01-07T14:05:19.031Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This article was writen in english since english is a common language for software engineering area. If you want to read it in another language, I would suggest you to give a try with a </em><a href="https://translate.google.com/"><em>translator</em></a><em> to help you out.</em></p><p>Throughout my experience I heard many times how Test Driven Development helped to maintain the code in a good shape, keeping methods and classes small, avoiding code rigidity as it make easier to follow laws and principles. However, the point I want to bring up today is how TDD goes beyond the code and also impacts the architecture.</p><p>I am going to focus on how TDD makes the communication among micro services mature and bring up a discussion on how the test driven mindset enables the team to create reliable micro services, how it brings a user centered thinking and how it guides the project to avoid anti patterns.</p><p>Before we get started, I need to say that although TDD is a great support to achieve a clean architecture, it certainly is not the unique required knowledge. Some techniques as micro services, DDD and reactive patterns could be also necessary to tackle complexity. They all work together.</p><h3>Relationship between testability and reliability</h3><blockquote>A messed code is hard to test, a messed architecture is hard to test as well.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/1*Qbemyibg7dYQKZA3pOTL4w.jpeg" /><figcaption>Tom planning a trap to catch Jerry in Tom &amp; Jerry cartoon.</figcaption></figure><p>But what I mean by a messed architecture? I mean an over-complex one! One with a lot of accidental complexity, where the wheel was reinvented two or three times, where there isn’t a good responsibility definition and all this makes the solution rigid, slow and difficult to rely on. You can remove all these complexities and the product will still be there.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F4WFEPa71o5Vm2bd02s%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fcomplexity-unnecessary-accidentalcomplexity-4WFEPa71o5Vm2bd02s&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F4WFEPa71o5Vm2bd02s%2Fgiphy-downsized-large.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/dcd12db006c19f6ba63a83f5e39eb7c0/href">https://medium.com/media/dcd12db006c19f6ba63a83f5e39eb7c0/href</a></iframe><p>In the last years I saw some Tom’s solutions (gif above) that became messed due to different reasons. There were applications too big that required a xxx-large machine just to run it: impossible to test efficiently. And also there were applications spliced in many places without a good responsibility definition, bad communication with each other, data integrity errors, dependent deployments among other issues: small changes in those systems were really a pain.</p><p>Fortunately, TDD appeared in my daily work and the adjective “testable” became one of the most important adjectives. That adjective has a close relationship with the system reliability. To start develop guided by test was an effective way to tackle the code/architecture complexity and a broad solution that changed the team mindset.</p><p>I picked up some points of the relationship between TDD and software reliability in the following list:</p><ul><li>TDD keeps the team with high code coverage, so you feel better to do a code refactoring without breaking features in production. The code, the architecture and the universe tend to chaos, if you are not able to do a efficient refactoring, your architecture is going to be messed up in a short time.</li><li>TDD avoids accidental complexity. Let’s think together: if you start coding the tests and lot of unnecessary complexity jumps from hell, and testing becomes a pain (a lot of scenarios, failure cases, dependencies and so forth), you do have to stop and rethink your solution. We all know that we have to improve the solution to be testable.</li><li>TDD guides us to use community patterns instead of reinventing the wheel since there are a lot of tools to test those patterns already available. For instance, if you need to create a feature to share something among other services, it is pretty easy to test HTTP’s patterns with RSpec, Scalatest, Cucumber and other frameworks tools.</li><li>By running the functional tests, the visibility of non functional requirements comes up daily as the test automation run in the pipeline. For example, if a functional test ran in 13 seconds for the past 4 weeks and after some code change it degraded to 19 seconds: you are able see which commit added that degradation in the application performance, thus you can take an action to avoid your application to be slow. If you have to fix it later, probably there will a lot of code changes you should consider so won’t be that easy to fix the issue.</li><li>A testable code tends to be aligned with market technology. To create a test we need to think how to make sure the functional requirements are met. For instance, I have seen testable code tending to use containerization technologies because it is pretty simple to test the whole application inside a container that is the same one that is going to be used in production. <a href="https://www.infoq.com/br/articles/kubernetes-effect">That impacts the software architectures in many good ways</a>.</li></ul><h3>Team members journey perspective</h3><p>Currently at Stone I’m dealing with the experience of building a team with a QA mindset, TDD is a key practice to ensure it. Those are the points where TDD supports the team onboarding:</p><ul><li>Even for people which are pretty new coding, TDD helps them ensure the quality;</li><li>Tests are a live documentation whom teach the domain side of the code;</li><li>New hires grow up with a testing mindset that maintains the system reliable;</li></ul><h3>Infrastructure perspective</h3><p>During some conversations at Stone we talked about good questions of infrastructure tests and one of the points was that they not as mature as software tests are. Does the infra tests sometimes test the test itself? Does tools like <a href="https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/">liveness probe</a> from Kubernetes do what the infra tests was supposed to do? Does the performance tests already an infra test was supposed to do?</p><p>Anyway, the key point on the talk was that a clean architecture (a testable one) is easier to provision and monitor. Services that runs in containers with their inputs and outputs tested as a whole, that is not a Tom’s solution, enable the team to have flow’s visibility in any environment.</p><p>Those are my thoughts on how TDD impacts system architecture that I have seen in the last 4 years practicing it. I hope it helps on your journey.</p><p>Share you feedback and thoughts, it would be great to hear other perspectives.</p><p>Thanks <a href="https://medium.com/u/84394d76b465">Marcus Lucas</a>, <a href="https://medium.com/u/e87225d50585">Diego Morales</a> and <a href="https://medium.com/u/a538889f8357">RafaR</a> for improving this article.</p><h3>References</h3><p><a href="https://www.linkedin.com/in/joseronierison/">My developer life</a> — José Roniérison</p><p><a href="https://www.amazon.com.br/Test-Driven-Development-Kent-Beck/dp/0321146530?tag=goog0ef-20&amp;smid=A1ZZFT5FULY4LN&amp;ascsubtag=go_1494986073_58431735035_285514469186_aud-519888259198:pla-538704511116_c_">TDD By Example</a> — Kent Beck</p><p><a href="https://www.infoq.com/articles/kubernetes-effect">Kubernetes Effect</a> — <a href="https://www.infoq.com/profile/Bilgin-Ibryam">Bilgin Ibryam</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f38cd0c5aad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/stonetech/how-tdd-helps-software-architecture-to-be-clean-1f38cd0c5aad">How TDD helps software architecture to be clean</a> was originally published in <a href="https://medium.com/stonetech">stonetech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My two cents in dependability, fault tolerance and Hystrix]]></title>
            <link>https://medium.com/@joseronierison/my-two-cents-in-dependability-faults-and-hystrix-b82e1fbb7dc7?source=rss-ff7be9ece56------2</link>
            <guid isPermaLink="false">https://medium.com/p/b82e1fbb7dc7</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[fault-tolerance]]></category>
            <category><![CDATA[hystrix]]></category>
            <category><![CDATA[dependability]]></category>
            <dc:creator><![CDATA[José Roniérison]]></dc:creator>
            <pubDate>Wed, 06 Sep 2017 02:03:08 GMT</pubDate>
            <atom:updated>2018-01-18T21:59:00.497Z</atom:updated>
            <content:encoded><![CDATA[<p>In my last projects, I have seen the increase of dependability among the services in order to attend the rise of business requirements and also to reach the implementation of <a href="https://martinfowler.com/articles/microservices.html">microservice</a> architecture.</p><p>Even with all known benefits of microservice architecture, the aiming of this articles is sharing with you some of my experience to deal with two cons of microservice architecture: <strong>dependability and faults</strong>. So, the main point is: as more as I split the dependencies responsibilities among services much more edge of communication is added and hence the fault risk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KdVUxnOKCCgtNSNeW76GKg.png" /><figcaption>In Monolithic there is only DB as uniq point of communication failure, in the microservice approach there are seven+</figcaption></figure><p>To make<strong> </strong>the system more resilient is necessary <strong>to avoid breaking user experience </strong>even after failure, be aware of faults and take automatically corrective decisions to <strong>recover fast </strong>and<strong> </strong>improve the <strong>visibility</strong> of system behavior.</p><h3>Kind of preamble of helpful taxonomy</h3><p>Let me share some words of taxonomy to help the understanding on this subject before start talking into it deeper.</p><ul><li><strong>Errors </strong>is<strong> </strong>inconsistent state which generate an incorrect value and it can provoke a failure</li><li><strong>Faults</strong> happens when a defect in the design or in the operation of the system causes an error, in other words, when something affects the system badly</li><li><strong>Failures </strong>happens when the system stops to provide its service as expected</li></ul><p>So, as I dealt with a service which communicate through a bunch of services I realized there is a great number of possibles faults as: development, operational, natural phenomena, hardware, software, malicious, accidental and so on.</p><p>Thus what we can do is to embrace the chaos and do it gracefully.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*rtNnHZgWuTJNpIaz." /><figcaption>A cat making some calculus to try jumping from a shelf to another shelf and then, the cat fails gracefully</figcaption></figure><h3>Circuit Breaker on system boundaries</h3><p>What worked very well for my team was the Circuit Breaker pattern (that was widespread by Michael Nygard in his book <a href="https://www.amazon.com/gp/product/0978739213?ie=UTF8&amp;tag=martinfowlerc-20&amp;linkCode=as2&amp;camp=1789&amp;creative=9325&amp;creativeASIN=0978739213">Release It</a>). Summarising, this pattern is a way to protect your system from failures when it has to make remote calls — in a similar way of a physical circuit breaker idea.</p><p>The circuit breaker logic monitor the health of requests. While everything is going well and the percentage of errors is beneath the threshold, the circuit is still <strong>closed </strong>and<strong> </strong>the requests continue to be made. Otherwise, when the supplier service is on a failure state or responding in a huge delay causing timeouts AND the percentage of this bad responses is over the threshold, then the circuit <strong>opens </strong>and the application stops doing this call.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/397/1*IYcFkCXqRd78eN5OC9oBBw.png" /><figcaption>Circuit breaker diagram</figcaption></figure><p>This is a very simple overview of the Circuit Breaker pattern. If you want to go deeper, I suggest this Martin Fowler&#39;s <a href="https://martinfowler.com/bliki/CircuitBreaker.html">article</a>.</p><h3>Hystrix as circuit breaker lib</h3><p>Hystrix is a java library which provides tolerance of latency and failure which mainly implements the circuit breaker pattern. Hystrix also implements Thread Pool, Semaphore and Command pattern in order to abstract implementation and improve the performance of problematics requests you would like to make.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/264/0*t0lQEgB5BqcFqvpQ." /><figcaption>The hystrix logo (it looks like a panda). My team call me crazy, but I really see a panda here</figcaption></figure><p>The command implementation of Hystrix wraps the network call and provides a very simple way to add configurations to different cases.</p><p>A really simple command code (just for didactic purposes) in Scala looks like:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b5e8d67187df80c9ca691c922fa86f37/href">https://medium.com/media/b5e8d67187df80c9ca691c922fa86f37/href</a></iframe><p>The <strong>settings</strong> of command are in the object GetDependencyCommand, which says respectively that this command will:</p><ul><li>use thread pool strategy</li><li>wait 1 second before checking if a open circuit is healthy again</li><li>open the circuit when error is 70% + in the bucket window (more info <a href="https://github.com/Netflix/Hystrix/wiki/How-it-Works#circuit-breaker">here</a>)</li><li>the maximum time waiting for thread response is 2 seconds</li></ul><p>There are so many config options and you can see more <a href="https://github.com/Netflix/Hystrix/wiki/Configuration">here</a>, this is a very simple configuration.</p><p>The <strong>run </strong>method in class GetDependencyCommand is the place to call the function that makes the request which can fail. In run method execution is possible to throw a exception that will be catched in <strong>getFallback</strong> method, for instance, if in the dependency response there is contract break.</p><p>The <strong>getFallback</strong> method is the place where you can handle the things gracefully or, at least, protect the service of a non-handled failure. There are three approaches to handle this faults:</p><ul><li><strong>Custom Fallback: </strong>this approach is good when the data can be replace by a stale data, a placeholder and so on. For instance, instead of listing the a catalog using the response of the recommendation service is possible make just a alphanumerical ordination.</li><li><strong>Fail Silent: </strong>this is a good approach when the data is optional and can just be replaced by a null value.</li><li><strong>Fail Fast: </strong>this is always the last option, but when the dependency is so necessary that without him there is nothing to be displayed to the user, just say to user: &quot;Oh Crap! We are broken, but we will recover as fast as we can&quot; and this approach helps you to keep the promise of recover fast, since when the faults take place the circuit opens, then the application stop calling the unhealthy dependency and <strong>still alive.</strong></li></ul><p>The hystrix also lib also provide a way a dashboard to improve the visibility of service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1011/0*52ru3TDpYd34Jy7C." /><figcaption>Dashboard with a bunch of circuits</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*jr3r9Ljq8Vo2V0Ik." /><figcaption>Meanings of number in command dashboard</figcaption></figure><p>The Netflix team also provide the <a href="https://github.com/Netflix/Turbine/wiki">Turbine</a> which aggregate the circuits among your service instance in a unique dashboard.</p><h3>Reaping the fruits</h3><p>Is much more easy to deal with a high volume of requests, reducing the risk of the whole ecosystem fails in peaks.</p><p>The dashboard improves the visibility of dependency faults. This dashboard can stay together the team radiator, so the team will be more aware of service health.</p><p>Not to mention that made much easier to look after scheduled down time of external dependencies, since the service can recover as soon as the external service is back to normal its operation.</p><p>Finally, reflecting: I never know when a ballet dancer fails, the user should never know when a service fails as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*XHKU6f5GHdH3R3qy3RnJmg.gif" /><figcaption>A ballet dancer dancing on a theater</figcaption></figure><h3>Thanks for reading</h3><p>I hope that was a good reading! Feel free to comment, share your feedback, a different point of view or a meme. :D <em>(face smiling)</em></p><h3>Fontes:</h3><p><a href="https://medium.com/netflix-techblog/fault-tolerance-in-a-high-volume-distributed-system-91ab4faae74a">https://medium.com/netflix-techblog/fault-tolerance-in-a-high-volume-distributed-system-91ab4faae74a</a></p><p><a href="https://www.nasa.gov/pdf/636745main_day_3-algirdas_avizienis.pdf">https://www.nasa.gov/pdf/636745main_day_3-algirdas_avizienis.pdf</a></p><p><a href="https://martinfowler.com/articles/microservices.html">https://martinfowler.com/articles/microservices.html</a></p><p><a href="https://martinfowler.com/bliki/CircuitBreaker.html">https://martinfowler.com/bliki/CircuitBreaker.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b82e1fbb7dc7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Biografia]]></title>
            <link>https://medium.com/joseronierison/biografia-eb30dd6d94b1?source=rss-ff7be9ece56------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb30dd6d94b1</guid>
            <category><![CDATA[biography]]></category>
            <dc:creator><![CDATA[José Roniérison]]></dc:creator>
            <pubDate>Sun, 26 Feb 2017 20:49:20 GMT</pubDate>
            <atom:updated>2018-11-06T23:39:17.212Z</atom:updated>
            <content:encoded><![CDATA[<p>Olá, meu nome é José Roniérison, mas todos me chamam de Roni. Sou Pernambucano, casado com Dayanne Íris e tutor de um cachorro excêntrico chamado Festus. Atualmente sou consultor/desenvolvedor de software na Thoughtworks. Apaixonado por trabalhar e estudar — sou assumidamente academicista e realmente gosto de estar dentro da universidade . Fui fortemente influenciado pela filosofia Clean Code, pelo desenvolvimento guiado por testes e pela metodologia ágil<em>.</em> Comecei na programação por diversão fazendo jogos de console quando estava doente. Roni por Roni :D <em>(olhinhos com sorriso aberto)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*DCMV0qf6mlK4foAgTQnu4Q.jpeg" /><figcaption>Day, Eu e Yasmin (minha irmã)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/639/1*p-2tFJb_6hgVn8I1nyGjyQ.jpeg" /><figcaption>Esse é Festus indo pro rola</figcaption></figure><p>Encontre-me em:</p><p><a href="https://www.facebook.com/JoseRonierison">https://www.facebook.com/JoseRonierison</a></p><p><a href="https://www.linkedin.com/in/joseronierison/">https://www.linkedin.com/in/joseronierison/</a></p><p><a href="https://twitter.com/JoseRonierison">https://twitter.com/JoseRonierison</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb30dd6d94b1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/joseronierison/biografia-eb30dd6d94b1">Biografia</a> was originally published in <a href="https://medium.com/joseronierison">joseronierison</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scrum Hello World]]></title>
            <link>https://medium.com/joseronierison/scrum-hello-world-23ad1af663dd?source=rss-ff7be9ece56------2</link>
            <guid isPermaLink="false">https://medium.com/p/23ad1af663dd</guid>
            <category><![CDATA[agile-scrum-methodology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[José Roniérison]]></dc:creator>
            <pubDate>Mon, 07 Nov 2016 03:25:31 GMT</pubDate>
            <atom:updated>2017-07-06T01:04:47.000Z</atom:updated>
            <content:encoded><![CDATA[<p><em>O Scrum</em> tem sido utilizado na equipe da qual faço parte para observar a ligação entre cada etapa do processo com os princípios do manifesto ágil e assim alcançar a fluência em deixar nossos clientes satisfeitos, assunto <a href="https://medium.com/joseronierison/de-repente-agile-d43286d46be9#.slq5cp7z1">abordado no post anterior</a>.</p><p>Então a questão é: por que o que aparentemente é tido normalmente como uma receita de bolo pode dar tão errado? Exatamente pelo mesmo motivo que alguém que não tem prática em fazer um bolo normalmente erra: não seguir a receita. Então vamos refletir um pouco com uma analogia com o Shu Ha Ri, algo que considero uma incrível sabedoria das artes marciais.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*qTpHgh2JuUO5w76jDCjjHg.png" /><figcaption>Imagem: <a href="http://bit.ly/2fgDPT9">http://bit.ly/2fgDPT9</a></figcaption></figure><p><strong>Shu Ha Ri </strong>se trata de um ciclo de treinamento ensinado no aikido, no qual o <em>Shu</em> é o ciclo no qual o aluno apenas aplica as regras estritamente como elas são, o <em>Ha </em>a reflexão é exercitada para adaptação do uso do método pelo aluno e no <em>Ri</em> o aluno poderá superar o método. Note que no <em>jiu jitsu</em> o ato de repetir por centenas de vezes o <em>armlock </em>possibilita a noção de como é possível variar e modificar essa posição por conta própria depois de meses de treinamento e, posteriormente, absorvendo os princípios físicos e fisiológicos que são o seus fundamentos, é superada mais uma barreira. Ou seja, se pularmos uma fase a próxima será apenas teoria, um corpo sem coordenação.</p><p>Claro que o mesmo se aplica ao inserir a metodologia Scrum dentro das equipes. Pular passos fundamentalmente simples fará com que a equipe se torne imprecisa e ao mesmo tempo não consiga mensurar suas capacidades.</p><p>Logo<strong> burlar os passos do <em>scrum</em></strong><em> </em>como as <em>daily’s</em>, inserir/remover <em>cards </em>durante a sprint e planejar fantasias farão com que a equipe permaneça estagnada, nunca progredindo. <strong>Não ter uma entrega contínua com iterações curtas</strong>, também o fará, podendo criar um misto entre a rigidez do <em>planing mindset</em> e as expectativas — que quase sempre serão frustradas — de facilidade na mudança de requisitos.</p><p>Então lembre-se que para aprender a andar de bicicleta haverão quedas e que ninguém nasce sabendo. Renove o processo, mas tenha consciência da maturidade que a equipe tem antes de tirar as rodinhas, então assim você possibilitará a equipe a alcançar uma maior fluência do ágil na cultura e no <em>mindset</em>.</p><h3>Agradecimentos</h3><p>import { agradecimentos } from <a href="https://medium.com/joseronierison/de-repente-agile-d43286d46be9#.slq5cp7z1">De repente agile</a></p><h4>Referências</h4><p>Agile Manifesto — &lt;<a href="http://agilemanifesto.org/principles.html">http://agilemanifesto.org/principles.html</a>&gt;</p><p>Scrum: The art of doing twice the work in half the time — Jeff Sutherland &lt;http://amzn.to/2eBShV0&gt;</p><p>Eduardo Borges — Visão do Produto no Scrum&lt;<a href="https://youtu.be/vg1S1WYZa6o">https://youtu.be/vg1S1WYZa6o</a>&gt;</p><p>Eduardo Borges — Métodos ágeis e documentação de software &lt;<a href="https://youtu.be/3Smbhnmue7Y">https://youtu.be/3Smbhnmue7Y</a>&gt;</p><p>Shu Ha Ri — &lt;<a href="http://www.aikidofaq.com/essays/tin/shuhari.html">http://www.aikidofaq.com/essays/tin/shuhari.html</a>&gt;</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23ad1af663dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/joseronierison/scrum-hello-world-23ad1af663dd">Scrum Hello World</a> was originally published in <a href="https://medium.com/joseronierison">joseronierison</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[De repente agile]]></title>
            <link>https://medium.com/joseronierison/de-repente-agile-d43286d46be9?source=rss-ff7be9ece56------2</link>
            <guid isPermaLink="false">https://medium.com/p/d43286d46be9</guid>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[agile-development]]></category>
            <dc:creator><![CDATA[José Roniérison]]></dc:creator>
            <pubDate>Mon, 07 Nov 2016 03:11:47 GMT</pubDate>
            <atom:updated>2016-11-08T11:46:16.929Z</atom:updated>
            <content:encoded><![CDATA[<p>Ametodologia ágil é um tema recorrente no meio de desenvolvimento de software. Tem objetivo satisfazer o cliente, tornar equipes mais motivadas e aumentar a qualidade do produto. Então, quais os obstáculos no caminho para se ter desenvolvedores com pensamento ágil? Quais obstáculos para fazer uma equipe ágil? E quais os obstáculos para alcançar uma empresa com uma cultura ágil?</p><p>O caminho para alcançar essa fluência permeia todo processo de desenvolvimento e em cada um destes passos pode ser feito algo para entregar valor adiantado para o cliente e <strong>ser</strong> mais <em>agile</em>.</p><h3><strong>Entrega adiantada e contínua de Valor</strong></h3><p>Voltando para a década de 1990 onde o <a href="https://youtu.be/URlnxbaHhTs?t=102"><em>planing mindset</em></a><em> </em>era a visão mais comum no desenvolvimento de software, o <a href="https://pt.wikipedia.org/wiki/Modelo_em_cascata">modelo em cascata</a> deste <em>mindset</em> tinha o objetivo de produzir contratos para definir o que o cliente receberia e um prazo no qual ocorreria a entrega, que normalmente era dado em semanas ou meses. Apesar do modelo em cascata ainda ser utilizado hoje em dia, escolhi usar o futuro do pretérito para passar o <em>feeling</em> de prazos fantasiosos encontrados no histórico do <em>planing mindset</em>.</p><p>Mas o que ocorre com projetos em equipe que tem o <em>mindset </em>de<em> planing </em>para haver tantas falhas<em>? A </em>pergunta a ser feita é “no que a equipe está focando?”. Se a resposta é cumprir o contrato, isso acarretará na desconsideração das mudanças de contexto, de mercado e de visão do cliente ocorridas durante o processo de desenvolvimento e gerará a insatisfação do cliente e consequente falha do projeto.</p><p>Então a metodologia ágil reage a essas falhas, alterando o foco para a entrega software de valor para o cliente, e o pulo do gato é notar que há algumas <a href="https://pt.wikipedia.org/wiki/Sine_qua_non"><em>conditios sini qua non</em></a><em>.</em></p><p><strong>Entregas continuas e frequentes</strong></p><p><a href="http://agilemanifesto.org/principles.html">Os três primeiros princípios do manifesto ágil</a> tem uma correlação forte, que pode ser traduzida por entregas incrementais.</p><p>Portanto, entregar software funcionando com frequência, aceitar a mudança de requisitos e consequentemente entregar valor de forma adiantada é fundamental para satisfação do cliente. Ou seja, sem entregas continuas e incrementais para obter uma entrega final adiantada, o risco de frustração cresce por não ouvirmos nossos clientes. Note como isso lembra uma das falhas do <em>planing</em>.</p><p>Logo vemos que pequenas entregas de valor no menor período de tempo possível possibilita:</p><ul><li>feedback do cliente, <em>product owner </em>e outros interessados;</li><li>acolhimento de novos requisitos e re-priorização do <em>backlog</em> a partir do feedback recebido;</li><li>avaliação da sustentabilidade do projeto do ponto de vista de mercado e retorno financeiro;</li><li>a real compreensão do andamento do desenvolvimento do produto, visto que é possível mensurar a velocidade da equipe e a qualidade da entrega;</li></ul><p>Ou seja, c<a href="https://youtu.be/aoMfbgF2D_4"><em>ontinuous delivery</em></a><em> </em>é uma poderosíssima ferramenta não só do ponto de vista técnico, mas também do ponto de vista de negócios.</p><p><strong>Ter uma equipe que decida como trabalha, nivelada e multifuncional</strong></p><p>Partindo para prática e aplicando a metodologia ágil, logo ficará claro que <a href="https://youtu.be/URlnxbaHhTs?t=868">as equipes nem sempre respondem da mesma forma às mudanças para o ágil</a> e <a href="https://youtu.be/URlnxbaHhTs?t=996">modificar a forma de visualizar o mundo do desenvolvimento de software para ágil também não terá resultados instantâneo</a>s. Isto acontece em decorrência da natureza dos problemas em desenvolvimento de software e da natureza das pessoas envolvidas no desenvolvimento de software.</p><p>But why? <a href="https://youtu.be/URlnxbaHhTs?t=819">Diferentes problemas exigem diferentes formas de resolvê-los</a> e os times necessitam da liberdade e a capacidade de decidir como resolvê-los. Isto implica <a href="https://youtu.be/DngAZyWMGR0?t=49">a desconstrução da visão da definição de um plano de como cada um irá trabalhar</a>, na desconstrução da hierarquia dentro das equipes e resultante construção de um time multifuncional conforme Suttherland (2014, p.50).</p><p>Então, joguem fora os crachás!</p><p>Tenha em mente <a href="https://youtu.be/URlnxbaHhTs?t=1036">uma escala gradual</a>, citada por Martin Fowler em sua palestra sobre Agile Essence and Fluency, onde são elencados os estágios e a estimativa de absorção da cultura ágil em uma organização. <strong>Foco no valor</strong>, <strong>entrega de valor</strong>, <strong>otimização do valor</strong> e <strong>alinhamento com a cultura da empresa</strong>. Cada uma delas tem seu tempo, variando de alguns meses à cinco anos para se obter fluência em cada estágio.</p><p>Por fim, deixo uma reflexão: ter uma equipe com profissionais <a href="http://bit.ly/2fpKI4T">T-Shaped</a> pode ser um facilitador para este processo?</p><p>Tudo isto parece ser um desafio e tanto para se alcançar. Então por onde começar? Isto é um assunto que irei abordar no próximo artigo.</p><p>Espero que tenham gostado e que esse compartilhamento de experiência tenha te acrescentado algo de bom. Ficarei muito feliz com as críticas positivas ou negativas. Forte abraço!</p><h3>Agradecimentos</h3><p>Fico grato por todo conhecimento obtido nos diálogos e convivência com os membros da minha atual equipe, assim como demais amigos da Ignição Digital, que tem sido uma grande fonte de renovação e conhecimento. Em especial agradeço a <a href="https://br.linkedin.com/in/thom%C3%A1s-alvarenga-26419891">Thomas Alvarenga</a> e <a href="https://br.linkedin.com/in/vitornogueiraa">Vitor Nogueira</a> pelas longas conversas sobre assuntos ligados a metodologia ágil, assim como opiniões sobre este artigo; agradeço também a <a href="https://br.linkedin.com/in/marcuslucasfalcao/pt">Marcus Lucas</a>, <a href="https://br.linkedin.com/in/brunoquaresma1">Bruno Quaresma</a> e <a href="https://br.linkedin.com/in/dayvsonlima">Dayvson Lima</a> por seus olhares críticos, revisão e consequentes melhorias e a Dayanne Lima pela revisão gramatical.</p><h4><strong>Referências</strong></h4><p>Agile Manifesto — &lt;<a href="http://agilemanifesto.org/principles.html">http://agilemanifesto.org/principles.html</a>&gt;</p><p>Martin Fowler — Agile Essence and Fluency &lt;<a href="https://youtu.be/URlnxbaHhTs">https://youtu.be/URlnxbaHhTs</a>&gt;</p><p>Martin Fowler — Continuous Delivery &lt;<a href="https://youtu.be/aoMfbgF2D_4">https://youtu.be/aoMfbgF2D_4</a>&gt;</p><p>Martin Fowler — Making Architecture Matter &lt;<a href="https://youtu.be/DngAZyWMGR0">https://youtu.be/DngAZyWMGR0</a>&gt;</p><p><a href="http://tableless.com.br/author/diegoeis/">Diego Eis</a> — O perfil T-Shaped e o dev full-stack — &lt;<a href="http://bit.ly/2fpKI4T">http://bit.ly/2fpKI4T</a>&gt;</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d43286d46be9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/joseronierison/de-repente-agile-d43286d46be9">De repente agile</a> was originally published in <a href="https://medium.com/joseronierison">joseronierison</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>