4 ms·

While this has its points there is something missing. Why were Tim's (and his group's) projects failing before they sdopted MDD? Were many of them new at the c

• sparkslabs 12y ago
  In the story as given, it says many of Tim's projects etc failed before they adopted MDD. What happened was Tim changed to being a manager (after 15 years dev experience) and formed a new team and adopted MDD. They then attributed to MDD the success, when in fact the success was due to people. This point is emphasised again later when he finds a new team in his org when MDD is failing. That team has a new manager (with 15 years dev experience), working with a new team and a new methodology QDD. Again, the team attributes success to QDD, not the people. ie the success is down to people, not the process. If you realise MDD (and QDD) is completely made up, that will probably explain things somewhat. Also subsitute MDD with Agile, and realise that Agile was created under similar circumstances and you'll probably get the point. :-)