极限编程SaaS协作工具
我正在寻找专用于极限编程的 SaaS 协作工具。像带有积压日志、任务和项目管理、仪表板等的 SocialText 之类的东西...... 您使用哪些工具？
谢谢！
I'm looking for SaaS collaborative tools dedicated to extreme programming. Something like SocialText with back log, task and project management, dashboard, etc...
Which tools are you using ?
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
我推荐 Trello。
我们已经使用它有一段时间了，非常棒。
I would recommend Trello.
We have been using it for a while and it is great.
您可以尝试尽可能简单的 google wave。您可以将电子表格、日历、仪表板等 Google 小工具添加到您的 Wave 中。您可以添加图像、附件。您可以在 Wave 中协作管理项目。
You can try google wave which is simple as possible. You can add google gadgets like spreadsheet, calendar, dashboard etc. to your wave. You can add images, attechments. You can manage project collaboratively in wave.
您尝试过 Assembla 吗？它有积压工作、用户故事的票务系统、GIT 和 SVN 的托管源代码控制以及用于记录需求的 Wiki。它还显示了常见的燃尽图等。
Did you try Assembla? It has a backlog, a ticketing system for user stories, hosted source control for GIT and SVN and a Wiki for documenting requirements. It also shows the usual burndown charts etc.
我喜欢的 3 个很棒的工具：
并非所有这些本质上都是 SaaS，但安装和开始使用它们都很容易
3 great tools I love:
Not all of them are essentially SaaS, but it's easy to install and start using all of them
如果您正在跟踪迭代，我会推荐 Pivotal Tracker。如果您的做法更像看板风格，我会推荐 Trello ，两者都是 SaaS 解决方案。
I would recommend Pivotal Tracker if you are following iterations. If you are doing more like Kanban Style, I would recommend Trello both are SaaS solutions.
极限编程又被描述为专注于测试驱动的方法。它的原则基本上是采取极端的最佳工程实践（因此称为“极限编程”）。 XP常被称为平等结对编程；然而，这并不完全正确。虽然 XP 确实包含这种实践，但它还包含 11 种实践，包括首先编写单元测试、持续集成等。
附注：如果您决定使用 XP 框架，请确保遵循所有 12 条准则 - 甚至省略一条其中可能会使整个过程效率低下。完整源代码链接
Extreme Programming is, in its turn, described as concentrating on the test-driven approach. Its principles are, basically, best engineering practices taken to the extreme (hence the name "Extreme Programming"). XP is often said to equal pair programming; however, it is not completely true. While XP does include this practice, it consists of 11 more practices, including writing unit tests first, continuous integration, etc.
A quick side note: if you decide to use the XP framework, make sure you follow all 12 guidelines - omitting even one of them may make the whole process inefficient.link to full source