这将是真正的umb,但在我多年帮助公司实现基于纸张的自动化进程时,首先要了解这一进程。 你们最有可能发现没有人理解整个事情。 你们需要发挥作用,抓住这一进程的诸多道路,让你领导这一进程。 一旦你提出调查结果,每个人都会感到惊讶,因为他们对这个复杂的问题没有想法。 利用这一机会进行精简。

启动一个中断的进程,只会使这一进程更快地重新进行,并告诉许多人。

就工具而言,我的经验令我看上去,但试图利用这些特性:

• EASY to change. You WILL be changing it. So don t hard-code anything.
• Possible revision control - changes to a process may or may not affect documents already in route?
• Visual workflow editing. Everyone wants this but they ll all ask you to drive it. Still, nice tools.

如果没有这种帮助,那么自动化进程的成功80%不是技术。

这略微脱离了专题,但相关的是,缺陷跟踪系统通常有工作流程发动机/状态。 (事实上,我想Joel或一些其他促进委员会雇员在利用FB管理最初的电子邮件和恢复程序方面做了一些事情)

我在提出任何编码或技术选择之前,就模拟工作流程提出其他建议。 你们也希望这样做具有灵活性。

正如N8owl提醒我们的那样,对一只肉类进行调节,会产生一个自动的肉类:,这不是一个改进。 许多纸面制系统已经发展到<>代号,可以相当多余和毫不掩饰。 有些人可能认为“带有形式”侵犯了他们的个人财产,因此看望你们的回馈。

1. model the workflow in terms of the forms used by whom in what roles for what purposes; this documents the current process as a baseline. Get estimates of how long each step takes, both in terms of man-hours and calendar time
2. understand the workflow in terms of the information gathered, generated, and transmitted
3. consolidate the information on the forms into a new set of forms for minimal workflow
4. be prepared to be told "This is the way we ve always done it and we re not going to change", and to gently (a) validate their feelings, (b) explain how less work is more efficient, and (c) show concrete benefits [vs.the baseline from step 1]
5. soft-code when possible; use processing rules when possible; web services and html forms (esp. w/jquery) will go a long way if you have an intranet
6. beware of canned packages (including sharepoint) unless you are absolutely certain they encompass your organization s current and future needs

good!

页: 1

我在此发现,对于基于工作流程的方法,有一种一般的谨慎态度,必须达成一致。 请注意:,大多数工作流程技术都牺牲了灵活性。