Comments on: Agile Development of Use Cases http://tynerblain.com/blog/2007/04/02/agile-development-of-use-cases/ Software product success. Sun, 12 Feb 2012 19:10:25 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Scott Sehlhorst http://tynerblain.com/blog/2007/04/02/agile-development-of-use-cases/comment-page-1/#comment-85714 Scott Sehlhorst Wed, 04 Apr 2007 00:24:51 +0000 http://tynerblain.com/blog/2007/04/02/agile-development-of-use-cases/#comment-85714 Thanks Levent! I appreciate very much your participation here, and I know our readers get a lot of value from your insights on agile (hint - check out Levent's blog). I'm convinced that the mythical "best" process involves combining ideas that have matured in agile, structured/BUF requirements disciplines, BPM, and interaction design. I hope you'll continue to help us mine each of these areas to find the gems that are hidden within. Thanks Levent! I appreciate very much your participation here, and I know our readers get a lot of value from your insights on agile (hint – check out Levent’s blog).

I’m convinced that the mythical “best” process involves combining ideas that have matured in agile, structured/BUF requirements disciplines, BPM, and interaction design. I hope you’ll continue to help us mine each of these areas to find the gems that are hidden within.

]]> By: Levent Gurses http://tynerblain.com/blog/2007/04/02/agile-development-of-use-cases/comment-page-1/#comment-85671 Levent Gurses Tue, 03 Apr 2007 18:27:50 +0000 http://tynerblain.com/blog/2007/04/02/agile-development-of-use-cases/#comment-85671 Really good stuff Scott! Many people in the Agile community are too fast to dismiss the use cases as they find them too structured and process-heavy. The part that most miss is the traceability that comes as a result of written requirements. In addition not all use cases have to be three pages long and capture all possibilities for a given context. You can take advantage of use cases and still be Agile. Really good stuff Scott! Many people in the Agile community are too fast to dismiss the use cases as they find them too structured and process-heavy. The part that most miss is the traceability that comes as a result of written requirements. In addition not all use cases have to be three pages long and capture all possibilities for a given context. You can take advantage of use cases and still be Agile.

]]>