首页> 外文会议>Systems engineering: managing complexity and change >10 Pitfalls of System Process Development with Avoidance Solutions
【24h】

10 Pitfalls of System Process Development with Avoidance Solutions

机译:使用避免解决方案进行系统过程开发的10大误区

获取原文
获取原文并翻译 | 示例

摘要

Process literature has provided excellent guidance on what to include when writingrnnew process descriptions, but very little has stated clearly what actions must be taken byrncompanies during the course of developing usable, integrated processes. Countless hours havernand are being spent on development of company processes, which end up sitting on shelves inrntheir unopened, shrink-wrapped notebooks, or archived to sparsely accessed and often ignoredrninternal web sites. Management assumes the processes must not be the right ones, or personnelrnwould joyfully use them. The result is yet another extensive effort to “get it right” by re-writingrnthe processes with a different slant. Why is it that processes are not well received or utilized byrnsome companies, yet others embrace process with open arms? This paper explores the author’srnexperienced pitfalls of integrated, system process development at an organizational level,rnwhether that translates to a program, division, or enterprise level, and offers avoidance solutionsrnto help remedy the maladies. This paper is intended to provide solutions to circumvent therncommon maladies associated with process development and process improvement.
机译:流程文献为编写新的流程说明时要包括的内容提供了极好的指导,但是很少有人明确说明公司在开发可用的集成流程时必须采取哪些措施。花费了无数时间来开发公司流程,最终导致公司流程停在架子上,这些架子是未打开的,收缩包装的笔记本,或者归档到内部网站上经常访问且经常被忽略的地方。管理层认为流程一定不是正确的流程,否则工作人员会乐于使用它们。结果是通过以不同的角度重写流程的“正确解决”的另一项广泛努力。为什么有些公司没有很好地接受或利用流程,而其他公司却怀着开放的态度拥抱流程?本文探讨了作者在组织级别进行集成,系统过程开发时遇到的陷阱,无论是转换为程序级别,部门级别还是企业级别,并提供了避免方法来帮助纠正疾病。本文旨在提供解决与过程开发和过程改进相关的常见疾病的解决方案。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号