scrum敏捷_Scrum敏捷原则

scrum敏捷

Waterfall as a methodology, is not a bad thing. In few cases it makes good sense, like to start building construction, where a defined set of steps, when implemented in order, will result in a building.

瀑布作为方法论,不是一件坏事。 在极少数情况下,这很有意义,例如开始建筑施工,如果按顺序实施,则定义的一组步骤将形成建筑物。

Factual work is more like a science experiment. You try something, check out the outputs and if it didn't work for you, try some other approach. You surely can't do that when constructing a house, but with software or some other product, you can do it every day. That's why waterfall didn't work well for software development.

事实工作更像是科学实验 。 您尝试一些操作,检查输出,如果对您不起作用,请尝试其他方法。 建造房屋时,您当然不能做到这一点,但是有了软件或其他产品,您每天都可以做到。 这就是为什么瀑布不能很好地用于软件开发的原因。

You literally cannot upfront plan the process of discovery. The frustration of highly skilled software developers working on Waterfall projects was the tipping point that led to the Agile revolution.

您实际上无法预先计划发现过程。 从事瀑布式项目的高技能软件开发人员的挫败感是引发敏捷革命的转折点。

Have a look at the Agile Manifesto and it's underlying principles. This group of innovators supported this manifesto with 12 key principles. This manifesto and the principles became the foundation for a new set of project management and software development methodologies.

看看《敏捷宣言》及其基本原理。 这组创新者通过12条关键原则支持了这一宣言。 这一宣言和原则成为了一套新的项目管理和软件开发方法的基础。

Agile Manifesto: Check Out

敏捷宣言: 签出

Principles behind the Agile Manifesto: 12 sacred principles

敏捷宣言背后的原则: 12项神圣原则

是什么使敏捷与众不同? (What make Agile different?)

There are a couple of overriding themes that make Agile different. One of the key changes is that, we're asking our business partners to work with us throughout the project. Not just show up at the beginning to describe what they want, then show up at the end and tell us how we missed the mark. We need direct, on going interaction to deliver what they really need.

有几个最重要的主题使敏捷与众不同。 关键的变化之一是,我们要求业务伙伴在整个项目中与我们一起工作。 不仅要在开始时出现来描述他们想要的东西,然后在结尾时出现并告诉我们我们如何错过分数。 我们需要持续不断的互动,以交付他们真正需要的东西。

Another key is that we no longer want to measure success using milestones and project phases.

另一个关键是我们不再希望使用里程碑和项目阶段来衡量成功。

翻译自: https://www.studytonight.com/scrum-framework/agile-principles

scrum敏捷

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值