You could try to use Kanban. It is more suited for such dynamic situations than Scrum. The ultimate solution would be to use Kanban for support activities and Scrum for development, but in case you spend much less than 50% of your time for development this may be not worthed (overengineering).
Even though it is purely reactive, you surely have larger requests that need to be prioritized? I am using Scrum in a support situation to help prioritizing the non-emergency work that often requires hours or days of effort. I think that Scrum in some ways fits in even better in a support situation than in development.
I would start with prioritizing the issues that come in (someone from the business end should be responsible for that), making things visible (e.g. getting them up on a task board), and improving your definition of done for each task (tests, code review, etc).
Now that you have a tester with the team, it would be a good time to start some TDD and definitely start automating a lot of your tests.
Once you have some of these basics in place, you can look at either Scrum or Kanban depending on your needs. If tasks always seem to come out of the blue, Kanban is probably more appropriate as another poster suggested.
In order to be successful with Kanban, you must make sure that you have a very solid definition of done to ensure that you maintain quality throughout. Without it, you won't see the full benefit.
I would also recommend scheduling regular retrospectives to see what is working for you and where you need to improve.
发布评论
评论（3）
您可以尝试使用看板。它比 Scrum 更适合这种动态情况。最终的解决方案是使用看板进行支持活动，使用 Scrum 进行开发，但如果您花在开发上的时间远少于 50%，那么这可能不值得（过度设计）。
You could try to use Kanban. It is more suited for such dynamic situations than Scrum. The ultimate solution would be to use Kanban for support activities and Scrum for development, but in case you spend much less than 50% of your time for development this may be not worthed (overengineering).
尽管它纯粹是被动的，但您肯定有更大的请求需要优先考虑吗？我在支持情况下使用 Scrum 来帮助确定通常需要数小时或数天努力的非紧急工作的优先级。我认为 Scrum 在某些方面比开发更适合支持情况。
Even though it is purely reactive, you surely have larger requests that need to be prioritized? I am using Scrum in a support situation to help prioritizing the non-emergency work that often requires hours or days of effort. I think that Scrum in some ways fits in even better in a support situation than in development.
我首先会优先考虑出现的问题（业务端的某个人应该负责），使事情可见（例如将它们放在任务板上），并改进每个任务的完成定义（测试、代码）审查等）。
现在您的团队中已经有了一名测试人员，现在是开始一些 TDD 并肯定开始自动化大量测试的好时机。
一旦掌握了其中一些基础知识，您就可以根据需要查看 Scrum 或看板。如果任务似乎总是突然出现，那么看板可能更合适，正如另一位海报所建议的那样。
为了在看板方面取得成功，您必须确保对完成有一个非常可靠的定义，以确保自始至终保持质量。没有它，您将无法看到全部好处。
我还建议安排定期回顾，看看什么对你有用，什么地方需要改进。
I would start with prioritizing the issues that come in (someone from the business end should be responsible for that), making things visible (e.g. getting them up on a task board), and improving your definition of done for each task (tests, code review, etc).
Now that you have a tester with the team, it would be a good time to start some TDD and definitely start automating a lot of your tests.
Once you have some of these basics in place, you can look at either Scrum or Kanban depending on your needs. If tasks always seem to come out of the blue, Kanban is probably more appropriate as another poster suggested.
In order to be successful with Kanban, you must make sure that you have a very solid definition of done to ensure that you maintain quality throughout. Without it, you won't see the full benefit.
I would also recommend scheduling regular retrospectives to see what is working for you and where you need to improve.