Best of Agile — July 2024

1. 1
   Article

   Community Picks·2y

   Understanding Tdd vs Bdd : A Guide For Developers

   TDD (Test Driven Development) and BDD (Behavior Driven Development) are two development approaches that emphasize testing and collaboration but have distinct differences. TDD is developer-centric and focuses on code correctness, while BDD is user-centric and revolves around system behavior. TDD involves writing tests before code, whereas BDD involves writing behavior specifications before code. Both methodologies can be complementary, with TDD ensuring technical correctness and BDD ensuring the application meets user expectations. Examples and steps to implement each approach are provided.

   167

   8
2. 2
   Article

   groCTO·2y

   6 atomic habits of highly efficient CTOs

   Kovid Batra, founder of groCTO, shares six crucial habits that distinguish highly effective CTOs: holding daily stand-ups, scheduling deep work sessions, conducting regular one-on-ones, continually updating one's knowledge, and moving quickly with immediate feedback loops. These habits foster alignment, productivity, strong team relationships, and continuous improvement.

   150

   9
3. 3
   Article

   Lobsters·2y

   Fear of over-engineering has killed engineering altogether

   Over the past two decades, there has been a shift in software engineering from rigorous planning to rapidly shipping products without much foresight. While agile methodologies have benefited the tech industry, there's a growing concern that the pendulum may have swung too far, leading to a disregard for basic engineering principles. The post emphasizes the importance of using simple tools like napkin math and Fermi problems for making informed decisions, ultimately saving time and resources. By sharing examples from the development of fika, the author illustrates how basic calculations can prevent costly mistakes and optimize development processes.

   97

   4
4. 4
   Article

   InfoQ·2y

   Thinking Like an Architect

   Key insights into the role of architects include their function as IQ amplifiers, enhancing team intelligence by simplifying complex concepts and fostering better decision-making. They bridge organizational levels, use metaphors to make technical ideas relatable, and leverage simplified models for effective problem-solving. The ability to see multiple dimensions enables architects to introduce innovative solutions, tackle constraints, and balance standardization with innovation.

   47
5. 5
   Article

   Community Picks·2y

   Is Agile over?

   Agile, once the dominant methodology for software development and business operations, is facing scrutiny as many organizations report poor outcomes from its implementation. The problem often lies in superficial adoption, leading to failed transformations and disillusionment. The solution may lie in focusing less on rigid frameworks and more on desired outcomes and team behaviors, promoting true agility over mere adherence to Agile principles.

   40

   6
6. 6
   Article

   The New Stack·2y

   Devs Need System Design Tools, not Diagramming Tools

   Engineering teams often face the XY problem when selecting tools for software system design, focusing on specific solutions instead of underlying issues. This results in fragmented approaches and significant inefficiencies. System design goes beyond diagramming and requires tools that support dynamic and continuous design processes, incorporating real-time updates, collaboration, and comprehensive system understanding. Modern software's complexity demands tools that facilitate visibility and understanding, surpassing the limitations of traditional diagramming tools.

   38

   4
7. 7
   Article

   The Mountain Goat Software·2y

   How to Create a Story Map When Writing User Stories

   Story maps visually represent user actions to achieve a goal, aiding in understanding and planning for agile projects. They help prioritize the product backlog, uncover user needs, and visualize how features fit together. Created at project initiation or when new capabilities are developed, story maps involve the entire Scrum team and stakeholders. The horizontal dimension shows sequential user steps, while the vertical dimension presents alternative steps. Additional features like headers and submaps enhance readability and functionality. Story maps can guide the creation of product roadmaps and identify missing functionalities.

   14
8. 8
   Article

   The Mountain Goat Software·2y

   What Does a Product Owner Do, When, and Why?

   Product owners play a vital role in product development, balancing responsibilities between chronological planning and cyclical activities. Key actions include understanding the market, engaging stakeholders, maintaining the product backlog, building trust, being a good teammate, and continuously improving. Their work is crucial in guiding projects from conception through to the final launch, while always remaining flexible to adapt to changes.

   13
9. 9
   Article

   Hacker News·2y

   Story Points are Pointless, Measure Queues

   Story points, a widely used method in Agile for estimating effort, are criticized for being inconsistent, confusing, and counterproductive. The post explains why story points fail, citing variability among teams, misuse in comparing team velocities, and the flawed conversion of points to time. Instead, the post advocates for managing queues by focusing on task breakdowns, eliminating uncertainties, and tracking historical progress. This method aims to provide more reliable estimates and improve project flow and decision-making.

   12

   2