首页> 外文会议>IEEE International Conference on Global Software Engineering >Doing Scrum Rather Than Being Agile: A Case Study on Actual Nearshoring Practices
【24h】

Doing Scrum Rather Than Being Agile: A Case Study on Actual Nearshoring Practices

机译:做敏捷而不是敏捷:以实际的近岸实践为例

获取原文

摘要

Previous research in the field of Agile Distributed Software Development often focused on the a synchronicity of working hours due to different time zones, as if this was the only risk when developing software in non-co-located environments. This case study reflects a near shoring setting in which this primary impediment does not exist and investigates a broader range of risks now standing out more clearly. We observed two Polish Scrum teams working for a German company, which has been successfully applying Agile Methods for over four years. We present the actual process and practices of the external teams and contrast them to the intended way of proceeding. Main result: Agile near shoring is feasible and may produce high satisfaction amongst Product Owners, but this satisfaction might be delusive if process deviations due to misunderstandings of what Agile development means go unnoticed.
机译:先前在敏捷分布式软件开发领域的研究通常将重点放在由于不同时区而导致的工作时间同步上,这似乎是在非同一地点环境中开发软件时的唯一风险。本案例研究反映了这种主要障碍不存在的近乎支撑的情况,并调查了目前更加清楚地表明的更大范围的风险。我们观察到两个波兰Scrum团队在一家德国公司工作,该公司已经成功应用敏捷方法四年了。我们介绍了外部团队的实际流程和实践,并将它们与预期的进行方式进行了对比。主要结果:敏捷的接近支撑是可行的,并且可能在产品负责人中产生很高的满意度,但是,如果由于对敏捷开发方法的误解而导致的流程偏差没有引起注意,这种满意度可能是一种欺骗。

著录项

相似文献

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

客服邮箱:kefu@zhangqiaokeyan.com

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

  • 服务号