Greenhopper:只有购买整个敏捷包才有用吗?

发布于 2024-09-29 21:53:46 字数 261 浏览 0 评论 0原文

我在一家远程公司工作,电子邮件、论坛和即时消息是主要的沟通工具。我们没有正式遵循任何书本方法,但在发布计划、客户交互和适合分布式团队的某种 Scrum 方面,我们一直在朝着更敏捷风格的设置发展。

我们在一个项目中使用 Jira,我想知道 Greenhopper 是否有用。或者,它是否专注于更正式地遵守整个敏捷教条的团队,并且最终会妨碍?

我不想讨论敏捷是好还是坏、它涉及什么等等……只是 Greenhopper 对于那些方法论受到敏捷原则启发而不是由它们定义的项目是否有用。

I work in a remote company where email, forums and IM are key communication tools. We don't formally follow any book-methodology but have been evolving towards a more agile-style setup in terms of release schedules, client interaction and a sort of scrum adapted for distributed teams.

We use Jira on one project and I wondered if Greenhopper might be of use. Or, whether it is focused on teams who adhere much more formally to the entire Agile dogma, and would end up getting in the way?

I don't want to get into a discussion on if Agile is good or bad, what it involves, etc... just whether Greenhopper is useful to projects whose methodology is inspired by Agile principles rather than defined by them.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

三生路 2024-10-06 21:53:46

GreenHopper 非常灵活。我见过营销团队、运营团队等使用任务板来跟踪他们正在进行的工作,但没有任何真正的“敏捷”想法。尝试一下,让我知道你进展如何。

谢谢,
尼古拉斯·马尔登
格林霍珀产品经理

GreenHopper is pretty flexible. I've seen marketing teams, operations teams plus more using the task board to track their work in progress without any real though to 'agile'. Give it a shot and let me know how you get on.

Thanks,
Nicholas Muldoon
GreenHopper Product Manager

ゞ记忆︶ㄣ 2024-10-06 21:53:46

我不会评论 Greenhopper,因为我最近没有这方面的经验。

许多工具都是基于“纯敏捷”模型设计的。也就是说,对于单个团队来说,为单个产品所有者或单个产品所有者工作。

然而,根据我的经验,现实世界中的绝大多数组织(即使是非常小的组织)都需要管理更复杂的环境。通常,即使是一个自由开发人员也有很多事情要做:活跃的项目、新项目的领导、旧项目的维护等等。具有纯 Scrum、一个团队一次只处理一件事情的简单工具并不能解决这个问题……

Agilefant 是恕我直言,虽然遵守“敏捷教条”,但在如何将人们分配到多个事物方面非常灵活。此外,它在如何将不同类型的工作建模到其中方面非常灵活(也就是说,不需要将每个项目都作为 Sprint 进行,等等)。

免责声明:我是 Agilefant 的产品负责人。

I won't comment on Greenhopper, since I don't have recent experience regarding it.

Many tools are designed based on a "pure agile" model. That is, for a single team, working on a single thing for or a single product owner.

However, in my experience the vast majority of real-world organizations – even the very small – have a more complex landscape they need to manage. Often, even a single freelance developer has a load of things to work on: the active project(s), leads for new projects, maintenance of old projects, and so on. And simple tools that have a pure-scrum-one-team-works-on-a-single-thing-at-a-time just won’t cut it…

Agilefant is IMHO, while complient with "the agile dogma", also pretty flexible with respect to how people can be assigned to multiple things. Also, it's quite flexible in terms how different types of work can be modeled into it (that is, there's no need to conduct every project as Sprints, and so on).

DISCLAIMER: I'm Agilefant's product owner.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文