InfoQ

InfoQ

Presentation

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Recorded at:
Recorded at

Martin Fowler and Dan North Point Out a Yawning Crevasse of Doom

Presented by Martin Fowler & Dan North on Aug 13, 2008 Length 00:56:19
Sections
Process & Practices
Topics
Collaboration ,
Agile ,
Communication
Tags
DSLs ,
Feedback ,
Domain Driven Design ,
Qcon London 2007 ,
QCon ,
Ubiquitous Language
The next QCon is in London March 5-9, Join us!
 

How would you like to view the presentation?

In case you are having issues watching this video, please follow these simple steps to help us investigate the issue:
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
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.

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

  • This article is part of a featured topic series on Agile
Great presentation! by Stephen Cresswell Posted
Partly Disagree by Ashwanth Fernando Posted
Re: Partly Disagree. by Ashwanth Fernando Posted
  1. Back to top

    Great presentation!

    by Stephen Cresswell

    Shame it's cut short by (what I assume to be) a few minutes

  2. Back to top

    Partly Disagree

    by Ashwanth Fernando

    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.

  3. Back to top

    Re: Partly Disagree.

    by Ashwanth Fernando

    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!

Educational Content

Questions for an Enterprise Architect

Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?

Wrap Your SQL Head Around Riak MapReduce

Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.

Polyglot Persistence for Java Developers - Moving Out of the Relational Comfort Zone

Chris Richardson shows how he ported a relational database to three NoSQL data stores: Redis, Cassandra and MongoDB.

The Golden Circle – Why How What

Jean Tabaka challenges the audience to reflect on what Agile practices they are employing, how they are using them, ending with the questions “Why have their organization chosen to go Agile?

The Web Platform as a Limitless Pool of Innovation, with Andreas Gal

Andreas talks about the benefits of the Open Web and how it compares to proprietary stacks. He also talks about various projects that push the envelope like Boot to Gecko, Broadway and pdf.js.

Hadoop and NoSQLin a Big Data Environment

Ron Bodkin discusses early adoption of Hadoop, NoSQL and describes MapReduce and related libraries and Frameworks. Other topics include Hive, Pig, multi tenancy, and security in a big data environment

Spring and Platform Interoperability

Stephen Bohlen explains how Spring helps with interoperability between Java and .NET, demoing it with the help of a sample application.

How to Stop Writing Next Year's Unsustainable Piece of Code

Guilherme Silveira mentions some of the turning points in project development that may affect the quality of the code offering advice on avoiding writing crappy code.