Hi,
This is my first post (and first visit to this site, although definitely not my last... it looks really useful). I have just started in a new job and have come into a project partway through. A lot of the analysis has already been completed, but I have been tasked with preparing end to end process models. That's fine (I think), but I've also been asked to prepare operational models, both current and target. Really not too sure where to start with this, especially as I have been asked not to bother the business users unless absolutely necessary (apparently they're "workshop-ed out"!
I've tried searching on the internet, but there doesn't seem to be much in the way of a standard to follow... any help please?
Thanks
Hi:
You are being asked to do what should have been done up-front - so the project may not be as far along as you were told. More than once I have come onboard a largely or almost done requirements project only to have to throw all or most the previous work away. If you have been told to have minimal contact with the end-users, I would bet that the project is in trouble.
The "as-is" model is the major part of what you need to do. And that requires alot of end-user contact.
For large-scale end-to-end "as-is" modeling efforts I say to use data flow diagrams. They alone make "holes" in your analysis glaringly obvious. They are the only techniques that employes a lithmus test of completedness. Remember that analysis is about discovery and therefore, you want a technique that best supports that.
Tony
What Tony says is potentially true. You must have the access to the business as you require it. Otherwise your work will be counter productive.
Also designing the operating model usually comes before designing future business processes. However, it may be the case that your business process models are of the current state of the organization.
Regardless of these risks, I expect you want to get some information about how to put together an operating model.
You are right - there is no solid consensus in the industry on how to do this. In fact there are several views of what an operating model is.
A couple of key concepts that people often labeled as or related to operating models are;
I hope this helps.
Craig Brown
www.betterprojects.net
Thanks for both posts... some useful starting points. Fully take on board the comments about access to the business and am trying with a little success! The project has bought in a new system, so in terms of the system implementation, they are quite advanced. But they have focussed on that rather than processes so far... still gives me something to do now I'm here!
Thanks again!
Our experience might assist you to get some more "engagement" with your user community. Tools available for discovery and documentation of the "as-is" position, are typically complex and do not invite engagement. Give your user community each a copy of Visio , ask them to document their as-is processes and see what happens. Visio is complex enough to the uninitiated and does not lend itself to a simple, easy-to-use collaborative tool. The success of "as-is" discovery goes around the ability to 1) Engage , 2) collect data in a common format, 3) Be able to use the data as an output from the discovery and documentation tool for further collaboration towards ongoing optimisation.
A new tool called Process Master does enable all of the above. The simple text based system with automatic diagram presentation is flexible easy to use and the output in XML can connect to various analysis suites. Does round-trip connectivity with the likes of Aris, Tibco, FlowCentric and other automated workflow tools. Give it a try, it only costs $299 per copy or try a free download www.processmaster.com
Hope this helps
brought to you by enabling practitioners & organizations to achieve their goals using: