Best of Agile — December 2024

1. 1
   Article

   Medium·1y

   My DOs and DON’Ts of Software Architecture

   A software architect shares personal dos and don'ts based on their experience. Key advice includes treating everyone as equals, ensuring clarity, documenting decisions, defining ownership, using architectural contracts, and avoiding over-architecture. The don'ts emphasize challenging directives, proposing solutions with problems, and avoiding 'WaterGile' by implementing true Agile methodologies. This guidance aims to help navigate workplace dynamics and drive successful projects.

   112

   2
2. 2
   Article

   InfoQ·1y

   Software Architecture and the Art of Experimentation

   Architecting software involves unavoidable instances of being wrong, making experimentation crucial. Minimum Viable Architectures (MVAs) test the viability of architectural decisions, providing data to refine them. Effective experiments should be atomic, timely, and unambiguous, focusing on verifying assumptions. The goal is to minimize the cost of mistakes by running small, manageable experiments and making informed, sustainable decisions that support long-term value.

   22
3. 3
   Article

   The New Stack·1y

   Scrum Sucks Because You’re Doing It Wrong

   Scrum is often misunderstood and misapplied, leading to frustration among engineers. Effective scrum implementation requires understanding its fundamentals, such as having a fully cross-functional team, conducting meaningful standups and retrospectives, and correctly handling metrics like story points and velocity. Common pitfalls include partial adoption of agile practices, incorrectly set teams, and not acting on retrospective feedback. Addressing these issues can greatly improve the success of scrum in a team.

   10

   1