Comments on: A Victory for “Barely Good Enough” Use Cases http://mittechnical.com/BOSTON-SEO-WORDPRESS/a-victory-for-barely-good-enough-use-cases/2007 Project Management, Systems Analysis, Semantic Web, SEO, and Whatever Else... Tue, 06 Jan 2009 06:49:47 +0000 http://wordpress.org/?v=2.6.2 By: Agile vs. agile versus Versus | Blog of a Boston-based IT Consultant http://mittechnical.com/BOSTON-SEO-WORDPRESS/a-victory-for-barely-good-enough-use-cases/2007#comment-3080 Agile vs. agile versus Versus | Blog of a Boston-based IT Consultant Wed, 12 Nov 2008 20:41:03 +0000 http://mittechnical.com/BOSTON-SEO-WORDPRESS/a-victory-for-barely-good-enough-use-cases/2007#comment-3080 [...] Barely Good Enough (see previous posts) is not insightful. I realized this suddenly, while thinking of how insightful it is. It is a cool [...] [...] Barely Good Enough (see previous posts) is not insightful. I realized this suddenly, while thinking of how insightful it is. It is a cool [...]

]]> By: Agile Up Front Requirements : Blog of a Boston-based IT Consultant http://mittechnical.com/BOSTON-SEO-WORDPRESS/a-victory-for-barely-good-enough-use-cases/2007#comment-2791 Agile Up Front Requirements : Blog of a Boston-based IT Consultant Thu, 01 May 2008 23:44:44 +0000 http://mittechnical.com/BOSTON-SEO-WORDPRESS/a-victory-for-barely-good-enough-use-cases/2007#comment-2791 [...] Requirements will serve to give you an estimate and a rough scope - as rough as you decide is Barely Good Enough. And then you scrum away, allocate from your backlog, and change direction when required like a UFO [...] [...] Requirements will serve to give you an estimate and a rough scope - as rough as you decide is Barely Good Enough. And then you scrum away, allocate from your backlog, and change direction when required like a UFO [...]

]]> By: Josh http://mittechnical.com/BOSTON-SEO-WORDPRESS/a-victory-for-barely-good-enough-use-cases/2007#comment-21 Josh Mon, 23 Jul 2007 23:32:34 +0000 http://mittechnical.com/BOSTON-SEO-WORDPRESS/a-victory-for-barely-good-enough-use-cases/2007#comment-21 Hey Scott, I like what you say very much. Thanks for the comment. I don't know why I am such a stickler about Use Cases, but I agree with you: Use Cases with design elements = *unacceptable* Use Cases. J Hey Scott,

I like what you say very much. Thanks for the comment. I don’t know why I am such a stickler about Use Cases, but I agree with you: Use Cases with design elements = *unacceptable* Use Cases.

J

]]> By: Scott Sehlhorst http://mittechnical.com/BOSTON-SEO-WORDPRESS/a-victory-for-barely-good-enough-use-cases/2007#comment-20 Scott Sehlhorst Mon, 23 Jul 2007 16:36:46 +0000 http://mittechnical.com/BOSTON-SEO-WORDPRESS/a-victory-for-barely-good-enough-use-cases/2007#comment-20 Hey Josh, Great representation of exactly how use cases can be mis-used. Including implementation cues in the use case is a bad thing(tm). It is one of the most common blunders. Sorry your team had to go through the pain of it, and glad you made progress in convincing them the error of their ways. For what its worth, I wouldn't say that excluding the design elements yields a "barely good enough" use case - I would say that including the design elements yields an unacceptable use case. Hey Josh,

Great representation of exactly how use cases can be mis-used. Including implementation cues in the use case is a bad thing(tm). It is one of the most common blunders. Sorry your team had to go through the pain of it, and glad you made progress in convincing them the error of their ways.

For what its worth, I wouldn’t say that excluding the design elements yields a “barely good enough” use case - I would say that including the design elements yields an unacceptable use case.

]]>