首页> 外文会议>Annual Pacific northwest software quality conference >Does DAD Know Best, Is it Better to do LeSS or Just be SAFe? Adapting Scaling Agile Practices into the Enterprise
【24h】

Does DAD Know Best, Is it Better to do LeSS or Just be SAFe? Adapting Scaling Agile Practices into the Enterprise

机译:DAD知道得最好吗,做LeSS还是SAFE更好?适应企业的扩展敏捷实践

获取原文

摘要

Organizations, large and small, that are experimenting and succeeding in using agile practices at team level, face their next challenge in scaling these practices across the enterprise. This challenge can come from expanding pilot programs from handful of teams to more teams; or, it comes from agile teams working with non-agile parts of the organization. The process inevitably creates confusion as teams employing different methods interface with each other. Introduction of agile practices challenges existing structures and practices, and brings forth questions regarding traditional roles, responsibilities and expectations. Should an organization continue to hone team level practices or should it try to extend agile practices to other parts of the organization? Are there large scale practices that work in easing the interaction between agile teams, and other non-agile, semi-agile business units? While scaling, can an organization get too process heavy and risk losing the original intent of transitioning to agile practices? There are primarily three scaling frameworks that try to address scaling agile practices: Disciplined Agile Delivery (DAD), Large-Scale Scrum (LeSS), and Scaled Agile Framework (SAFe). Each of these frameworks draws from variety of agile and lean practices. However, an organization's context matters most in deciding whether to embrace particular framework or only select practices to obtain desired results. In most cases, an organization has to make informed, pragmatic choices and experiment with various practices in order to address its specific needs without losing sight of why it embarked on an agile transition and transformation journey in the first place. Cambia Health Solutions has for over three years rolled out Scrum and other agile practices across more than 40 development oriented teams. We also keep apprise of scaling models and newer practices to better understand our own implementation. For Cambia, scaling practices, articulated in scaling frameworks, such as enterprise-wide synchronized Sprints, multi-program Quarterly Release Planning, Scrum of Scrums and Communities of Practices, have been effective in organizing our work. Many of these practices can prove useful not only to larger enterprises like Cambia, but also to smaller ones, who are looking to improve and refine their adaption of agile practices.
机译:在团队级别上尝试并成功使用敏捷实践的大小型组织,都面临着在企业范围内扩展这些实践的下一个挑战。挑战可能来自将试点计划从几个团队扩展到更多团队。或者,它来自与组织的非敏捷部门一起工作的敏捷团队。当采用不同方法的团队相互交互时,该过程不可避免地会造成混乱。引入敏捷实践挑战了现有的结构和实践,并提出了有关传统角色,责任和期望的问题。组织应该继续磨练团队级别的实践,还是应该尝试将敏捷实践扩展到组织的其他部门?是否存在大规模的实践来简化敏捷团队与其他非敏捷,半敏捷业务部门之间的交互?在扩展的同时,组织是否会变得过于繁重,并冒失去过渡到敏捷实践的初衷的风险?主要有三种扩展框架试图解决扩展敏捷实践:纪律敏捷交付(DAD),大规模Scrum(LeSS)和扩展敏捷框架(SAFe)。每个框架都来自各种敏捷和精益实践。但是,组织的环境在决定是采用特定框架还是仅选择实践来获得期望的结果时最重要。在大多数情况下,组织必须做出明智的,务实的选择,并尝试各种实践,以解决其特定需求,而又不会忘记为什么首先要进行敏捷过渡和转型的原因。 Cambia Health Solutions已在40多个面向开发团队的团队中推广了Scrum和其他敏捷实践。我们还不断提出扩展模型和更新的实践方法,以更好地了解我们自己的实现。对于Cambia而言,扩展框架中阐明的扩展实践(例如企业范围的同步Sprint,多程序季度发布计划,Scrum的Scrum和实践社区)已有效地组织了我们的工作。这些实践中的许多实践不仅对像Cambia这样的大型企业很有用,对于希望改善和改进敏捷实践适应性的小型企业也是如此。

著录项

相似文献

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

客服邮箱:kefu@zhangqiaokeyan.com

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

  • 服务号