Neal Ford investigates agile architecture and design, specifically addressing how big up-front architecture and design fail because of the unknown unknowns of a project. Read more
Complex software always has an architecture, even if it isn’t intentional. Being agile isn’t enough. It isn’t prudent to just keep your code clean and hope that good architecture will simply emerge. Especially when there is a lot of technical risk, interdependencies, and conflicting priorities. Good architecture requires ongoing attention and stewardship. Read more
The most important question to be asked when developing a new software system is “How will we replace it?” It is however a question seldom asked. Instead organization focus on reusability, which unfortunately helps create rigid and inflexible software architectures. The talk shows how to design an Agile systems made up of small parts, why you should standardize on protocol and not platform and how you will end with a system that is easier to scale and maintain. Read more
There is widespread acceptance that software development using Agile methods works well. However, there are still areas of software development organizations that view their roles or mandates as incompatible with Agile methods. This talk addresses the legitimate role of an Enterprise Architect and provides concrete recommendations on how Architects can work with Agile development teams to accomplish their objectives. Topics will include concerns about data architecture, addressing the “ilities”, and why evolutionary architecture works. Read more
This video discusses using TDD and BDD to avoid complexity and creating evolving architectures where convention is emphasized over configuration. Read more
Software architecture plays a pivotal role in the delivery of successful software yet it’s frustratingly neglected by many teams. Whether performed by one person or shared amongst the team, the architecture role exists on even the most agile of teams yet the balance of up front and evolutionary thinking often reflects aspiration rather than reality. Read more
This short video summarize a clinic held at the Scrum Gathering that took place in Amsterdam, November 2010 and where the question was “What is the role of Architects in Scrum?”.
There often seems to be a tension that surfaces between the process (that which guides us) and the execution (that which we do). Agility and architecture also play out in this same way, and it can be a very destructive. Yet, each side needs the other to exist. In this session, we will turn this tension into a powerful force that you can use to achieve a balance between keeping the problem and it’s solution under control.
Watch this video on oredev.org
This experience reports focuses on the major scrum–related technical challenges that arose during a 120 000 hour scrum controlled project. For each of them, we try to identify the cause and the consequence, and then follow up with any solutions we tried. Finally we sum up and assess whether the problem was successfully solved or not.
James Coplien explains the DCI (Data, Context, Interaction) paradigm used to better represent the user’s mental model in code through system state and behavior. Coplien makes an attempt to reintroduce architecture to Lean and Agile projects due to its value in sustaining high velocity and change resiliency.keep looking »