如何让管理层相信 QA 很重要? [英] How to convince management that QA is important?

查看:24
本文介绍了如何让管理层相信 QA 很重要?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在一家程序员不到 10 人的小型软件公司工作.我们的软件安装在世界各地的数十个地方.我们的代码库很大,主要是由于糟糕的设计和大量的代码重复 (IMO).我们有大约 30 个不同的项目,每个项目总共有大约 600 KLOC,其中大约 200 KLOC 是我们自己开发的代码.当我在 2006 年到达那里时,此代码甚至不受版本控制.我已经设法说服权力它很重要,我们现在使用代码控制系统(cs-rcs,不是我的选择,但总比没有好)和错误跟踪系统.最大的缺失是整个过程中完全缺乏 QA.我们的发布过程在纸面上是不存在的,实际上它包括按 ctrl-F9,将二进制文件复制到客户端,声明问题已修复."

I work for a small software company with less than 10 programmers. Our software is installed in dozens of places across the world. Our code base is huge, due mostly to poor design and massive amounts of duplication of code (IMO). We have roughly 30 different projects, each with a total of about 600 KLOC with about 200 KLOC of that being our own homegrown code. When I got there in 2006, this code wasn't even under revision control. I've managed to convince powers that its important, and we now use a code control system (cs-rcs, not my choice but its better than nothin), and a bug tracking system. The huge missing piece is the total and complete lack of QA in the process. Our release process is non existant on paper, and in practice it consists of "hit ctrl-F9, copy binary to client, declare problem fixed."

谁能告诉我一些官方文件或PHB语言文件或文章,可以解释这个过程中公然的疯狂?我敢肯定老板可以聘请一些顾问告诉他这一点,然后他可能会相信.但我只是一个拥有软件工程学士学位的低级维护者.我的种族也帮不了我.在这种情况下最好使用什么弹药?

Can anyone point me to some official papers or PHB-language documents or articles that can explain the blatant lunacy in this process? I'm sure the boss could hire some consultant to tell him this, and then he might believe it. But I'm just a lowly maintainer with a Software Engineering BS degree. And my ethnicity doesn't help me either. What's the best ammunition to use in this case?

推荐答案

同义反复,说服他们的唯一方法是将他们置于令人信服的事物面前.那个东西可以从一个列表中提取,例如:

Tautologically, the only way to convince them is put them in front of something that is convincing. That thing could be drawn from a list such as:

  • 预示着代价高昂的灾难促使人们采用先前提出的解决方案
  • 该无法预料的灾难现成的永不重复的解决方案
  • A有说服力的预言一场灾难
  • 一个出色的对贪婪的说服力(节省预言的机会成本灾难)

或者别的什么.在所有这些情况下,您将不得不在某个时候为您提出的 QA 解决方案提出理由,而从表面上看,这个人必须是您.所以我会开始学习如何有说服力.

Or something else. In all these cases, someone is going to have to make the case at some point for the QA solution you propose, and that someone, from the looks of it, is going to have to be you. So I'd start learning about being persuasive.

如何赢得朋友和影响他人最多应该花你几块钱.选择是也很便宜.

How to Win Friends and Influence People should cost you a few bucks at most. Getting To Yes is also cheap.

您是如何就源代码控制达成一致的?您能否继续努力,一次一点点地改进流程?

How did you get agreement to source control? Can you keep chipping away, improving the process a small increment at a time?

尝试谷歌搜索改变你的组织",看起来有一些有希望的链接.

Try Googling "change your organization", there looked to be some promising links.

最后,请记住(正如一位智者曾经说过的)如果你不能改变你的组织,那么你应该改变你的组织.总有另一种选择.

And ultimately, remember that (as a wise man once said) if you can't change your organization then you should change your organization. There really is always an alternative.

这篇关于如何让管理层相信 QA 很重要?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