Hi there
I was hoping I could get some help. I am not a business analyst, but I have been charged with documenting the the current business processes in our company. I have been reading extensively on all of the tools and mapping tools out there.
My problem is that these all seem to be for the purpose of leading to what a solution is and are all quite technical . We are in the position where we know we will be converting to new IT systems. What I have to do is document the current processes so that we can go to vendors from a position of knowledge on what our processes are ( they in turn are likely to do their own review). I do not need to go down to the granular level ( screen shots) as we will be buying an off the shelf solution with miminal tweaking intended. What I am tring to find is a template of questions that you should ask people what you are documenting the systems. I 'd like to have it as a prompt to me so that I can ensure I am gathering as much info as possible. It is not a case of having to familiarise myself with the business as I am already on staff and understand the business.
If someone could point me in a direction that would be great.
Thanks very much
Elaine
It's a tough ask to nail this in this forum. You should contact someone in your local area for some face to face advice. People will be happy to share.
But - think about this -
These are the fundamentals.
There are some drawing conventions in the BPMN standards which would be useful to follow, but stick to the basics and don't get hung up on standards. The diagrams shiouyld be able to explain themseleves.
Hi Elaine,
my suggestion would be to start by breaking up the business into the relevant departments - Buying, Marketing, Supply Chain, Logistics, Distribution, administration etc.
Then select from within each department person/s who are experts in that department and sit down with then to give you and overall breakdown of each activity, who is involved and how long each activity takes.
Approach it in a logical fashion - begining to end.
I'm always a little wary of "Off the shelf" applications as they do not always provide all the solutions and tweaking to suit the client usually takes time and money.
On top of that there are times when the financial cost of and the implimentation overrides the business needs and a business can end up with a "white elephant", inefficient processes and disgruntled employees who find way to "Work around" the system.
Hopes this helps. I can understand the need for a checklist to make sure all bases are covered and nothing is missed.
I think it is really hard to come up with a checklist which can at the end ensure that you have documented all the possible use cases.
If I have to do it, I might start with asking the users or myself (if I have all the domain knowledge) about the current Business Process and will try to model it so that I know the flow of the information. Once I have the pictorial view, I can easily describe all the inputs, any processing which I need to do base on the information and the desired output I will get.
Do note, If you are documenting your Legacy system and you want to suggest any change then you need to document AS-IS and TO-BE business models, this will help the vendors to actually know the required change and will eventually help you guys to quickly wrap up the work.
While modeling your business process, you can tag the processes or the transition between processes, this will help the readers to easily understand what is happening where. Let me know if you need any samples/help….
-- Riz
brought to you by enabling practitioners & organizations to achieve their goals using: