Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Business Proces...  Documenting Improvements and impediments during as-is mapping
Previous Previous
 
Next Next
New Post 6/21/2017 7:19 AM
User is offline Slojo
1 posts
No Ranking


Documenting Improvements and impediments during as-is mapping 

I have been working on producing As-Is business process documentation and have gathered some valuable insights along the way while discovering the ways that users interact with the system.  These will be valuable inputs to the To-Be process, however  that will be treated as a separate phase of the project, initiated at a later date.

My question is, how do we collect and document the inhibitors and process improvement suggestions during the As-Is phase?  The Business Process document does not feel like the right place, would you manage these as change requests, another document, or a section within the As-Is document?

Any suggestions or ideas would be much appreciated.

Slojo

 
New Post 7/9/2017 10:09 AM
User is offline Adrian M.
722 posts
3rd Level Poster




Hi SRe: Documenting Improvements and impediments during as-is mapping 

Hi Slojo,

They should definitely be separate from the as-is business process documentation.  It sounds like you are in need of a backlog of potential improvements/changes/requests.  Think of a it as a wish list.

My suggestion is that these should be tracked in a list format so that your list can be sorted, prioritized, searched.

Think about some of the metadata (aka columns) you might want to track for each item in the wish list such as:

* Title

* Summary/Description

* Rationale (what problem you are solving or what opportunity you are addressing)

* Source/Sponsor (the name of the one who requested/discovered it)

* Reference to existing process (here you can link/reference to the as-is process you are documenting and which relates to the line item in context)

* Priority

* Relative Complexity

* Disposition/Status

* etc.

Let us know what you end up using and how it worked for you.

Adrian


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 
New Post 7/14/2017 3:40 AM
User is offline Kimbo
422 posts
5th Level Poster


Re: Documenting Improvements and impediments during as-is mapping 

Hi Slojo

 

I've just finished doing exactly that in my current contract. 

 

Just have an appendix in your AsIs document. Put it all in there. I capture most of that stuff under 'pain points'. Feeds into the ToBe nicely. You can get fancy as Adrian suggests if you like but I personally think that's overkill.

 

 

Kimbo

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Business Proces...  Documenting Improvements and impediments during as-is mapping

Community Blog - Latest Posts

EA Learning
EA Learning
I recently walked into a large shopping centre on a mission to buy a christening present for a friends son. I was very clear on what I wanted I just needed to find it… I was on my lunch break so I need to get the job done as I had a meeting that I needed to attend back in the office straight after lunch! I am not a frequent shopper and to b...
0 Responses
BusinessAnalysisHub
BusinessAnalysisHub
Have you woken up in the middle of night thinking how am I going to steer my team, give them the direction that they need but at the same time not constraint in what they want to build/deliver. I recently went through one of these night- I have joined an interesting project where we have very tight timescale to deliver a tech product to operational...
0 Responses
Peter
Peter
If you are building a reusable Security Product tool to specifically address Security Technical Implementation Guide (STIG)  Findings, should the requirements be considered Non Functional Requirements or Functional Requirements? For example if there are a number of STIGs such as: The minimum password length shall be 15 characters ...
1 Responses


Upcoming Live Webinars



Latest Articles

The Elevator Speech... for the BA
Nov 12, 2017
2 Comments
A BA walks into an elevator, is joined by an executive, and suddenly the executive asks the BA, “So, what are you working on these days?” ...
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC