博客
关于我
强烈建议你试试无所不能的chatGPT,快点击我
软件敏捷开发_避免开发敏捷软件的错误
阅读量:2506 次
发布时间:2019-05-11

本文共 4503 字,大约阅读时间需要 15 分钟。

软件敏捷开发

According to a survey taken of the Scrum Alliance, approximately handling Agile software development believe there are issues present between various internal departments within the company.

根据对Scrum联盟进行的一项调查,处理敏捷软件开发大约有认为公司内部各个部门之间存在问题。

The fact is, Agile groups work at a much faster pace. In order to mark progress, they use various markets, and in some cases, this puts staff members in direct conflict with each other.

事实是,敏捷团队的工作速度要快得多。 为了标记进步,他们使用各种市场,在某些情况下,这使工作人员彼此直接冲突。

The disjunction described above among Agile groups, as well as their peers, is a common mistake in the realm of Agile software development. However, there are a number of other reasons that some Agile projects are unsuccessful as well.

敏捷团队及其同伴之间的上述分离是敏捷软件开发领域中的常见错误。 但是,还有许多其他原因导致某些敏捷项目也未能成功。

You can learn about some of these issues here, and if you have some problems not listed in the article, you can check out software development forum. Knowing what these mistakes are can help you avoid them.

您可以在此处了解其中的一些问题,如果您有本文未列出的某些问题,可以查看软件开发论坛。 了解这些错误是什么可以帮助您避免这些错误。

Agile Software Development Mistakes to Avoid

不使用客户输入 (Not Using Customer Input)

There is a large number of groups that don’t pay attention to or use the information that is gathered from their customers when creating project designs. It’s smart to use feedback from customers so that you aren’t creating something that’s completely irrelevant.

在创建项目设计时,有很多小组不关注或使用从客户那里收集的信息。 使用客户的反馈很聪明,这样您就不会创建完全不相关的内容。

敏捷团队培训不当 (Improper Training of the Agile Team)

According to , up to 30 percent of the people who responded to the study mentioned above stated that they were not provided with sufficient training. Some even claimed that they received minimal training on the methodologies used by the company.

根据说法,对上述研究做出答复的人中,多达30%的人表示他们没有得到足够的培训。 一些人甚至声称他们对公司所使用的方法学的培训很少。

与其他部门不同步 (Not Being in Sync with Other Departments)

Are you in sync with other departments? If you aren’t, you are going to find it virtually impossible to meet the job approximation objectives. This is especially true if the other departments in question are integral to the success of the job or if they are focused on a timeline that isn’t associated with the development group.

您是否与其他部门保持同步? 如果不是,您将发现几乎不可能达到工作近似目标。 如果有问题的其他部门对工作的成功至关重要,或者他们专注于与开发小组无关的时间表,则尤其如此。

低于估算 (Subpar Estimates)

Quickness and velocity are essential when it comes to receiving the proper estimates. As a result, you need to be mindful when you are providing your group with practice time. It’s essential to provide accurate estimates before you give any type of compliance promises.

要获得适当的估算值,速度和速度至关重要。 因此,在为小组提供练习时间时,您需要注意。 在给出任何类型的合规承诺之前,必须提供准确的估计。

参与度不足 (Inadequate Engagement )

The majority of members of a group may be working in a remote location from time to time. This makes it much more challenging to have important conversations about important parts of the project that is going on. With that being said, most remote workers are only going to highlight the things that would still be an issue if everyone was working in the same building – inadequate engagement.

组中的大多数成员可能会不时地在远程位置工作。 与正在进行的项目的重要部分进行重要对话使挑战变得更加艰巨。 话虽这么说,大多数远程工作者只会强调如果每个人都在同一栋楼里工作,那仍然是个问题–参与不足。

无法进行回顾 (The Inability to Conduct the Retrospectives)

If you bypass the retrospective step in the Agile software development methodology, you are not providing your bigger group with the opportunity to assess and to enhance their own productivity. This can lead to negative consequences for the entire group.

如果您绕过了敏捷软件开发方法论中的回顾性步骤,那么您就没有为更大的团队提供评估和提高他们自己的生产力的机会。 这会对整个团队造成负面影响。

最少的小组努力和过多的命令 (Minimal Group Effort and Excessive Orders)

You should not work with a top-down methodology. Modern Agile leaders are encouraged to work and lead their group members toward a solution, rather than try to make them complete separate jobs on an individual basis.

您不应该使用自上而下的方法。 鼓励现代敏捷领导者开展工作,带领团队成员寻求解决方案,而不是试图使他们单独完成单独的工作。

公司文化不支持敏捷开发 (The Agile Development isn’t Being Supported by the Company Culture)

There are far too many companies that have a conflicting culture to the Agile methodology. This is going to result in subpar results for the entire team.

太多的公司与敏捷方法文化冲突。 这将导致整个团队的成绩低于标准。

If you want a successful Agile development process, then it is absolutely imperative that you know about the most common mistakes that are made. When you know what these mistakes are, you can take steps to ensure they don’t occur. In the long run, this is going to lead to a much higher rate of success.

如果您想要成功的敏捷开发过程,那么绝对有必要知道最常见的错误。 当您知道这些错误是什么时,您可以采取措施确保它们不会发生。 从长远来看,这将导致更高的成功率。

翻译自:

软件敏捷开发

转载地址:http://vvggb.baihongyu.com/

你可能感兴趣的文章
poj1185 炮兵阵地【状压DP】
查看>>
python2和python3 print输出不换行
查看>>
python使用progressbar显示进度条
查看>>
卷积神经网络的权值参数个数的量化分析
查看>>
telnet 的使用(ping 与 telnet)
查看>>
推理集 —— 物质与成分及性质的研究
查看>>
服务端事件EventSource揭秘
查看>>
Oracle 物理DG切换
查看>>
iOS本地版本和服务器对比
查看>>
js剪贴板操作
查看>>
spring mvc常用注解的说明
查看>>
MapReduce 编程模板编写【分析网站基本指标UV】程序
查看>>
一个整形数组中最大值求和问题(3)
查看>>
【bzoj2500】幸福的道路 树形dp+单调队列
查看>>
do/while(0)的妙用(转)
查看>>
UDP编程
查看>>
ecos中断机制分析(1)
查看>>
Plus One
查看>>
11.4 iftop:动态显示网络接口流量信息
查看>>
jQuery API中文文档
查看>>