• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (8)

1 localhost commented Trackback

Scott,as usual great article. I always start projects using the above approach. However I find it takes me a little bit more than a couple of weeks to get things done.

Usually a month to two months sounds about right for big projects. But this is usually because of the logistics of getting everyone together has to be taken into account. Clients typically want things polished and in electronic form regardless of team distribution, so that takes a bit of time as well.
I'm surprised you didn't mention building some form of high-level domain model, I find that just focusing on processes and functions leads to a somewhat anemic understanding of the solution.
I typically complement the models you have described for this envisioning stage with a domain model developed using techniques like those described by <a href='http://domaindrivendesign.org/'> domain driven design </a>.
To make it accessible, I frequently use collaborative modeling techniques that you have suggested such as <a href='http://www.agilemodeling.com/artifacts/crcModel.htm'> CRC cards </a>.
And I have found that they have been <a href='http://agileconsulting.blogspot.com/2008/02/crc-cards-incredibly-successful-so-far.html'> incredibly successful </a>.

2 localhost commented Permalink

Good catch. Domain models are critical (for business apps at least) for initial modeling. I've updated the post to include them in the list.<div>&nbsp;</div> Logistical problems, which I referenced, can stretch out the initial modeling time. That happens a lot, but those are problems that you could choose to overcome if you really want to. I typically point out the opportunity cost of not getting the right people together and usually the customer makes it happen.<div>&nbsp;</div> I don't count writing pretty PPT slide decks, nice documents, ... as modeling time. That's political and static specification effort which I would account for separately (and thereby making polishing explicit and likely to be questioned).<div>&nbsp;</div> - Scott

3 localhost commented Trackback

Your posts are great and I always admire them. One thing I noticed that we know agile is great but we dont know when it is feasible. I am long using Model Driven development and Agile only where needed. I suggest that we should always have some comparitive study befor adapting any methodology. I tried to delve into this in my recent post @ http://www.geekscafe.net/ under Design/Model Driven Development (DDD) or Test Driven Development (TDD).<div>&nbsp;</div> Any suggestion / comments are appreciated.<div>&nbsp;</div> Shams

4 williamfitzstephen commented Permalink

Really an informative blog post i collect very valuable and informative information.<a href="http://www.easyessayhelp.com" rel="nofollow">Get Essay Help</a>|<a href="http://www.easyessayhelp.com/research-paper.php">Research Paper Help Online</a>

5 AllanPerry commented Permalink

I agree, good stuff. <a href="http://www.rapidwriters.net/">Essay Writing</a> | <a href="http://thecoastal-life.com/">WIND INFO</a>

Add a Comment Add a Comment