Make sure your dev practices can support agile. You should have automated tests, daily integration builds, one-change-one check-in, customer accessible test environment, etc.
Get your customer on board. Scrum is a business-centric PM framework. It is in their interest to use agile techniques because it gets them the greatest value for their money. But they have to want it.
Get your team, PO, and management professional training in Scrum.
Make sure you, your team, and customers share the agile values (Agile Manifesto style). You would be amazed how many people value documentation over working software.
If you have 1-5, then go cold turkey. Scrum is a simple framework.
IMHO a step by step approach is wiser. You should first start doing retrospectives at the end of each iteration / sprint (if you use iterations - if not, that should be step 0 :-)
On the retrospective, you look through what is going well, not so well, and what can / should be improved. Then pick the most pressing issue and think about how it can be improved - primarily using Scrum, but you may have a look at other (agile or not) solutions too if you feel the need to. The aim is to work out your own process, which may be strict Scrum, or a hybrid - whatever works best for you, in your specific situation.
Personally, I would go a bit more Jeet Kun Do when it comes to project management strategies. With my team, I've created a piece of software where they answer the scrum questions (with some personal sauce), so instead of 15 minutes of debating, everybody knows what to do. And it beats having someone taking notes.
Even though SCRUM/Agile project management is populair, the waterfall approach has it benefits too. I would give a try-out first and keep the goodies and get rid of the baddies.
Make sure your team is truly cross-functional. Get all team members be commited 100% to the project on hand.
Note - succes of scrum teams often depends on strong scrum master - hence try to get a experienced scrum master or a coach to help your team during the transition period.
Try not to mix waterfall and agile - suggest go cold turkey to scrum.
发布评论
评论（4）
恕我直言，一步一步的方法是更明智的。您应该首先在每次迭代/冲刺结束时开始进行回顾（如果您使用迭代 - 如果没有，那应该是步骤 0 :-)
在回顾中，您会查看哪些进展顺利，哪些进展不顺利，以及哪些可以改进/ 应该改进。然后选择最紧迫的问题并考虑如何改进它 - 主要使用 Scrum，但如果您觉得有必要，您也可以看看其他（敏捷或非敏捷）解决方案。目的是制定您自己的流程，可以是严格的 Scrum，也可以是混合流程 - 根据您的具体情况，选择最适合您的流程。
IMHO a step by step approach is wiser. You should first start doing retrospectives at the end of each iteration / sprint (if you use iterations - if not, that should be step 0 :-)
On the retrospective, you look through what is going well, not so well, and what can / should be improved. Then pick the most pressing issue and think about how it can be improved - primarily using Scrum, but you may have a look at other (agile or not) solutions too if you feel the need to. The aim is to work out your own process, which may be strict Scrum, or a hybrid - whatever works best for you, in your specific situation.
就我个人而言，在项目管理策略方面，我会更多地采用截拳道。我和我的团队一起创建了一个软件，他们可以在其中回答 scrum 问题（带有一些个人的调味料），因此每个人都知道该怎么做，而不是 15 分钟的辩论。而且这比有人做笔记要好。
尽管 SCRUM/敏捷项目管理很流行，但瀑布方法也有它的好处。我会先尝试一下，保留好东西，除掉坏东西。
Personally, I would go a bit more Jeet Kun Do when it comes to project management strategies. With my team, I've created a piece of software where they answer the scrum questions (with some personal sauce), so instead of 15 minutes of debating, everybody knows what to do. And it beats having someone taking notes.
Even though SCRUM/Agile project management is populair, the waterfall approach has it benefits too. I would give a try-out first and keep the goodies and get rid of the baddies.
确保您的团队真正是跨职能的。让所有团队成员 100% 致力于手头的项目。
注意 - Scrum 团队的成功通常取决于强大的 Scrum Master - 因此尝试找一位经验丰富的 Scrum Master 或教练在过渡期间帮助你的团队。
尽量不要将瀑布式和敏捷混合在一起——建议彻底转向 Scrum。
Make sure your team is truly cross-functional. Get all team members be commited 100% to the project on hand.
Note - succes of scrum teams often depends on strong scrum master - hence try to get a experienced scrum master or a coach to help your team during the transition period.
Try not to mix waterfall and agile - suggest go cold turkey to scrum.