Learnings

<p>a thoughtful (and a bit controversial) reflection on the state of Agile Workflow </p>

<p>“In software, the greatest source of waste <em>is building the wrong thing</em>, period, not building the right thing slowly, not building the wrong thing slowly, just flat-out building things that add no value.” </p>

<p>How teams work at Nubank </p>

<p>Fixed-Everything: Agile? </p>

<p>Iterating a React Design with Styled Components </p>

<p>Scrum is a solution, not a goal. Understanding your agile needs first. </p>

<p>“While acceptance is good to control the development life-cycle of the feature, success is about mid/long-term impact and value created for real users of your product.” </p>

<p>“What are the key qualities of a great Product Leader? What makes a great Product Manager?” </p>

<p>Why software projects take longer than you think – a statistical model: </p>

<p>a bunch of useful tips on how to process design feedback from stakeholders </p>

<p>Excellent article about the trade-offs of Monolith, Microservices, Nanoservices, and Monorepo. Where Do You Want Your Complexity? </p>

<p>You don’t need standup </p>

<p>how to integrate design into the agile process </p>

<p>an agile process to design good onboarding experiences </p>

<p>Why Agile Isn’t Working and What Basecamp Does Differently: </p>

<p>Sprint Retrospective with DAKI: </p>

<p>Visual explanation why refactoring should be part of new features, not backlog: </p>