Talks
(Click on this icon
for slides or handout.)
In Seattle and Vancouver, slides for presentation on Technical Debt
. in October 2011.
At Agile New England in Waltham, Mass. on July 7, 2011, Agility and Architecture or: What colours is your backlog?
.
At the CSEE&T conference in Honolulu on May 23rd, the Frog and Octopus
.
At the Workshop on Architecture at RUG, in Groningen, Netherlands, on April 18th 2011, Games Architects Play
.
At Agile Vancouver, on March 21st, On Technical Debt
.
My “Sabbatical Year” Talks around the world:
- For Agile Spain attendees, slides on Agility in Context
(Spain)
Similar to the keynote at Agile Brazil. (See also this post) - For LAC2010 attendees, slides on “Technical Debt (or Investment opportunity)”
(Netherlands) - For EuroSPI attendees, slides on “the Octopus” (context)
.(France) - For ECSA attendees, here are the slides of the Keynote
and of my tutorial with Paris Avgeriou on Architecture Knowledge Management
. (Denmark)
- For colleagues in New Zealand and Australia, here are more recent slides on Software Architecture Knowledge Representation

- For JUG Wellington attendees, talk on Agility and architecture
, on February 17th, 2010. (New Zealand)
Not too different from the presentation in Capetown (South Africa).
For OOP 2010 attendees, here are the missing slides
, for the afternoon “exercise”. (Germany)
Three presentations in Japanese, with many thanks to Taku Fujii:
- Software Architecture Today, @ OGIS, Japan December 2009
- Software Architecture Knowledge Management, @ UMTP, Japan December 2009 (more here)
- Is Agility a New Passing Fad?, @ Agile Association, Japan December 2009
Older presentations, and in English, mostly:
- Agile Vancouver Conference, Nov. 3, 2009: What Colours is your Backlog (revisited)

… where I revisit an older presentation, adding some elements about value, cost, technical debt, risk… Videos of the presentation are here.
- JAOO, Århus, Denmark, Oct 7, 2009: Software Architecture Representation

- Agile Vancouver on September 21, 2009 & Scrumtisch in
Berlin on June 17, 2009: What colours is your backlog?
… where I speak about backlog and time-box, about value versus cost, about visible features versus invisible features (and in particular software architecture), about defects and technical debt, and more generally about release planning and sprint planning for non-trivial and long-lived software development projects.
Can an architecture-centric process be also agile? Should an agile team focus on architecture? BUFD and YAGNI? More a matter of co-existence between two cultures.
- Scrum Gathering, in Orlando, March 2009: What colours is your backlog? (see above; almost same slides)
… where I contend that most of the value of any software development practice depends on its context, and that Agility for an organization is not defined by simply embracing a labeled set of practices; nor even by a level of conformance to the agile manifesto. Agility should be defined relative to the value it brings to the business, namely the capacity of an organization to react and adapt faster than its environment can change. How agile an organization is, or can afford to be, will depend not on the practices alone, but on the context in which they are applied: how fit to that context are they. How do we define “context”? What elements or attributes of this context have a bearing on the selection of the set of practices an organization should adopt, and therefore how ‘agile’ it should strive to be? I’ll share some experience of applying agile practices far from their “sweet spot”, leading to the concept of situated agile processes. (see also this post)

Trackbacks