Comments on: Estimating the Effort of Documenting an As-Is Process http://tynerblain.com/blog/2006/09/28/estimating-as-is/ Software product success. Thu, 18 Mar 2010 20:39:50 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Scott Sehlhorst http://tynerblain.com/blog/2006/09/28/estimating-as-is/comment-page-1/#comment-55594 Scott Sehlhorst Wed, 18 Oct 2006 04:50:02 +0000 http://tynerblain.com/blog/2006/09/28/estimating-as-is/#comment-55594 Soumya, thanks for reading and for commenting! I appreciate the feedback, and agree that the "ride alongs" are a great idea! Soumya, thanks for reading and for commenting!

I appreciate the feedback, and agree that the “ride alongs” are a great idea!

]]> By: Soumya http://tynerblain.com/blog/2006/09/28/estimating-as-is/comment-page-1/#comment-55591 Soumya Wed, 18 Oct 2006 04:36:23 +0000 http://tynerblain.com/blog/2006/09/28/estimating-as-is/#comment-55591 Good stuff. I particularly liked the "One Size Does NOT Fit All" points. I also agree with Roger's suggestion of conducting contextual interviews. I've found them to be immensely valuable, more so when I had limited prior exposure to the domain being studied or when the process holder could not spare enough time away from desk for me (like in a contact center). Good stuff. I particularly liked the “One Size Does NOT Fit All” points. I also agree with Roger’s suggestion of conducting contextual interviews. I’ve found them to be immensely valuable, more so when I had limited prior exposure to the domain being studied or when the process holder could not spare enough time away from desk for me (like in a contact center).

]]> By: Scott Sehlhorst http://tynerblain.com/blog/2006/09/28/estimating-as-is/comment-page-1/#comment-55254 Scott Sehlhorst Fri, 29 Sep 2006 19:13:46 +0000 http://tynerblain.com/blog/2006/09/28/estimating-as-is/#comment-55254 Hey thanks, Bruce, and welcome aboard! Folks should check out Bruce's blog - BPMS Watch - he knows a whole lot more about BPM (and BPMN) than we do - one of the folks we're trying to learn from. Hey thanks, Bruce, and welcome aboard!

Folks should check out Bruce’s blog – BPMS Watch – he knows a whole lot more about BPM (and BPMN) than we do – one of the folks we’re trying to learn from.

]]> By: Bruce Silver http://tynerblain.com/blog/2006/09/28/estimating-as-is/comment-page-1/#comment-55252 Bruce Silver Fri, 29 Sep 2006 16:01:48 +0000 http://tynerblain.com/blog/2006/09/28/estimating-as-is/#comment-55252 Scott, Great information, very helpful. --Bruce Scott,
Great information, very helpful.
–Bruce

]]> By: Scott Sehlhorst http://tynerblain.com/blog/2006/09/28/estimating-as-is/comment-page-1/#comment-55249 Scott Sehlhorst Fri, 29 Sep 2006 14:04:30 +0000 http://tynerblain.com/blog/2006/09/28/estimating-as-is/#comment-55249 Great point Roger. Shadowing is a great elicitation technique. When we have time available in the schedule (we often are faced with a top-down scope/deadline in advance of doing a bottoms-up estimate), we should definitely take advantage of it. This is especially helpful when we lack domain expertise. I would classify this as part of the "Initial SME Interview", and add time to allow for it - as the benefit is not just observation but asking the questions that are prompted by the SME's actions. To estimate, double or triple the amount of time the SME would spend doing the process if you weren't interrupting her. Collecting artifacts from the process helps also (generated reports, screenshots, working documents (excel spreadsheets), generated correspondence, documented procedures, training manuals, etc). Great point Roger. Shadowing is a great elicitation technique. When we have time available in the schedule (we often are faced with a top-down scope/deadline in advance of doing a bottoms-up estimate), we should definitely take advantage of it. This is especially helpful when we lack domain expertise.

I would classify this as part of the “Initial SME Interview”, and add time to allow for it – as the benefit is not just observation but asking the questions that are prompted by the SME’s actions. To estimate, double or triple the amount of time the SME would spend doing the process if you weren’t interrupting her.

Collecting artifacts from the process helps also (generated reports, screenshots, working documents (excel spreadsheets), generated correspondence, documented procedures, training manuals, etc).

]]> By: Roger L. Cauvin http://tynerblain.com/blog/2006/09/28/estimating-as-is/comment-page-1/#comment-55248 Roger L. Cauvin Fri, 29 Sep 2006 13:52:31 +0000 http://tynerblain.com/blog/2006/09/28/estimating-as-is/#comment-55248 I believe an essential step is to observe, first-hand, the processes you're documenting. If you can actually <i>participate</i> in the process, it's even better. Insist that your client let you do some <a href="http://cauvin.blogspot.com/2005/08/ethnography.html" rel="nofollow">ethnographic research</a>. Unfortunately, too many companies are looking for a glorified documentation specialist, not a true product manager or requirements analyst. In such cases, the SME gets to do the most important part of your job. I believe an essential step is to observe, first-hand, the processes you’re documenting. If you can actually participate in the process, it’s even better. Insist that your client let you do some ethnographic research.

Unfortunately, too many companies are looking for a glorified documentation specialist, not a true product manager or requirements analyst. In such cases, the SME gets to do the most important part of your job.

]]>