Comments on: Communicating a delivery schedule with use cases http://tynerblain.com/blog/2005/12/22/communicating-a-delivery-schedule-with-use-cases/ Software product success. Sun, 27 May 2012 14:59:31 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Agile Documentation | devblogging.com http://tynerblain.com/blog/2005/12/22/communicating-a-delivery-schedule-with-use-cases/comment-page-1/#comment-805052 Agile Documentation | devblogging.com Thu, 21 Jul 2011 02:36:16 +0000 http://tynerblain.com/blog/2005/12/22/communicating-a-delivery-schedule-with-use-cases/#comment-805052 [...] actors to thinking about personas is a small one.  This chart comes from an earlier article on communicating a delivery schedule with use cases – it helps stakeholders get a big picture view of who benefits when – a user-centric, [...] [...] actors to thinking about personas is a small one.  This chart comes from an earlier article on communicating a delivery schedule with use cases – it helps stakeholders get a big picture view of who benefits when – a user-centric, [...]

]]> By: Scott Sehlhorst http://tynerblain.com/blog/2005/12/22/communicating-a-delivery-schedule-with-use-cases/comment-page-1/#comment-445810 Scott Sehlhorst Wed, 08 Oct 2008 01:21:06 +0000 http://tynerblain.com/blog/2005/12/22/communicating-a-delivery-schedule-with-use-cases/#comment-445810 Build something that is built on top of a database. Build queries to meet specific goals. Best way to learn something like that is by doing. Good luck! Build something that is built on top of a database. Build queries to meet specific goals. Best way to learn something like that is by doing. Good luck!

]]> By: werutzb http://tynerblain.com/blog/2005/12/22/communicating-a-delivery-schedule-with-use-cases/comment-page-1/#comment-445799 werutzb Wed, 08 Oct 2008 00:46:16 +0000 http://tynerblain.com/blog/2005/12/22/communicating-a-delivery-schedule-with-use-cases/#comment-445799 Hi! I want to extend my SQL capabilities. I red so many SQL books and would like to read more about SQL for my work as db2 database manager. What can you recommend? Thanks, Werutz Hi!

I want to extend my SQL capabilities.
I red so many SQL books and would like to
read more about SQL for my work as db2 database manager.

What can you recommend?

Thanks,
Werutz

]]> By: Why incremental delivery is good -Tyner Blain http://tynerblain.com/blog/2005/12/22/communicating-a-delivery-schedule-with-use-cases/comment-page-1/#comment-202 Why incremental delivery is good -Tyner Blain Thu, 02 Feb 2006 05:33:30 +0000 http://tynerblain.com/blog/2005/12/22/communicating-a-delivery-schedule-with-use-cases/#comment-202 [...] [Ed: This was previously published as part of this other post from December 2005, but is being republished as a separate post ] [...] [...] [Ed: This was previously published as part of this other post from December 2005, but is being republished as a separate post ] [...]

]]> By: Tyner Blain » How to interview when gathering requirements http://tynerblain.com/blog/2005/12/22/communicating-a-delivery-schedule-with-use-cases/comment-page-1/#comment-95 Tyner Blain » How to interview when gathering requirements Sun, 15 Jan 2006 22:38:27 +0000 http://tynerblain.com/blog/2005/12/22/communicating-a-delivery-schedule-with-use-cases/#comment-95 [...] If we get stuck for a good pretense to having the conversation, we can always use communication of the schedule as an excuse. [...] [...] If we get stuck for a good pretense to having the conversation, we can always use communication of the schedule as an excuse. [...]

]]> By: Scott Sehlhorst http://tynerblain.com/blog/2005/12/22/communicating-a-delivery-schedule-with-use-cases/comment-page-1/#comment-34 Scott Sehlhorst Wed, 04 Jan 2006 08:14:54 +0000 http://tynerblain.com/blog/2005/12/22/communicating-a-delivery-schedule-with-use-cases/#comment-34 Roger L. Cauvin said, December 22, 2005 at 12:50 pm · Edit Good observation regarding features versus use cases. As you mention, users don’t care so much about features per se; they care about accomplishing their goals. Scheduling around use cases helps product developers keep their eyes on the ball (focus on what matters to the prospective customer). In many cases, use cases often aren’t sufficiently granular (nor should they be) for scheduling. Craig Larman recommends dividing use cases into versions in such cases. I touch on this approach here: http://cauvin.blogspot.com/2005/08/approaches-to-iterating.html An example is a Purchase Items use case. You can break it into versions as follows: Purchase Items (cash only, no receipt) Purchase Items (cash, receipt) Purchase Items (cash and check, receipt) Purchase Items (cash, check, credit, receipt) That way you’re delivering end-to-end value to the user after every version. Roger L. Cauvin said,

December 22, 2005 at 12:50 pm · Edit

Good observation regarding features versus use cases. As you mention, users don’t care so much about features per se; they care about accomplishing their goals. Scheduling around use cases helps product developers keep their eyes on the ball (focus on what matters to the prospective customer).

In many cases, use cases often aren’t sufficiently granular (nor should they be) for scheduling. Craig Larman recommends dividing use cases into versions in such cases. I touch on this approach here:

http://cauvin.blogspot.com/2005/08/approaches-to-iterating.html

An example is a Purchase Items use case. You can break it into versions as follows:

Purchase Items (cash only, no receipt)
Purchase Items (cash, receipt)
Purchase Items (cash and check, receipt)
Purchase Items (cash, check, credit, receipt)

That way you’re delivering end-to-end value to the user after every version.

]]> By: Tyner Blain » Use case series: UML 2.0 use case diagrams http://tynerblain.com/blog/2005/12/22/communicating-a-delivery-schedule-with-use-cases/comment-page-1/#comment-30 Tyner Blain » Use case series: UML 2.0 use case diagrams Wed, 04 Jan 2006 08:10:53 +0000 http://tynerblain.com/blog/2005/12/22/communicating-a-delivery-schedule-with-use-cases/#comment-30 [...] Knowing that we can’t answer all 4 questions with a single communication tool, here’s what we should do: (1&3) Create a matrix view of use cases versus actors to show which actors perform each use case, and when they will be available. [...] [...] Knowing that we can’t answer all 4 questions with a single communication tool, here’s what we should do: (1&3) Create a matrix view of use cases versus actors to show which actors perform each use case, and when they will be available. [...]

]]>