Simple. Don't talk about scrum. Don't use scrum on her. Instead take the underlying principles of scrum (e.g. the purpose as opposed to the application) and create different approaches that accommodate her way of working but have subtle tints of scrum.
All humans are different and a lot of programmers dislike scrum. I wouldn't force it upon them as that would just be counter-productive. I'd suggest identifying the problems in the development process (in a non-scrum fashion), see if you can get her to agree that the issues exist, then ask her what she thinks would be a good solution. Her co-operation and input into the process is essential to her co-operation, if she doesn't have buy-in she wont become a citizen.
From there on in you can hopefully create some sort of quasi-hybrid scrum + her approach to the process where you can both agree on the way forward.
Without her input, I started the Scrum practices (daily scrums, burndown charts and other things I've found that worked for me and my previous teams (ala H. Kniberg's cool wall chart). During out daily stand up she slinks by and ignores us as if we actually weren't standing right outside her door (we are actually). It's pretty amazing. I've never seen such resistance.
Question... how do I get her onboard? Peer pressure is not working.
Yikes! Who would ever want to work in such an oppressive environment? If you're lucky, she's sending around her resume and you'll be able to hire someone who is on board with your development process.
Assuming you want to hang on to her, I'd turn down (or off) the rhetoric and work on being a friend and co-worker first. If the project is a year late, she can't be feeling good about herself and it sounds like you aren't afraid to trumpet your success. That can be intimidating.
I know nothing about Scrum, however. I'm just imagining what it would be like to walk around in your co-worker's shoes.
如果你只是接近他们并简单地说“你有时间吗？听着，沟通现在真的是一个问题，我觉得我不知道你在做什么，我通常不会对这些做法抱有“敌意””真的不想再次踩到你的脚趾并花两天时间写你上周已经做过的事情，所以让我们尝试一下X，你觉得怎么样？”。 要有同情心，不要容忍“坏苹果”，这就是我敏捷工作场所的方式，许多问题已经开始消失。 我们绝不是 100% XP 或 100% Scrum 兼容的地方，因为我们只是使用任何有效且需要的东西。
beaudetious, buddy,
I would really suggest you read Steve Yegge's blog called "Good Agile, Bad Agile". It's an oldy but a goody, and I think it's a must read for anyone - like myself about 2 months ago - who gets a little let's say "over-eager" to agile-up their workplace. Agile offers a lot of good practices, but you have to take them all with a grain of salt and adopt what you're lacking and skip out on all the other crud that might be unuseful for a particular situation - e.g. the daily scrum. If your co-worker would just like to code in quiet (read Peopleware for why this is a good thing) and she's being a productive team member quit bugging her with your scrumming a let her work in whatever way she likes most.
People are usually less "hostile" about these practices if you just approach them and simply say "Do you have a sec? Listen, communication is really a problem right now, I feel like I don't know what you're doing and I really don't want to step on your toes again and spend two days writing something you already did like last week, so let's work on this. I'd like to try X, what do you think?". Be compassionate and don't tolerate "bad apples", that's literally how I agiled up my workplace, and many problems have started evaporating. We're by no means an 100% XP or 100% Scrum compliant place, because we just use whatever works and was needed.
While Scrum other agile methodologies like it embody a lot of good practices, sometimes giving it a name and making it (as many bloggers have commented on) a "religion" that must be adopted in the workplace is rather offputting to a lot of people, including myself.
It depends on what your options and commitments are, but I know I'd be a lot more keen on accepting ideas because they are good ideas, not because they are a bandwagon. Try implementing/drawing her in to the practices one at a time, by showing her how they can improve her life and workflow as well.
Programmers love cool things that help them get stuff done. They hate being preached at or being asked to board what they see as a bandwagon. Present it as the former rather than the latter. (It goes without saying, make sure it actually IS the former)
Edit: another question
I've never actually worked for a place that used a specific agile methodology, though I'm pretty happy where I'm at now in that we incorporate a lot of agile practices without the hype and the dogma (best of both worlds, IMHO).
But I was just reading about Scrum and, is a system like that even beneficial for a 2 person team? Scrum does add a certain amount of overhead to a project, it seems, and that might outweigh the benefits when you have a very small team where communication and planning is already easy.
I'm not sure Scrum is the central issue here; I'm guessing she feels threatened by the new guy bringing in a lot of new ideas and stirring things up. I've been in that situation before as the new person bringing in a new perspective on things, and sometimes it's just difficult to immediately bring those existing people around to a new way of thinking. It often requires a culture shift which doesn't happen overnight.
Try to get her input and opinion on things as much as possible, and try to show that you respect that she has been on the team longer than you. If after a while she still doesn't participate, then all you can do is mention it to your Manager and let them take it from there.
I think the key would be to help her understand why you are doing Scrum in the first place. I guess you have your reasons, so why not tell her? You are likely to get resistance towards any change if the people involved don't understand why there is change or what they will benefit from it. If you can explain your reasons for using Scrum, and the following benefits, to her in a way that relates to her everyday work, I think she is more likely to adapt a more positive attitude towards it.
If she sees no value in the Scrum process, or doesn't understand how it relates to her, she probably won't care about it.
I think one of the most important concepts for someone to understand regarding Scrum is the fact that you are working as a group and commit to your project as a group, not as individuals. For many people, this is the hardest thing to grasp, since they are so used to living in "their own World".
Continue your efforts to involve the other developer. Remember you are the one who wants to make this change. Ask for help with problems you have. Invite them to the daily stand up meeting. I currently do the planning for the daily stand up and I make sure all the pigs and chickens are invited. If you are the lead on the project it is up to you to address the situation and take a risk. Put yourself out there.
发布评论
评论（7）
简单的。 不要谈论 scrum。 不要对她使用 scrum。 相反，采用 Scrum 的基本原则（例如，目的而不是应用程序）并创建不同的方法来适应她的工作方式，但具有 Scrum 的微妙色彩。
每个人都是不同的，很多程序员不喜欢 Scrum。 我不会强迫他们这样做，因为那只会适得其反。 我建议找出开发过程中的问题（以非 Scrum 的方式），看看是否能让她同意这些问题的存在，然后询问她她认为什么是好的解决方案。 她的合作和对该过程的投入对于她的合作至关重要，如果她不支持，她就不会成为公民。
从那时起，您有望创建某种准混合 Scrum + 她的流程方法，在该流程中，你们都可以就前进的方向达成一致。
Simple. Don't talk about scrum. Don't use scrum on her. Instead take the underlying principles of scrum (e.g. the purpose as opposed to the application) and create different approaches that accommodate her way of working but have subtle tints of scrum.
All humans are different and a lot of programmers dislike scrum. I wouldn't force it upon them as that would just be counter-productive. I'd suggest identifying the problems in the development process (in a non-scrum fashion), see if you can get her to agree that the issues exist, then ask her what she thinks would be a good solution. Her co-operation and input into the process is essential to her co-operation, if she doesn't have buy-in she wont become a citizen.
From there on in you can hopefully create some sort of quasi-hybrid scrum + her approach to the process where you can both agree on the way forward.
哎呀！谁愿意在如此压抑的环境中工作？如果你幸运的话，她正在发送简历，
假设你想留住她， 你就可以雇用一个参与你的发展过程的人。我会拒绝（或关闭）这些言辞，首先努力成为朋友和同事。如果项目晚了一年，她就不会自我感觉良好，而且听起来你并不害怕。宣扬你的成功可能会让人感到害怕，
但是我只是想象一下站在你同事的立场上走来走去会是什么样子。
Yikes! Who would ever want to work in such an oppressive environment? If you're lucky, she's sending around her resume and you'll be able to hire someone who is on board with your development process.
Assuming you want to hang on to her, I'd turn down (or off) the rhetoric and work on being a friend and co-worker first. If the project is a year late, she can't be feeling good about herself and it sounds like you aren't afraid to trumpet your success. That can be intimidating.
I know nothing about Scrum, however. I'm just imagining what it would be like to walk around in your co-worker's shoes.
漂亮，伙计，
我真的建议你阅读 Steve Yegge 的博客 “好的敏捷，坏的敏捷”。 这是一本老书，但却是一本好书，我认为对于任何人来说，这都是必读的——就像两个月前的我一样——谁有点“过于渴望”敏捷他们的工作场所。 敏捷提供了许多好的实践，但您必须对它们持保留态度，采用您所缺乏的内容，并跳过所有其他可能对特定情况无用的内容 - 例如每日例会。 如果你的同事只是想安静地编码（请阅读 Peopleware 了解为什么这是一件好事），并且她是一名高效的团队成员，请不要用你的混乱来烦扰她，让她以她最喜欢的方式工作。
如果你只是接近他们并简单地说“你有时间吗？听着，沟通现在真的是一个问题，我觉得我不知道你在做什么，我通常不会对这些做法抱有“敌意””真的不想再次踩到你的脚趾并花两天时间写你上周已经做过的事情，所以让我们尝试一下X，你觉得怎么样？”。 要有同情心，不要容忍“坏苹果”，这就是我敏捷工作场所的方式，许多问题已经开始消失。 我们绝不是 100% XP 或 100% Scrum 兼容的地方，因为我们只是使用任何有效且需要的东西。
beaudetious, buddy,
I would really suggest you read Steve Yegge's blog called "Good Agile, Bad Agile". It's an oldy but a goody, and I think it's a must read for anyone - like myself about 2 months ago - who gets a little let's say "over-eager" to agile-up their workplace. Agile offers a lot of good practices, but you have to take them all with a grain of salt and adopt what you're lacking and skip out on all the other crud that might be unuseful for a particular situation - e.g. the daily scrum. If your co-worker would just like to code in quiet (read Peopleware for why this is a good thing) and she's being a productive team member quit bugging her with your scrumming a let her work in whatever way she likes most.
People are usually less "hostile" about these practices if you just approach them and simply say "Do you have a sec? Listen, communication is really a problem right now, I feel like I don't know what you're doing and I really don't want to step on your toes again and spend two days writing something you already did like last week, so let's work on this. I'd like to try X, what do you think?". Be compassionate and don't tolerate "bad apples", that's literally how I agiled up my workplace, and many problems have started evaporating. We're by no means an 100% XP or 100% Scrum compliant place, because we just use whatever works and was needed.
虽然 Scrum 等其他敏捷方法论体现了许多良好的实践，但有时给它起一个名字并使其（正如许多博主评论的那样）成为工作场所必须采用的“宗教”，这会让很多人感到反感，包括我自己。
这取决于你的选择和承诺，但我知道我会更热衷于接受想法，因为它们是好想法，而不是因为它们是潮流。 尝试一次实施/吸引她一项实践，向她展示这些实践如何改善她的生活和工作流程。
程序员喜欢帮助他们完成工作的酷炫事物。 他们讨厌被人说教，或者被要求加入他们认为是跟风的东西。 将其呈现为前者而不是后者。 （不用说，确保它实际上是前者）
编辑：另一个问题
我从未真正在使用特定敏捷方法的地方工作过，尽管我很高兴我在那里工作现在，我们整合了许多敏捷实践，没有炒作和教条（两全其美，恕我直言）。
但我刚刚读到了有关 Scrum 的内容，这样的系统对于 2 人团队是否有益？ Scrum 似乎确实给项目增加了一定的开销，而且当您的团队规模很小且沟通和规划已经很容易时，这可能会超过其带来的好处。
While Scrum other agile methodologies like it embody a lot of good practices, sometimes giving it a name and making it (as many bloggers have commented on) a "religion" that must be adopted in the workplace is rather offputting to a lot of people, including myself.
It depends on what your options and commitments are, but I know I'd be a lot more keen on accepting ideas because they are good ideas, not because they are a bandwagon. Try implementing/drawing her in to the practices one at a time, by showing her how they can improve her life and workflow as well.
Programmers love cool things that help them get stuff done. They hate being preached at or being asked to board what they see as a bandwagon. Present it as the former rather than the latter. (It goes without saying, make sure it actually IS the former)
Edit: another question
I've never actually worked for a place that used a specific agile methodology, though I'm pretty happy where I'm at now in that we incorporate a lot of agile practices without the hype and the dogma (best of both worlds, IMHO).
But I was just reading about Scrum and, is a system like that even beneficial for a 2 person team? Scrum does add a certain amount of overhead to a project, it seems, and that might outweigh the benefits when you have a very small team where communication and planning is already easy.
我不确定 Scrum 是这里的中心问题； 我猜她对新人带来的许多新想法和搅局感到威胁。 我以前也遇到过这种情况，作为新人带来对事物的新视角，有时很难立即让现有的人接受新的思维方式。 它通常需要文化转变，而这种转变不是一朝一夕就能发生的。
尝试尽可能多地听取她对事情的意见和看法，并尝试表明您尊重她在团队中的时间比您长。 如果一段时间后她仍然不参加，那么您所能做的就是向您的经理提及并让他们从那里接受。
I'm not sure Scrum is the central issue here; I'm guessing she feels threatened by the new guy bringing in a lot of new ideas and stirring things up. I've been in that situation before as the new person bringing in a new perspective on things, and sometimes it's just difficult to immediately bring those existing people around to a new way of thinking. It often requires a culture shift which doesn't happen overnight.
Try to get her input and opinion on things as much as possible, and try to show that you respect that she has been on the team longer than you. If after a while she still doesn't participate, then all you can do is mention it to your Manager and let them take it from there.
我认为关键是帮助她理解你为什么要做 Scrum。 我想你也有你的理由，为什么不告诉她呢？ 如果相关人员不明白为什么要进行变革或者他们会从中受益，那么任何变革都可能会遭到抵制。 如果你能用与她日常工作相关的方式向她解释使用 Scrum 的原因以及以下好处，我认为她更有可能对此采取更积极的态度。
如果她认为 Scrum 流程没有价值，或者不明白它与她有何关系，她可能不会关心它。
我认为人们需要理解的关于 Scrum 的最重要的概念之一是，你作为一个团队工作，并作为一个团队而不是个人致力于你的项目。 对于很多人来说，这是最难掌握的事情，因为他们已经习惯了生活在“自己的世界”中。
I think the key would be to help her understand why you are doing Scrum in the first place. I guess you have your reasons, so why not tell her? You are likely to get resistance towards any change if the people involved don't understand why there is change or what they will benefit from it. If you can explain your reasons for using Scrum, and the following benefits, to her in a way that relates to her everyday work, I think she is more likely to adapt a more positive attitude towards it.
If she sees no value in the Scrum process, or doesn't understand how it relates to her, she probably won't care about it.
I think one of the most important concepts for someone to understand regarding Scrum is the fact that you are working as a group and commit to your project as a group, not as individuals. For many people, this is the hardest thing to grasp, since they are so used to living in "their own World".
继续努力让其他开发人员参与进来。 请记住，您是想要做出这一改变的人。 遇到问题时寻求帮助。 邀请他们参加每日站立会议。 我目前负责每日站会的规划，并确保所有的猪和鸡都被邀请。 如果您是该项目的负责人，则需要您来解决该情况并承担风险。 把自己放在那里。
Continue your efforts to involve the other developer. Remember you are the one who wants to make this change. Ask for help with problems you have. Invite them to the daily stand up meeting. I currently do the planning for the daily stand up and I make sure all the pigs and chickens are invited. If you are the lead on the project it is up to you to address the situation and take a risk. Put yourself out there.