知识卡片
划清工具声誉的边界
庞大定制应用即使只含少量流程,也可能被统称为某工作流工具项目。若整体应用延期、超支或取消,组织容易把原因归给引擎,损害后续采用。推广时应说明流程自动化实际承担的范围,并将项目复杂性与工具责任分别评价;否则无关失败会成为错误的选型证据。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 引入流程自动化的旅程 · 查看原书依据
While this is not a problem, it comes with a risk. If customers build huge bespoke applications, it can take a lot of time before they are actually put it into production. This kind of project tends to get very expensive, or might even be canceled due to too many problems in the implementation. These
参考来源
- 位置:《Practical Process Automation》第12章《引入流程自动化的旅程》(来源项目:book-sources;源文件:extracted/Practical Process Automation (Bernd Ruecker)/_epub-src/OEBPS/ch12.xhtml)
- 结论依据:原文指出巨大定制应用整体被称为厂商项目时,其失败会伤害流程自动化声誉。
- 原始内容:While this is not a problem, it comes with a risk. If customers build huge bespoke applications, it can take a lot of time before they are actually put it into production. This kind of project tends to get very expensive, or might even be canceled due to too many problems in the implementation. These