blocks|key|1022950|text|六西格玛可以很好地处理可重复的流程。我的意思是，纯过程始终产生(或应该产生)相同的输出。考虑到软件开发很少产生相同的输出，SS不是真正适用的，IMO。这是因为软件开发与其说是一个过程，不如说是一种实践。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1022951|话虽如此，读一读关于它的文章，并尝试了解哪些顶级想法可以放入软件开发中并不会有什么坏处……|1022952|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Six Sigma works well with reproducible processes. By that, I mean pure process that consistently produces (or is supposed to produce) the same output. Given that software development rarely produces the same output, SS is not really applicable, IMO. This is because software development is more a practice than a process.

That being said, it doesn't hurt to read about it and try to see what top-level ideas can be put into software development...

blocks|key|3538253|text|如果我理解正确的话，六西格玛依赖于有意义的、可衡量的指标。你的是什么？科洛克？将类签入到您的归档中？敏捷速度？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3538254|Six+sigma在车间工作得很好，但我不认为软件开发足够“小部件式”，不适合这样的方法。|3538255|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If I understand it correctly, six sigma depends on having meaningful, measurable metrics. What will yours be? KLOC? Classes checked into your archive? Agile velocity?

Six sigma works great on shop floors, but I don't believe that software development is sufficiently "widget-like" to lend itself to such an approach.

blocks|key|1027969|text|只要你不是在开发新产品，这绝对是可能的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1027970|只需遵循以下步骤。|1027971|1)创建应用程序的无bug版本。这可能需要大量的工作，因此最好选择一个范围不大的应用程序。|1027972|2)从头开始重新创建应用程序，并将迭代与步骤1中创建的理想情况进行比较，以创建指标。|1027973|3)调整您的流程，以便在下一次迭代中获得与度量更接近的对齐。|1027974|4)转到步骤2。|1027975|什么？你不会在你的商店里一遍又一遍地创建相同的应用程序吗？嗯，我不认为六西格玛在这种情况下会有多大用处。|1027976|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

It is definitely possible as long as you aren't developing a new product. 

Just follow these steps.

1) Create a bug free version of the application. This may take a considerable amount of effort thus it is best to select an application that is trivial in scope. 
2) Recreate the application from scratch and compare the iteration to the ideal created in step 1 to create a metric. 
3) Tweak your process to acheive closer alignment next to the metric on the next iteration. 
4) Go to step 2.

What? You don't create the same application over and over in your shop? Hmm, I don't think six sigma is going to be much use in that scenario.

blocks|key|1022996|text|为了让六西格玛变得有用，你需要容易比较的指标或程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1022997|软件太抽象了，无法提供所需的度量类型。|1022998|也许一个很好的问题是|1022999|1023000|在生产和制造领域，是否有类似于六西格玛的软件开发质量控制工具？|blockquote|1023001|1023002|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|O|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|P|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|Q|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|L|$]]

For Six Sigma to be useful you need easily comparable metrics or procedures. 

Software is too abstract to have the type of metrics needed.

Maybe a good question to ask would be 

<blockquote>
 Is there a quality control tool for software development similar to Six Sigma for the production and manufacturing world?
</blockquote>

blocks|key|320429|text|我使用了广泛的方法，六西格玛，敏捷等等。真正的软件开发质量管理的成功取决于一件关键的事情。球队的实力。这一切都归结为这一点。一个好的团队可以在一种糟糕的方法中工作，并让它工作。这就是为什么他们很棒的原因。流程很重要，你可以让一个糟糕的流程变得更有效率，但这完全取决于团队。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|320430|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I've used a wide range of methodologies, Six Sigma, Agile etc. Really the success of quality management on software development is dependent on one key thing. The quailty of the team. It all boils down to that. A good team can work within a horrible methodology and make it work. That's why they are good. Process is important, and you can make a bad process more efficient, but it's all dependent on the team.

blocks|key|320663|text|软件开发的某些部分并不适合，因为它们不能提供具有正态分布结果的过程。另一方面，关注风险、价值和做正确的事情是必不可少的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|320664|编辑看看Cynefin模型(在wikipedia上)，以了解为什么大部分软件开发都在复杂的领域中。|320665|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

