“销售” trac/buildbot/etc 到高层管理人员
我的团队主要使用基于 Flex 的应用程序。 话虽如此，几乎没有任何约定（甚至让它们重构本身就是一个奇迹）等等。
来自 .NET + CruiseControl.NET 背景，我一直渴望让每个人都使用一些像样的跟踪软件（我们现在使用 PHP 编码的待办事项列表）和 CI； 我认为 trac+BuildBot 将是一个不错的选择。
您如何说服高层管理人员这是可行的方法，以及 这篇文章？ 我的主要问题之一是每个人都在不加思考的情况下编码（你会对由此产生的“逻辑”类型感到惊讶......）
谢谢
My team works mostly w/ Flex-based applications. That being said, there are nearly no conventions at all (even getting them to refactor is a miracle in itself) and the like.
Coming from a .NET + CruiseControl.NET background, I've been aching to getting everyone to use some decent tracking software (we're using a todo list coded in PHP now) and CI; I figured trac+BuildBot would be a nice option.
How would you convince upper management that this is the way to go, as well as some of the rules mentioned in this post? One of my main issues is that everyone codes without thinking (You'd be amazed at the type of "logic" this spawns...)
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
现在有什么事情是你可以做而无需其他人许可的吗？ 您能否首先使用 trac/buildbot/etc 来完成您自己的工作，然后添加其他人感兴趣的内容？
根据我的经验，不问就做，你可以走得很远。
Is there anything you could do now that wouldn't require permission from anyone else? Could you start by just using trac/buildbot/etc for just your own work, then add in others as they are interested?
In my experience you can get quite far by doing w/out asking.
告诉管理层，使用这样的工具，他们将能够更好地关注进展情况。
Tell the management that they'll be better able to keep their eye on progress with such a tool.
您建议向他们展示而不需要他们购买的路线是否有具体的好处？
我有过让我的团队接受 Maven + Cruisecontrol CI 设置的经验。 基本上我试图让他们接受几天，但他们一直犹豫，因为它不熟悉。 然后我就自己做了，并将所有损坏的版本通过电子邮件发送到邮件列表。 那天晚上，项目负责人进行了一次检查，破坏了构建（他只是忘记了一个文件），当然，每个人都收到了关于他搞砸的电子邮件。
第二天，他走过来对我说：“我现在明白了。”
他不需要付出任何努力就能参与其中并免费看到好处。
Are there specific benefits to the route that you're suggesting that you could show them without them having to buy in?
I had an experience with getting my team to accept a maven + cruisecontrol CI setup. Basically I tried to get them to go along with it for a few days and they kept balking because it was unfamiliar. Then I just did it on my own and had all broken builds emailed to the mailing list. That night the project lead made a check in that broke the build (he just forgot a file) and, of course, everybody was emailed with his screw up.
The next day he came over to me and said, "I get it now."
It required no effort from him to get involved and got to see the benefits for free.