I think there's benefit to be gained by any method that helps you develop goals, tasks, keep on top of work and deliver something often.
Your individual work-products would gain the same advantages that teams gain with scrum:
You'd get something done every {Sprint Iteration Period Here}, something you can hand off and say "This is now ready".
Your estimation technique will start to improve with reflection and retrospectives
You'll start to plan your day and make commitments to yourself about getting things done, so again your estimation of your capacity will increase
Retrospectives will formalize improvement of your personal work process. You'll start actively improving, removing and adapting to suit you and your individual needs.
You wouldn't be able to rely on other team members to help out, which is a bit annoying, and you wouldn't have a product owner, Scrum master or a backlog to pick tasks from. You may not even be in a position to make decisions on what to work on next. But I think the formal discipline and reflection is helpful for all craft practitioners, at all levels, alone or in groups.
And who knows, you might even inspire your team to Scrum it up once they see what great results you're getting.
I would suggest that you use Extreme Programming instead, as that works better for one programming than a decidely team-based process.
Then you can get the benefits of being more agile, but if your team is not agile then you will have some issues due to the use of a different paradigm.
对我来说，最重要的关键是获得主管的支持。尝试进行某种 Sprint 但却多次中断可能会很困难（据说 XP 团队可以更好地处理这个问题，但我认为没有任何开发人员会这样做。）。另外，不要忘记包括高级用户（他们可以是测试人员）或可以用作产品负责人的其他部门的成员。我喜欢与其他用户坐在一起进行一种结对编程（好吧，他们不编码），我可以在编码时提出问题并进行快速演示以获得反馈。当我努力创建规范时，这很有帮助，因为那些请求该应用程序的人很难告诉我他们想要什么。
For me, the biggest key was getting buy-in from my supervisor. It can be tough to try and have some sort of Sprint only to have it interupted multiple times (Supposedly XP teams handle this better, but I don't think any developer does.). Also, don't forget to include either power users (they could be testers) or members of other departments that could be used as Product Owners. I like to sit with other users and do a type of paired programming (OK they don't code) where I can ask questions while coding and do quick demos to get feedback. This helps when I'm struggling to create specs because those requesting the app are having a hard time telling me what they want.
Even if it's just you in the daily stand-up, it can be scrum.
If you compare yesterday's planned with actual and define today's plans -- without talking to other people -- that's still a kind of daily stand-up.
I'd say that what you're doing probably is scrum if you're following the daily-sprint-release cycles; even if there aren't a any other people to talk to each morning.
For the best thing to come out of learning Scrum is the concept of involving the customer early and often. That way there are no nasty "that's actually not what we wanted" moments when you deliver to the customer after six months hard work.
发布评论
评论（5）
我认为任何可以帮助你制定目标、任务、掌控工作并经常交付成果的方法都会带来好处。
您的个人工作产品将获得与团队通过 Scrum 获得的相同优势：
你将无法依赖其他团队成员来提供帮助，这有点烦人，而且你也不会有产品负责人、Scrum 管理员或待办事项列表可供选择任务。您甚至可能无法决定下一步该做什么。但我认为正式的纪律和反思对所有级别的手工艺从业者，无论是单独还是团体都有帮助。
谁知道呢，一旦您的团队看到您所取得的出色成果，您甚至可能会激励他们进行 Scrum 活动。
I think there's benefit to be gained by any method that helps you develop goals, tasks, keep on top of work and deliver something often.
Your individual work-products would gain the same advantages that teams gain with scrum:
You wouldn't be able to rely on other team members to help out, which is a bit annoying, and you wouldn't have a product owner, Scrum master or a backlog to pick tasks from. You may not even be in a position to make decisions on what to work on next. But I think the formal discipline and reflection is helpful for all craft practitioners, at all levels, alone or in groups.
And who knows, you might even inspire your team to Scrum it up once they see what great results you're getting.
我建议您使用极限编程，因为这对于一个编程来说比完全基于团队的过程更有效。
然后，您可以获得更加敏捷的好处，但如果您的团队不敏捷，那么您将因使用不同的范式而遇到一些问题。
I would suggest that you use Extreme Programming instead, as that works better for one programming than a decidely team-based process.
Then you can get the benefits of being more agile, but if your team is not agile then you will have some issues due to the use of a different paradigm.
对我来说，最重要的关键是获得主管的支持。尝试进行某种 Sprint 但却多次中断可能会很困难（据说 XP 团队可以更好地处理这个问题，但我认为没有任何开发人员会这样做。）。另外，不要忘记包括高级用户（他们可以是测试人员）或可以用作产品负责人的其他部门的成员。我喜欢与其他用户坐在一起进行一种结对编程（好吧，他们不编码），我可以在编码时提出问题并进行快速演示以获得反馈。当我努力创建规范时，这很有帮助，因为那些请求该应用程序的人很难告诉我他们想要什么。
For me, the biggest key was getting buy-in from my supervisor. It can be tough to try and have some sort of Sprint only to have it interupted multiple times (Supposedly XP teams handle this better, but I don't think any developer does.). Also, don't forget to include either power users (they could be testers) or members of other departments that could be used as Product Owners. I like to sit with other users and do a type of paired programming (OK they don't code) where I can ask questions while coding and do quick demos to get feedback. This helps when I'm struggling to create specs because those requesting the app are having a hard time telling me what they want.
即使只有你一个人参加日常站立会议，也可能会出现争吵。
如果你将昨天的计划与实际进行比较并定义今天的计划 - 不与其他人交谈 - 这仍然是一种每日站立会议。
我想说，如果您遵循每日冲刺发布周期，那么您所做的可能就是 Scrum；即使每天早上没有其他人可以交谈。
Even if it's just you in the daily stand-up, it can be scrum.
If you compare yesterday's planned with actual and define today's plans -- without talking to other people -- that's still a kind of daily stand-up.
I'd say that what you're doing probably is scrum if you're following the daily-sprint-release cycles; even if there aren't a any other people to talk to each morning.
您好，
学习 Scrum 的最佳效果是尽早且经常让客户参与其中的概念。这样，当您经过六个月的努力工作后向客户交付产品时，就不会出现“这实际上不是我们想要的”的令人讨厌的时刻。
HTH
欢呼，
G'day,
For the best thing to come out of learning Scrum is the concept of involving the customer early and often. That way there are no nasty "that's actually not what we wanted" moments when you deliver to the customer after six months hard work.
HTH
cheers,