One of the (wonderful) purposes of agile techniques is to try and remove a lot of unnecessary planning, as you admit that your project plans will change, and that if you hold to a tried and true planning method such as the common waterfall method (reqs->specs->design->dev->qa->release, etc) that you're going to go through a lot of needless iterations and wasted time.
Either plan less, or have a pool of activities that developers can pull from if they have flexible time to use (minor feature requests, old UI bugs, less important things that can be dropped if needed)
In that case there is a chance of resources getting freed up from the planned work.
First, I'd start to talk about people or team members, not resources ("respect people").
It may get difficult to allocate new tasks to them during sprint
You shouldn't allocate tasks to people (this sounds like micro-management). Tasks are in the queue (the sprint) and the team should self-organize to get items DONE, focusing on most important items first.
What is the best way to plan resources in these situations?
I think Agile still needs planning, otherwise anyone will pull anything from the backlog queue and start working on absolutely unrelated tasks and it will reach no where. work need to be planned to achieve common goal. Database and environmert resources need to be planned for availability if there are crossfunctional teams
First off, I am not sure what "agile" methods you are following. In Agile SCRUM the ScrumMaster manages the backlog and the user stories are weighted (prioritized) by the team. This ensures that they won't just "pull anything from the backlog". Each sprint has a common goal.
Agile development doesn't just mean any one can do anything within a sprint...there is still structure in it with daily standups for reveiwing progress and adding more to the sprint if needed, as well as sprint reviews and sprint planning meetings. The key is that the team is self-mananging the work with guidance from the ScrumMaster.
发布评论
评论（5）
只需给您的资源一些自由即可。如果它是敏捷的——他们会很高兴。
Just give your resources some freedom. If it is agile - they will be happy.
“在冲刺期间向他们分配新任务可能会很困难，因为那时大多数项目都与计划的工作紧密相关”
项目管理的味道。
如果您“预先计划”了所有工作，那就不是很敏捷，不是吗？敏捷==灵活。您应该能够重新排列而不破坏任何东西。
如果你的计划“被打破”，那么你的计划太多而敏捷太少。
这种事情你不应该过度计划。
"It may get difficult to allocate new tasks to them during sprint as mostly all projects are tied up at that point with planned work"
Project management smell.
If you have "pre-planned" all the work, that's not very Agile, is it? Agile == Flexible. You should be able to rearrange without breaking anything.
If your plan "breaks" you have too much plan and too little Agile.
You shouldn't over-plan this kind of thing.
敏捷技术的（美妙的）目的之一是尝试消除许多不必要的计划，因为您承认您的项目计划将会改变，并且如果您坚持一种经过验证的真实计划方法，例如常见的瀑布方法（ reqs->specs->design->dev->qa->release 等），您将经历大量不必要的迭代并浪费时间。
要么减少计划，要么拥有一个活动池，如果开发人员有灵活的时间可以使用（次要的功能请求、旧的 UI 错误、如果需要可以删除的不太重要的事情）
One of the (wonderful) purposes of agile techniques is to try and remove a lot of unnecessary planning, as you admit that your project plans will change, and that if you hold to a tried and true planning method such as the common waterfall method (reqs->specs->design->dev->qa->release, etc) that you're going to go through a lot of needless iterations and wasted time.
Either plan less, or have a pool of activities that developers can pull from if they have flexible time to use (minor feature requests, old UI bugs, less important things that can be dropped if needed)
首先，我会开始谈论人或团队成员，而不是资源（“尊重人”）。
您不应该向人员分配任务（这听起来像微观管理）。任务在队列（冲刺）中，团队应该自我组织以完成项目，首先关注最重要的项目。
最好的办法就是不做。
First, I'd start to talk about people or team members, not resources ("respect people").
You shouldn't allocate tasks to people (this sounds like micro-management). Tasks are in the queue (the sprint) and the team should self-organize to get items DONE, focusing on most important items first.
The best way is to not do it.
我认为敏捷仍然需要规划，否则任何人都会从待办事项队列中取出任何东西并开始处理完全不相关的任务，并且它不会到达任何地方。需要计划工作以实现共同目标。如果存在跨职能团队，则需要规划数据库和环境资源的可用性
首先，我不确定您正在遵循什么“敏捷”方法。在敏捷 SCRUM 中，ScrumMaster 管理积压工作，并且用户故事由团队加权（优先级）。这确保了他们不会只是“从积压的工作中提取任何东西”。每个冲刺都有一个共同的目标。
敏捷开发不仅仅意味着任何人都可以在冲刺中做任何事情......其中仍然有每日站立会议的结构，用于审查进度并在需要时向冲刺添加更多内容，以及冲刺审查和冲刺计划会议。关键是团队在 ScrumMaster 的指导下自我管理工作。
I think Agile still needs planning, otherwise anyone will pull anything from the backlog queue and start working on absolutely unrelated tasks and it will reach no where. work need to be planned to achieve common goal. Database and environmert resources need to be planned for availability if there are crossfunctional teams
First off, I am not sure what "agile" methods you are following. In Agile SCRUM the ScrumMaster manages the backlog and the user stories are weighted (prioritized) by the team. This ensures that they won't just "pull anything from the backlog". Each sprint has a common goal.
Agile development doesn't just mean any one can do anything within a sprint...there is still structure in it with daily standups for reveiwing progress and adding more to the sprint if needed, as well as sprint reviews and sprint planning meetings. The key is that the team is self-mananging the work with guidance from the ScrumMaster.