Discussions

News: Be Agile: Doing just enough initial modeling up front

  1. In his October 9th article entitled Disciplined Agile Architecture: Initial Architecture Envisioning, Scott Ambler discusses the mistakes Agile teams often make when they do their initial, up front modeling. The mistake? It seems to be all of that modeling they’re doing.

    "Some architects mistakenly believe that you need to do detailed up front modeling,” says Ambler in his post. "This not only isn’t true it also proves to be quite risky in practice,” he says, pointing to an earlier article he wrote about Big Modeling Up Front (BMUF).

    Most application developers are pretty comfortable with the YAGNI (You Ain't Gonna Need It) philosophy that stops us from building all of those methods and components that we think we might need. When it comes to documentation and writing up modeling documents, the corresponding acronym is TAGRI, or They Ain't Gonna Read It. Often big modeling diagrams fall into that same category.

    It's good advice. Do what you need, but don't do more than you need. What good is doing more than you need to do, especially when it comes to up front models and documentation.

    Disciplined Agile Architecture: Initial Architecture Envisioning, Scott Ambler

     

  2. Any evidence?[ Go to top ]

    Or is it just some random advice?

  3. Cam anyone point to any significant non-trivial or enterprise systems Scott Ambler has designed?