I grant that the group was not diverse with regard to ethnicity, gender, age, nationality. But amongst the seventeen people, I do count quite a few schools of thought.
There are the eXtreme Programming people: Ron Jeffries, Kent Beck (also of TDD fame), Ward Cunningham (also inventor of the CRC cards and the wiki, and already a house hold name in the software pattern community). Also to be positioned in the XP camp at that point in time: Martin Fowler (best known at that time for popularizing Refactoring techniques) and James Grenning (who invented Planning Poker)
Then there are the Scrum people: Ken Schwaber, Jeff Sutherland, Mike Beedle
And half a dozen other methodologies (RAD, Dynamic systems development method, Crystal Clear, Adaptive Software Development, Feature-driven development, Object-Oriented Systems Analysis) are represented by Arie van Bennekum, Alistair Cockburn, Jim Highsmith, Jon Kern and Steve Mellor: who either developed the methods or at least published about them.
And although Brian Marick, Bob Martin, Andy Hunt and Dave Thomas didn't invent their own processes and methods, they all had published rather successful books about several aspects of software development.
I think with regard to ideas they had, they were quite a diverse group. I find it actually rather astonishing that they got a high-level consensus (the manifesto) as a result of their prolonged week-end.
But frankly, to me a much more interesting and pressing question than the diversity of this group, is, whether the manifesto for agile software development did actually constitue a good develoment or whether it might be considered a disservice in hindsight.
Diversity of thought is a pretty pale substitute for actual diversity. As someone flippantly pointed out elsewhere in this thread, melanin is not midochlorians. BUT melanin is statistically correlated with lower median household income and accumulated wealth, with being incarcerated or having an incarcerated family member, with single parenthood, and with being misidentified by AI.
When I look at the above group I don't actually see that much diversity of thought. I see a group of people who are likely not primary caregivers for children or elderly parents. I see a group of people who is more likely to be promoted to management if they choose that career path. I see a group of people who were affluent enough to have access to personal computers and professional development related to personal computing in the 1990s, before this was super common. I can't list the CV of everyone on this list, but it seems to me that this group also skews toward consultancy shops as opposed to product shops. These things all inflect the base assumptions that are baked into the manifesto. The question of whether agile software development constitutes good development praxis is inseparable from the diversity of the philosophy's founding group.
For example, if you have a lot of spare time to devote to professional development outside of work hours, you might press for more (or all) of your hours at work to go to pair programming. Pair programming in itself isn't a bad thing, but if it's all you're doing, you might be eliminating time that someone would ordinarily spend studying design patterns, or experimenting with refactoring methods on their own to get practical experience. If you think that all of that sort of professional development should take place outside of work hours, you're implicitly stating something about the kind of person who ought to be able to work in software. This isn't just an arguably bad moral stance, it leads to worse software.
If you don't have women on your team from the beginning, you're less likely to develop anti-harassment and safety tools. See also: Twitter. I bet someone with incarcerated family members would probably have something to say about the development of prison e-readers that are used to restrict access to books for incarcerated people. Likewise, they might have valuable insight into algorithms that predict recidivism rates that are based on biased and incomplete datasets that target residents of low income and black neighborhoods. Having trans people on your team is great for privacy and data collection standards, because they know to question the data collection fields that you might think are a no brainer, but are actually unnecessary for you to store!
I take your point that these seventeen men are not identical. But their collected viewpoints fall so radically short of representing and addressing the needs of a growing and shifting population. Software is made for people, by people. Right now, a lot of people's valuable insights are dismissed by virtue of being excluded from the room. These seventeen men might have come to a consensus over a long weekend. But they stopped there. They didn't solicit amendments or context reads from their diverse colleagues. In 2001, it was likely that they didn't have many diverse colleagues. That had important ripple effects that are still manifesting. This should be instructive for how we compose our teams and build our products.
That's a great question and a lovely summary of all the original contributors to the original agile manifesto and principles. I'd be more than happy if people want to discuss that.
I'm enjoying rereading a lot of the writing about agile at the time and some of the more recent trains of thought and contributions. As part of a team coming fresh to working in an Agile/Scrum setting a lot of the ideas still seem helpful and useful. I've written here about the ones that have enthused me.
Disservice is a big word. I think the manifesto has directed thinking about what is good or bad and what is valued in a particular direction. On a personal level I was shocked at the point I realized how much it shaped (or fitted) my natural assumptions and values.
Every so often something stops me short and shows me there are alternative ways to see the world - sometimes through choice, sometimes through lack of choice.
These are smart guys who knew their jobs. A lot of their books were my mentors when I was first learning how to code in a work environment. What they said has value but it is not written in stone.
Everyone coming now has the chance to adopt, adapt and change that if they want to better fit their needs. I wrote the post because I wondered what that world might look like.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I grant that the group was not diverse with regard to ethnicity, gender, age, nationality. But amongst the seventeen people, I do count quite a few schools of thought.
There are the eXtreme Programming people: Ron Jeffries, Kent Beck (also of TDD fame), Ward Cunningham (also inventor of the CRC cards and the wiki, and already a house hold name in the software pattern community). Also to be positioned in the XP camp at that point in time: Martin Fowler (best known at that time for popularizing Refactoring techniques) and James Grenning (who invented Planning Poker)
Then there are the Scrum people: Ken Schwaber, Jeff Sutherland, Mike Beedle
And half a dozen other methodologies (RAD, Dynamic systems development method, Crystal Clear, Adaptive Software Development, Feature-driven development, Object-Oriented Systems Analysis) are represented by Arie van Bennekum, Alistair Cockburn, Jim Highsmith, Jon Kern and Steve Mellor: who either developed the methods or at least published about them.
And although Brian Marick, Bob Martin, Andy Hunt and Dave Thomas didn't invent their own processes and methods, they all had published rather successful books about several aspects of software development.
I think with regard to ideas they had, they were quite a diverse group. I find it actually rather astonishing that they got a high-level consensus (the manifesto) as a result of their prolonged week-end.
But frankly, to me a much more interesting and pressing question than the diversity of this group, is, whether the manifesto for agile software development did actually constitue a good develoment or whether it might be considered a disservice in hindsight.
Diversity of thought is a pretty pale substitute for actual diversity. As someone flippantly pointed out elsewhere in this thread, melanin is not midochlorians. BUT melanin is statistically correlated with lower median household income and accumulated wealth, with being incarcerated or having an incarcerated family member, with single parenthood, and with being misidentified by AI.
When I look at the above group I don't actually see that much diversity of thought. I see a group of people who are likely not primary caregivers for children or elderly parents. I see a group of people who is more likely to be promoted to management if they choose that career path. I see a group of people who were affluent enough to have access to personal computers and professional development related to personal computing in the 1990s, before this was super common. I can't list the CV of everyone on this list, but it seems to me that this group also skews toward consultancy shops as opposed to product shops. These things all inflect the base assumptions that are baked into the manifesto. The question of whether agile software development constitutes good development praxis is inseparable from the diversity of the philosophy's founding group.
For example, if you have a lot of spare time to devote to professional development outside of work hours, you might press for more (or all) of your hours at work to go to pair programming. Pair programming in itself isn't a bad thing, but if it's all you're doing, you might be eliminating time that someone would ordinarily spend studying design patterns, or experimenting with refactoring methods on their own to get practical experience. If you think that all of that sort of professional development should take place outside of work hours, you're implicitly stating something about the kind of person who ought to be able to work in software. This isn't just an arguably bad moral stance, it leads to worse software.
If you don't have women on your team from the beginning, you're less likely to develop anti-harassment and safety tools. See also: Twitter. I bet someone with incarcerated family members would probably have something to say about the development of prison e-readers that are used to restrict access to books for incarcerated people. Likewise, they might have valuable insight into algorithms that predict recidivism rates that are based on biased and incomplete datasets that target residents of low income and black neighborhoods. Having trans people on your team is great for privacy and data collection standards, because they know to question the data collection fields that you might think are a no brainer, but are actually unnecessary for you to store!
I take your point that these seventeen men are not identical. But their collected viewpoints fall so radically short of representing and addressing the needs of a growing and shifting population. Software is made for people, by people. Right now, a lot of people's valuable insights are dismissed by virtue of being excluded from the room. These seventeen men might have come to a consensus over a long weekend. But they stopped there. They didn't solicit amendments or context reads from their diverse colleagues. In 2001, it was likely that they didn't have many diverse colleagues. That had important ripple effects that are still manifesting. This should be instructive for how we compose our teams and build our products.
THANK YOU Jess. Yes. I really appreciate you lifting up specific ways lack of representation has led to extremely harmful products and practices.
That's an awesome reply. Thanks for expressing all that so eloquently.
That's a great question and a lovely summary of all the original contributors to the original agile manifesto and principles. I'd be more than happy if people want to discuss that.
I'm enjoying rereading a lot of the writing about agile at the time and some of the more recent trains of thought and contributions. As part of a team coming fresh to working in an Agile/Scrum setting a lot of the ideas still seem helpful and useful. I've written here about the ones that have enthused me.
Disservice is a big word. I think the manifesto has directed thinking about what is good or bad and what is valued in a particular direction. On a personal level I was shocked at the point I realized how much it shaped (or fitted) my natural assumptions and values.
Every so often something stops me short and shows me there are alternative ways to see the world - sometimes through choice, sometimes through lack of choice.
These are smart guys who knew their jobs. A lot of their books were my mentors when I was first learning how to code in a work environment. What they said has value but it is not written in stone.
Everyone coming now has the chance to adopt, adapt and change that if they want to better fit their needs. I wrote the post because I wondered what that world might look like.