Big Design Upfront was considered so evil in the early days of Agile that it acquired its own acronym. It’s time we relearned that great products start with asking the right questions.
Giovanni Asproni shows how to create a software architecture with just the right amount of design that can be incrementally evolved (or changed) as the system grows and changes.
Karen Siers outlines the difficulties encountered by a developer switching from a waterfall or cowboy coding environment to a collaborative Agile style.
Giovanni Asproni suggests that teams should not blindly embrace a methodology but rather create their own suiting their specific needs by using an approach based on patterns and pattern languages.
Dror Helper shares from his experience implementing Agile practices in his team, outlining the do and don'ts that can make all the difference. He addresses teams working in a non-agile environment.
Barry Hawkins considers as necessary to have a development process but in the same time maintaining a critical view of it in an attempt to improve it and make it fit within the current context.
James Kovacs explains how to use TDD and BDD to focus the architectural efforts on the high-value areas of the code in order to obtain just-in-time software architecture.
Simon Ogle, Alexander Kikhtenko, and Peter Thomas present a case study of a development team transitioning from a waterfall approach to 15 offshore Agile teams over a period of 5 years.
Experiences and lessons learned facing DevOps problems in the IT trenches (even if they weren’t calling it DevOps!). The good, the bad, the surprises, and ideas for the future.
Eric Evans advocates on gradual blending of modeling and design into iterative development in an attempt to create a solution that expresses the domain and is flexible enough to support changes.
In large organizations, it’s simply not practical to just "flip a switch" and have your IT department start doing agile all at once.