There are parts of software development that don't fit well, as they do not provide a process with a normal distribution of results. On the other hand, the focus on risk, value and doing the right things is essential 

[edit] Take a look at the Cynefin model (on wikipedia) to understand why large parts of software development are in the complex domain.

blocks|key|3538609|text|六西格玛可以很好地适用于有大量积压的离散工作项目的维护团队。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3538610|六西格玛设计有一些可以应用于构建新软件产品的元素。|3538611|由于大多数软件是业务流程的推动者，并且该业务流程可能是一个高度重复的过程，其中可以应用六西格玛的统计工具，因此六西格玛可以在确定什么是提供最大业务价值的最高价值软件功能方面发挥作用。它可以将情感从决策过程中剔除，以确定特征的优先级。如果您的环境中，产品经理/利益相关者的呼声最大或最有说服力地建立了他们的东西，则可以应用六西格玛来修复开发过程中不健康的方面，方法是将一些合理的度量放在优先级确定过程之后。|3538612|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Six Sigma can be a good fit for maintenance teams that have a big backlog of discrete work items.

Design for Six Sigma has some elements that can be applied to building a new software product.

And since most software is an enabler to a business process, and that business process may be a highly repeated process where the statistics tools of six sigma can be applied, six sigma can have a role in determining what the highest value software feature is to deliver maximal business value. It can take the emotion out of the decision making process for feature prioritization. If you have an environment where the product manager/stakeholder who yells loudest or most eloquently got their stuff built, six sigma can be applied to fix that unhealthy aspect of your development process by putting some rational measurement behind the prioritization process.

blocks|key|320560|text|我不一定会跟你走。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|320561|SixSigma是一种管理流程变化的方法论，它使用数据和统计分析来衡量和改进公司的运营绩效。|offset|length|style|BOLD|320562|因此，采取任何流程(SDP或其他)，选择要衡量的内容，确定问题，计划解决方案，评估影响。|320563|我参与的所有SixSigma项目都是相当横向的，与软件生命周期无关。|320564|320565|通过横向，我的意思是横向到“产品设计-开发-构造-交付”的过程，即软件开发。|320566|例如，在一个环境中，我们需要在内部生产平台上生成一组运行在我们的生产平台上的程序，我们的大多数SixSigma项目都是以为中心的，即“使操作成为一个执行环境”(如何设置服务器和网络，以便停止、更新、安装和启动一组可执行程序，以及许多项目，每个项目都有自己的可执行程序)。|320567|这是一个横切到你想要的任何SDP的概念，因为最终，所有这些“开发过程”只有一个共同的目标:将你的软件投入生产。|320568|要衡量的标准是精确和可重复性的，从管理合并最终可执行文件所需的合并时间到合并错误的数量，再到部署错误(由于错误的标签或错误的发行说明)。|320569|所有这些失误都被记录在一个又一个版本中，目标是减少它们。|320570|一个副作用是找出一个不充分的merge+workflow，工作流程，一旦修复，允许我们极大地减少最终交付集的错误。|320571|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Six_Sigma|1|https://stackoverflow.com/questions/216212#216228^0|0|D|8|0|8|0|0|0|0|0|0|0|0|0|0|E|E|1|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@$D|1A|E|1B|F|G]]|9|@$D|1C|E|1D|1|1E]]|A|$]]|$1|H|3|I|5|6|7|1F|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1G|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1I|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1J|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1K|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1L|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1M|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1N|8|@]|9|@$D|1O|E|1P|1|1Q]]|A|$]]|$1|Y|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]|16|$5|11|12|13|A|$14|17]]]]

I am not sure to follow you.

<a href="http://en.wikipedia.org/wiki/Six_Sigma" rel="nofollow noreferrer">SixSigma</a> is a is a methodology to manage process variations that uses data and statistical analysis to measure and improve a company's operational performance.

So take any process (SDP or other), choose what you want to measure, identify the issues, plan the solutions, evaluate the impacts.

The SixSigma projects I have participated were all fairly transversal and not linked to a software life cycle.

<hr>

By transversal, I mean transversal to the "product design-development-construction-delivery" process that is software development.

