Comments on: Role Storming http://lostechies.com/joeocampo/2008/10/29/role-storming/ Tales from the field... Sat, 11 Feb 2012 08:43:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Tobin Harris http://lostechies.com/joeocampo/2008/10/29/role-storming/#comment-493 Tobin Harris Mon, 03 Nov 2008 09:20:16 +0000 /blogs/joe_ocampo/archive/2008/10/28/role-storming.aspx#comment-493 @Joe I wasn't clear in my comment - I was saying I like the fact you said you focus on listening: "Let the customer do most of the talking." That means you're doing more listening thank talking, which is really important IMHO :) I've found these user-task lists very useful for scoping out small projects too. @Joe

I wasn’t clear in my comment – I was saying I like the fact you said you focus on listening:

“Let the customer do most of the talking.”

That means you’re doing more listening thank talking, which is really important IMHO :)

I’ve found these user-task lists very useful for scoping out small projects too.

]]> By: Scott Sehlhorst http://lostechies.com/joeocampo/2008/10/29/role-storming/#comment-492 Scott Sehlhorst Sat, 01 Nov 2008 16:00:05 +0000 /blogs/joe_ocampo/archive/2008/10/28/role-storming.aspx#comment-492 Great stuff. I think the key 'how to make it work' advice is to not dive deep during this elicitation session. Personally, I struggle with that. Diving deep matters, it just needs to be deferred. I think about domain discovery / scoping as a "broad and deep" exercise - first, go broad across everything, then go deep on one thing. Imagine surveying for a drilling operation. You survey all of the available land, then pick the most promising spot and start drilling. Then the next most promising. This is a great way to organize those survey results. In enterprise projects, I'm often dealing with SMEs from distinctly different areas of the company, who don't know anything about the other areas of the company. They are focused on specific areas (like channel versus retail, or finance versus manufacturing). This is a great approach to allow the SMEs to get a shallow understanding of what happens in the other areas of the business, and how their silos work together in the bigger picture. Great stuff. I think the key ‘how to make it work’ advice is to not dive deep during this elicitation session. Personally, I struggle with that. Diving deep matters, it just needs to be deferred. I think about domain discovery / scoping as a “broad and deep” exercise – first, go broad across everything, then go deep on one thing. Imagine surveying for a drilling operation. You survey all of the available land, then pick the most promising spot and start drilling. Then the next most promising.

This is a great way to organize those survey results.

In enterprise projects, I’m often dealing with SMEs from distinctly different areas of the company, who don’t know anything about the other areas of the company. They are focused on specific areas (like channel versus retail, or finance versus manufacturing). This is a great approach to allow the SMEs to get a shallow understanding of what happens in the other areas of the business, and how their silos work together in the bigger picture.

]]> By: Joe Ocampo http://lostechies.com/joeocampo/2008/10/29/role-storming/#comment-491 Joe Ocampo Wed, 29 Oct 2008 11:24:03 +0000 /blogs/joe_ocampo/archive/2008/10/28/role-storming.aspx#comment-491 @Tobin I tool like to *listen* to the customer but I usually employ these mechanism when I have a room full of 10+ SME's in the room are large enterprise Agile projects. If it were just 1 - 4 people I would do what do you do and just listen. @Tobin

I tool like to *listen* to the customer but I usually employ these mechanism when I have a room full of 10+ SME’s in the room are large enterprise Agile projects. If it were just 1 – 4 people I would do what do you do and just listen.

]]> By: Tobin Harris http://lostechies.com/joeocampo/2008/10/29/role-storming/#comment-490 Tobin Harris Wed, 29 Oct 2008 08:17:37 +0000 /blogs/joe_ocampo/archive/2008/10/28/role-storming.aspx#comment-490 That's cool. I like the focus on *listening* to the customer :) This is also very similar to the user-task list that Alistair Cockburn talks about in "Writing Effective Use Cases". The user task list isn't the same as use-cases, it's early brainstorming for who can do what (identifying roles and goals!). Role-storming - nice name :) That’s cool. I like the focus on *listening* to the customer :)

This is also very similar to the user-task list that Alistair Cockburn talks about in “Writing Effective Use Cases”. The user task list isn’t the same as use-cases, it’s early brainstorming for who can do what (identifying roles and goals!).

Role-storming – nice name :)

]]>