Once you have a program (a collection of interrelated projects focused on one business goal) and you have technical debt, you have a much bigger problem. Not just because the technical debt is likely bigger. Not just because you have more people. But because you also geographically distributed teams, and those teams are almost always […]
I’ve had several conversations in email and with clients recently that have all been about this question: “What do we do about our infrastructure?” Either the project or the program has to create/update/upgraded their architecture or automated test infrastructure, pay down technical debt, or somehow do something that’s not part of a story. And, that’s
I’ve been developing an agile architecture workshop with Rebecca Wirfs-Brock. Aside from more Murphy’s Law moments than a small project deserves, we’ve encountered a number of agile architecture and program myths. Here are three for your reading pleasure. (Just in case you aren’t sure, all of these are false–they are myths.) “We don’t need no
I hope that this 3-part series on how to move to continuous integration and how to evaluate if it’s worth moving to continuous integration on your program convinced you moving to continuous integration was worth it for programs. The reason continuous integration is an issue on programs, is because the lack of CI can delay
I’ve been blogging about agile architecture, and the responses have been fascinating. Some people are totally against the idea of an agile architect, regardless of the size of the program. Others are ready to give me the benefit of the doubt. In this column, let me clarify the case for (or against) the job-titled agile
I missed one presentation in my last post. At Oredev, I had an opportunity to speak with the PMI Sweden folks (at least, the southern Sweden folks). I talked about Agile Program Management, and discussed my current thinking about agile program management. As I’ve been working with clients, I’ve been updating my thinking—what a surprise
I spent the most recent four weeks conferencing. I had a blast. Because I kept traveling, I nicknamed this series of conferences my “Northern Hemisphere Conference Tour.” I’ve posted the slides on slideshare.net. Oct 24-Oct 28, I was in Vancouver, BC at Much Ado About Agile 2011. I delivered a keynote entitled, “Where is Agile
Workshop Objective: This experiential workshop provides you with an understanding and options for how you might create a successful geographically distributed agile project. The topics we’ll address are how to plan and execute the work for a geographically distributed project. Workshop Overview: If you have teams all over the world trying to create a product together, you
Israel Gat had a great Agile Cutter Advisor recently, the Friction of Agile (registration required). He discussed the friction of agile going up in geographically distributed teams because of the dis-economies of assimilation (the space-time continuum problem, and the issue of under-funding the infrastructure of the non US-based teams). He had a stunning (to me)
I’ve been keeping up with my email newsletters this year—at least, better this year than previously. Yesterday, I posted “Organizing Programs.” I received several emails agreeing with that one. Apparently, I struck a nerve. If you think you are supposed to be on my email list, and you are not receiving the emails, please let