For example, in an environment were we need to produce a set of programs running on our internal production platform, most of our SixSigma projects are centered around <a href="https://stackoverflow.com/questions/122931#123132">Operational Architecture</a>, that is "making operational an execution environment" (how to set up servers and networks in order to stop, update, install and launch a set of executables, and that for many projects each with their own SDP). 
That is a notion transversal to any SDP you want, since in the end, all those "Development Processes" have but one goal in common: put your software into production.

The criteria to measure were precise and reproducible, going from the time to manage the merges needed to consolidate a final executable to the number of merge errors to the deployment errors (because of an incorrect labels or a faulty release notes).

All those missteps were noted release after release, and the goal was to reduce them. 
One side-effect was to identify an inadequate <a href="https://stackoverflow.com/questions/216212#216228">merge workflow</a>, workflow which, once fixed, allowed us to greatly reduce the errors in the final set of deliveries.

blocks|key|320747|text|我在一个班上有一位教授教授六西格玛和其他生产效率技术，在告诉他我在软件开发领域后，他建议我写一本书Lean+Software+Development。不幸的是，我没有读过它，但它似乎涉及到将六西格玛和精益制造的一些适用概念应用于生产软件(如消除浪费，减少缺陷，持续改进)。Here's是一份描述精益软件开发的简短白皮书。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|320748|entityMap|0|LINK|mutability|MUTABLE|url|http://books.google.com/books?id=8o1eom6ifIMC&dq=lean%2Bsoftware%2Bdevelopment&printsec=frontcover&source=bn&hl=en&ei=ra16S6ihG5CjngfPwaj4DA&sa=X&oi=book_result&ct=result&resnum=4&ved=0CCcQ6AEwAw#v=onepage&q=&f=false|1|http://www.projectperfect.com.au/info_lean_development.php^0|1D|P|0|3S|6|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

I had a professor in a class that taught six sigma and other manufacturing efficiency techniques, and after telling him I was in the software development field he suggested the book <a href="http://books.google.com/books?id=8o1eom6ifIMC&amp;dq=lean+software+development&amp;printsec=frontcover&amp;source=bn&amp;hl=en&amp;ei=ra16S6ihG5CjngfPwaj4DA&amp;sa=X&amp;oi=book_result&amp;ct=result&amp;resnum=4&amp;ved=0CCcQ6AEwAw#v=onepage&amp;q=&amp;f=false" rel="nofollow noreferrer">Lean Software Development</a>. Unforunately I haven't read it, but it seems to deal with applying some of the applicable concepts of six sigma and lean manufacturing to producing software (like eliminating waste, reducing defects, continuous improvement). <a href="http://www.projectperfect.com.au/info_lean_development.php" rel="nofollow noreferrer">Here's</a> a short white paper describing lean software development.

blocks|key|4385949|text|我在具体的性能测试项目中使用了六西格玛，这些项目以特定的可测量的问题陈述开始，以同样可测量的反措施结束。DMAIC有助于性能调优，因果分析、实验设计等工具和技术也是如此。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4385950|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I have used Six Sigma for specific performance testing projects which begin with a specific measurable problem statement and end with a counter measure that is again measurable. The DMAIC lends itself to performance tuning, as do the tools and techniques of Causal Analysis, Design of Experiments etc.

Is it possible to use Six Sigma Quality Management with Software Development Processes?

What's your experience on that?

If you're using an Agile method like Scrum or XP, isn't Six Sigma too bureaucratic?

I'm talking about quality management on software development as a whole, since requirements gathering until deployoment and operations, and not only the construction phase (which tools like TDD and unit testing are more or less already established as best practices).

Six sigma quality management and software development

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

是否可以在软件开发过程中使用六西格玛质量管理？你对此有什么经验？如果你使用像Scrum或XP这样的敏捷方法，六西格玛是不是太官僚了？我谈论的是整个软件开发的质量管理，因为需求收集直到部署和运营，而不仅仅是构建阶段(像TDD和单元测试这样的工具或多或少已经被确立为最佳实践)。

问六西格玛质量管理和软件开发
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问六西格玛质量管理和软件开发EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问六西格玛质量管理和软件开发
EN