InfoQ Homepage Presentations Martin Fowler and Dan North Point Out a Yawning Crevasse of Doom
Martin Fowler and Dan North Point Out a Yawning Crevasse of Doom
Summary
In this presentation filmed during QCon London 2007, Martin Fowler and Dan North talk about the communication gap existing between the developers and the customers or users. Closing this gap is extremely important in order to create successful software.
Bio
Martin Fowler is one of our industry's most well known thought leaders having had an influence in the adoption of OO, refactoring, patterns, agile methodologies, domain modeling, UML, and XP. Dan North is a principal consultant with ThoughtWorks, where he writes software and coaches teams in agile and lean methods. He believes in putting people first and writing simple, pragmatic software.
About the conference
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community.QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
Community comments
Great presentation!
by Stephen Cresswell,
Partly Disagree
by Sara Jay,
Re: Partly Disagree.
by Sara Jay,
Great presentation!
by Stephen Cresswell,
Your message is awaiting moderation. Thank you for participating in the discussion.
Shame it's cut short by (what I assume to be) a few minutes
Partly Disagree
by Sara Jay,
Your message is awaiting moderation. Thank you for participating in the discussion.
I think I would not go as far as to say that the BA (Business Analyst) does not need to be the middle man in software projects. The set of tasks that developers need to do , every day become increasingly bigger and bigger - Architecting, Design, Coding, Unit Testing, Integration Testing, Memory Profiling, Learning on new technologies, Versioning, etc. etc. This makes them impossible to remove the ferry man and create a direct bridge between the business and developers. A techno functional BA must be present to write the requirements documents and translate between jargons, so that developers can atleast go home by 12.00 Midnight. You see, if developers come to work cursing, because they are not getting enough work-life balance, that is not a good thing either.
However, there has to be workshops on a regular basis (perhaps every couple of weeks) between the developers and the business so that the developers get a feel of what the business really wants out of a project.
On other days, the ferry man's duty is translation, adding functional ideas to the business folks and giving them to the developers, so that developers concentrate on their core activities.
Re: Partly Disagree.
by Sara Jay,
Your message is awaiting moderation. Thank you for participating in the discussion.
But one thing that I like, is Martin Fowler's way of presenting concepts, either in his books or at a talk. Simply phenomenal!! I used to like Josh Bloch's presentation skills. Martin Fowler is just as good, if not better.
Keep it up Martin!