Yes, Agile is a lot about Getting Things Done (the real meaning, not the book, see below). It's about getting trough procrastination too. I've found that Agile methodologies tend to solve mostly psychological problems. In fact, most problems we encounter in software development are not technical, but psychological.
I have many projects where I'm the only one involved, and yet I've my own backlog, sprint backlog, my own information radiator, I apply the same "done" definition rules, reviews, retrospectives, ...
But no, I'm not doing standups meeting alone or with my cat :)
I've read many books about productivity improvements before I discovered agile methodologies. And what I've observed is that agile is very similar to them.
For exemple, Scrum is a lot about Getting Things Done, and others well known books on the subject.
That book certainly saved my life at a certain point. So get it and read it. It will helps you "get it", I mean, understanding what Agile means. Trying to do Agile not understanding it will leads you to failure.
Is it realistic to apply this to a lone developer who codes as a hobby (I also code for a living in a team where I have learnt agile from)? Things like stories, scheduled retrospectives, etc, can be useful (Even if I am asking myself things)?
Definitely yes and it worked for me. I have tried doing it myself and it definitely makes me more productive. A good way to try it without the need of buying a whole lot of office supplies is using ScrumWorks (google danube) which is freeware for the basic version. You can add products, releases, user stories. tasks, and see burn down charts etc.
Doing a retrospective by yourself would be a little weird and it may make people in your house think you are losing your marbles while you talk to yourself out loud but that is just my opinion. What I do is I write down the Retrospective notes on a soft document and attach it to the Sprint or a Backlog in ScrumWorks.
发布评论
评论（3）
是的，敏捷很大程度上是关于把事情做好（真正的含义，不是书本，见下文）。这也是关于如何度过拖延。我发现敏捷方法论往往能解决大部分心理问题。其实我们在软件开发中遇到的大多数问题都不是技术上的，而是心理上的。
我有很多项目，其中我是唯一参与的，但我有自己的待办事项、冲刺待办事项、我自己的信息辐射器，我应用相同的“完成”定义规则、评论、回顾……
但不，我不会单独或与我的猫一起开站立会议:)
在发现敏捷方法之前，我读过很多关于生产力提高的书籍。我观察到敏捷与它们非常相似。
例如，Scrum 包含很多关于完成事情等内容有关该主题的著名书籍。
那本书在某种程度上确实救了我的命。因此，获取并阅读它。我的意思是，它将帮助您“理解”敏捷的含义。尝试进行敏捷而不理解它会导致你失败。
Yes, Agile is a lot about Getting Things Done (the real meaning, not the book, see below). It's about getting trough procrastination too. I've found that Agile methodologies tend to solve mostly psychological problems. In fact, most problems we encounter in software development are not technical, but psychological.
I have many projects where I'm the only one involved, and yet I've my own backlog, sprint backlog, my own information radiator, I apply the same "done" definition rules, reviews, retrospectives, ...
But no, I'm not doing standups meeting alone or with my cat :)
I've read many books about productivity improvements before I discovered agile methodologies. And what I've observed is that agile is very similar to them.
For exemple, Scrum is a lot about Getting Things Done, and others well known books on the subject.
That book certainly saved my life at a certain point. So get it and read it. It will helps you "get it", I mean, understanding what Agile means. Trying to do Agile not understanding it will leads you to failure.
当然，尽管有些做法可能不适用或者可能感觉有点愚蠢。
即使你孤身一人，将你的工作分解成故事并安排你的发展时间也绝对有帮助。
无论如何，测试驱动开发实际上是一个单独的过程，并且对于独立开发人员来说当然很有用。
然而，结对编程需要精神分裂症。每日站立会议可能会进行得更快...
Ward's Wiki 几年前，这可能值得一看。
Certainly, though some of the practices may not apply or may feel a bit silly.
Breaking your work into stories and timeboxing your development can definitely help even if your all alone.
Test-Driven-Development is really an individual process anyway, and certainly is useful as a solo developer.
Pair-programming would require schizophrenia however. Daily standup meetings would probably go much more quickly...
There was some talk of this on Ward's Wiki years ago, which might be worth a look.
将其应用到一个以编码为爱好的孤独开发人员（我也在一个团队中以编码为生，在那里我学到了敏捷）是否现实？像故事、预定的回顾之类的事情可能有用（即使我问自己一些事情）？
绝对是的，它对我有用。我自己尝试过这样做，这确实让我更有效率。无需购买大量办公用品即可尝试的一个好方法是使用 ScrumWorks（谷歌 Danube），它是基本版本的免费软件。您可以添加产品、版本、用户故事。 自己做回顾
会有点奇怪，它可能会让你家里的人认为你在大声自言自语时失去了理智，但这只是我的观点。我所做的就是在软文档上写下回顾笔记，并将其附加到 ScrumWorks 中的 Sprint 或 Backlog 中。
希望这会对您有所帮助。
Is it realistic to apply this to a lone developer who codes as a hobby (I also code for a living in a team where I have learnt agile from)? Things like stories, scheduled retrospectives, etc, can be useful (Even if I am asking myself things)?
Definitely yes and it worked for me. I have tried doing it myself and it definitely makes me more productive. A good way to try it without the need of buying a whole lot of office supplies is using ScrumWorks (google danube) which is freeware for the basic version. You can add products, releases, user stories. tasks, and see burn down charts etc.
Doing a retrospective by yourself would be a little weird and it may make people in your house think you are losing your marbles while you talk to yourself out loud but that is just my opinion. What I do is I write down the Retrospective notes on a soft document and attach it to the Sprint or a Backlog in ScrumWorks.
Hoping this will help you.