Comments for SpikesTogether http://blogs.spikes.be/bpm Towards the Information Worker Walhalla Fri, 18 May 2012 09:08:16 +0000 http://wordpress.org/?v=2.9.1 hourly 1 Comment on Ideas for a better Information Architecture with SharePoint (Part 1) by SpikesTogether » Ideas for a better Information Architecture with SharePoint (Part 3) http://blogs.spikes.be/bpm/?p=59&cpage=1#comment-34 SpikesTogether » Ideas for a better Information Architecture with SharePoint (Part 3) Fri, 18 May 2012 09:08:16 +0000 http://blogs.spikes.be/bpm/?p=59#comment-34 [...] Part 1: Every document has its process [...] [...] Part 1: Every document has its process [...]

]]> Comment on Ideas for a better Information Architecture with SharePoint (Part 1) by SpikesTogether » Ideas for a better Information Architecture with SharePoint (Part 4) http://blogs.spikes.be/bpm/?p=59&cpage=1#comment-33 SpikesTogether » Ideas for a better Information Architecture with SharePoint (Part 4) Fri, 18 May 2012 09:06:47 +0000 http://blogs.spikes.be/bpm/?p=59#comment-33 [...] Part 1: Every document has its process [...] [...] Part 1: Every document has its process [...]

]]> Comment on Ideas for a better Information Architecture with SharePoint (Intro) by SpikesTogether » Ideas for a better Information Architecture with SharePoint (Part 2) http://blogs.spikes.be/bpm/?p=56&cpage=1#comment-32 SpikesTogether » Ideas for a better Information Architecture with SharePoint (Part 2) Fri, 18 May 2012 09:04:56 +0000 http://blogs.spikes.be/bpm/?p=56#comment-32 [...] - Intro [...] [...] – Intro [...]

]]> Comment on Ideas for a better Information Architecture with SharePoint (Part 3) by SpikesTogether » Ideas for a better Information Architecture with SharePoint (Intro) http://blogs.spikes.be/bpm/?p=76&cpage=1#comment-31 SpikesTogether » Ideas for a better Information Architecture with SharePoint (Intro) Fri, 18 May 2012 09:02:59 +0000 http://blogs.spikes.be/bpm/?p=76#comment-31 [...] Read more details in Part 3 – Every document type has its author/audience pattern. [...] [...] Read more details in Part 3 – Every document type has its author/audience pattern. [...]

]]> Comment on Ideas for a better Information Architecture with SharePoint (Intro) by SpikesTogether » Ideas for a better Information Architecture with SharePoint (Part 1) http://blogs.spikes.be/bpm/?p=56&cpage=1#comment-30 SpikesTogether » Ideas for a better Information Architecture with SharePoint (Part 1) Fri, 18 May 2012 09:01:42 +0000 http://blogs.spikes.be/bpm/?p=56#comment-30 [...] - Intro [...] [...] – Intro [...]

]]> Comment on Ideas for a better Information Architecture with SharePoint (Intro) by SpikesTogether » Ideas for a better Information Architecture with SharePoint (Part 4) http://blogs.spikes.be/bpm/?p=56&cpage=1#comment-29 SpikesTogether » Ideas for a better Information Architecture with SharePoint (Part 4) Fri, 18 May 2012 09:01:13 +0000 http://blogs.spikes.be/bpm/?p=56#comment-29 [...] - Intro [...] [...] – Intro [...]

]]> Comment on Ideas for a better Information Architecture with SharePoint (Intro) by SpikesTogether » Ideas for a better Information Architecture with SharePoint (Part 3) http://blogs.spikes.be/bpm/?p=56&cpage=1#comment-28 SpikesTogether » Ideas for a better Information Architecture with SharePoint (Part 3) Fri, 18 May 2012 08:55:15 +0000 http://blogs.spikes.be/bpm/?p=56#comment-28 [...] - Intro [...] [...] – Intro [...]

]]> Comment on Ideas for a better Information Architecture with SharePoint (Part 2) by SpikesTogether » Ideas for a better Information Architecture with SharePoint (Intro) http://blogs.spikes.be/bpm/?p=72&cpage=1#comment-27 SpikesTogether » Ideas for a better Information Architecture with SharePoint (Intro) Mon, 14 May 2012 07:15:45 +0000 http://blogs.spikes.be/bpm/?p=72#comment-27 [...] Read more about workflow patterns in Part 2 – Every document type has its workflow pattern. [...] [...] Read more about workflow patterns in Part 2 – Every document type has its workflow pattern. [...]

]]> Comment on Ideas for a better Information Architecture with SharePoint (Part 1) by SpikesTogether » Ideas for a better Information Architecture with SharePoint (Intro) http://blogs.spikes.be/bpm/?p=59&cpage=1#comment-26 SpikesTogether » Ideas for a better Information Architecture with SharePoint (Intro) Thu, 03 May 2012 09:44:36 +0000 http://blogs.spikes.be/bpm/?p=59#comment-26 [...] Read more about types of documents in Part 1 – Every Document has its process. [...] [...] Read more about types of documents in Part 1 – Every Document has its process. [...]

]]> Comment on BPM is ‘Old School’: Adaptive Case Management is here to stay by Ronald Hermans http://blogs.spikes.be/bpm/?p=43&cpage=1#comment-18 Ronald Hermans Mon, 29 Aug 2011 11:51:49 +0000 http://blogs.spikes.be/bpm/?p=43#comment-18 Thanks for sharing your thoughts, Marc. By experience, think you're right ... Looking fw to your next post, very interested in how SharePoint can help. In that matter, I'm currently not overwelmed of the collaboration capabilities of SharePoint. - Ronald Thanks for sharing your thoughts, Marc. By experience, think you’re right … Looking fw to your next post, very interested in how SharePoint can help. In that matter, I’m currently not overwelmed of the collaboration capabilities of SharePoint. – Ronald

]]> Comment on Business Process Modeling: the Overview by Marc Vanderheyden http://blogs.spikes.be/bpm/?p=29&cpage=1#comment-14 Marc Vanderheyden Mon, 27 Jun 2011 06:10:33 +0000 http://blogs.spikes.be/bpm/?p=29#comment-14 Hello Jennifer, I thank you for your comment. You are right about the problem of managing a process model in different (MS Office) files. However, the combination of Visio and SharePoint does allow you to work in an integrated way. We store the process diagrams in Visio files in a SharePoint library and - and this is the main trick- we store the process objects that are used in the diagrams in SharePoint Lists, and then integrate them in the diagrams using the data link of Visio. (I will describe the details in a futur blog post.) The result: an integrated process model that uses SharePoint as its repository. At no additional license cost. Regards, Marc Hello Jennifer, I thank you for your comment. You are right about the problem of managing a process model in different (MS Office) files. However, the combination of Visio and SharePoint does allow you to work in an integrated way. We store the process diagrams in Visio files in a SharePoint library and – and this is the main trick- we store the process objects that are used in the diagrams in SharePoint Lists, and then integrate them in the diagrams using the data link of Visio. (I will describe the details in a futur blog post.) The result: an integrated process model that uses SharePoint as its repository. At no additional license cost.
Regards, Marc

]]> Comment on Business Process Modeling: the Overview by Jennifer Nolan http://blogs.spikes.be/bpm/?p=29&cpage=1#comment-13 Jennifer Nolan Sun, 26 Jun 2011 19:40:13 +0000 http://blogs.spikes.be/bpm/?p=29#comment-13 Hi, Thanks for a good blog post on a short intro to business process modeling. I completely agree with your suggestion that it is important to use levels to properly structure and show right amount of detail for the process models, most people end up creating one big flat model which is unwieldy and hard to understand. I also agree with that a process model is not just a drawing or a flowchart, but it should have documentation of rules and exception handling etc. as well. On the last point, we found that the different Microsoft tools (Word, PowerPoint and Visio) are not ideal for fully documenting processes because you end up having different information of a model in different documents and that does not lend itself to collaboration and versioning. We have been using the AccuProcess Modeler product over the last year and our team has found it to be very easy and effective business process modeling tool. It also includes process simulation for process analysis. They also offer a free version. You can download an try it at: http://www.accuprocess.com Thank you, regards, - Jennifer N Hi,

Thanks for a good blog post on a short intro to business process modeling. I completely agree with your suggestion that it is important to use levels to properly structure and show right amount of detail for the process models, most people end up creating one big flat model which is unwieldy and hard to understand. I also agree with that a process model is not just a drawing or a flowchart, but it should have documentation of rules and exception handling etc. as well.

On the last point, we found that the different Microsoft tools (Word, PowerPoint and Visio) are not ideal for fully documenting processes because you end up having different information of a model in different documents and that does not lend itself to collaboration and versioning. We have been using the AccuProcess Modeler product over the last year and our team has found it to be very easy and effective business process modeling tool. It also includes process simulation for process analysis.

They also offer a free version. You can download an try it at: http://www.accuprocess.com

Thank you, regards,

- Jennifer N

]]>