Eight Points For One Team Is Two Points For Another Team
- Lloyd Atkinson tl;dr: "In my ongoing quest to explore the problems that are endemic to modern software development, I decided to focus in particular on estimation and the disaster that is “story pointing.”" Lloyd discusses the antipatterns experienced when estimating, including failing to realize story points are an estimate, coercing developers into choosing a lower number, discounting high or low numbers, and more.featured in #309
Agile And The Long Crisis Of Software
- Miriam Posner tl;dr: "Recently, though, some signs are emerging that Agile’s power may be fading. A new moment of reckoning is in the making, one that may end up knocking Agile off its perch." Miriam discusses the negative impact and aspects of agile development on eng teams.featured in #307
Accessibility in Agile Transformational Practices
- Dylan Barrell tl;dr: How to develop accessibility practices into your agile processes (1) create central team to manage the transformation (2) Execute an ongoing empathy program (3) Curate a set of high-quality learning resources and integrate into onboarding (4) Form a team of accessibility coaches to coach teams (5) Create an accessibility dashboard.featured in #144
featured in #143
How To Balance The Tension Between Data Science And Agile
- Anat Rapoport tl;dr: Although specific deadlines are not alway possible with Data Scientists, flexible timelines & goal setting are. Trust & communication are key. Work in short cycle so DS aren't siloed for long.featured in #133