I would suggest to try Scrum for start. As lightweight project management framework it should suite your small team needs. To do that less painful I would also suggest temporary hiring someone familiar with scrum (certified scrum master maybe), after 3-4 months you should be able to keep it running by yourself. Really investing in few months of experienced team member should pay off. And I don't mean analytic, consultant or whatever you call person that comes, analyzes, makes presentation, takes money and goes while you stay with a problem. I mean Team member that will work with you but also introduce scrum to you via daily practice. You could also just read some books instead, or send one or two team members to a training, but I think that having someone to incorporate Scrum into your daily work and start learning by examples is the best.
Subscribing rigidly to someone else's view of the development process isn't going to work for everyone. Start with the real basics
Get the basics of the development process right - see The Joel Test.
Track everything. Use a system like JIRA, FogBugz or so on to track all issues, features and bugs that are ever reported. Track how long you spend on each task; the information you have the better prepared you'll be.
Triage - Work with stakeholders to make sure what you are doing is actually important, rather than just what you think is important. In my experience, developers and customers often have wildly differing views!
These are very practical books that look at the whole business value chain from a software team's viewpoint, instead of being head-down in software land and ignoring business goals.
Highly recommended reading includes : The Agile Manifesto and The Pragmatic Programmer. Subsequently, you'll probably want to get familiar with Scrum software development, or Test-Driven Development. At the very least you should have:
Source Control repository
Bug tracking system
Standard set of tools for communication (A wiki tends to be popular for documentation, these days),
IDE
Testing framework
A lot of things will depend on the skills of your team and the application domain that you're seeking to go into. Get yourselves familiar with some methodologies, then practice them. Have 15 minute standing meetings at the start of the day. Develop code incrementally with a write a failing test, make it pass, repeat mindset. Etc etc.
发布评论
评论（4）
我建议先尝试 Scrum。作为轻量级项目管理框架，它应该适合您的小型团队的需求。
为了减少痛苦，我还建议暂时雇用熟悉 Scrum 的人（也许是经过认证的 Scrum Master），3-4 个月后，您应该能够自己保持运行。真正投资几个月的经验丰富的团队成员应该会得到回报。我指的不是分析、顾问或任何你所说的人，他们会来分析、做演示、拿钱然后离开，而你却一直在解决问题。我的意思是团队成员将与您一起工作，但也会通过日常练习向您介绍 Scrum。
你也可以看一些书，或者派一两个团队成员去参加培训，但我认为有人将 Scrum 融入到你的日常工作中并通过示例开始学习是最好的。
好的描述详细描述（基于日常工作）将是 Scrum 和 XP 来自战壕（替代来源）。
I would suggest to try Scrum for start. As lightweight project management framework it should suite your small team needs.
To do that less painful I would also suggest temporary hiring someone familiar with scrum (certified scrum master maybe), after 3-4 months you should be able to keep it running by yourself. Really investing in few months of experienced team member should pay off. And I don't mean analytic, consultant or whatever you call person that comes, analyzes, makes presentation, takes money and goes while you stay with a problem. I mean Team member that will work with you but also introduce scrum to you via daily practice.
You could also just read some books instead, or send one or two team members to a training, but I think that having someone to incorporate Scrum into your daily work and start learning by examples is the best.
Good description detailed description (based on daily work) would be Scrum and XP from the Trenches (alternative source).
严格遵循别人对开发过程的看法并不适合所有人。从真正的基础知识开始
Subscribing rigidly to someone else's view of the development process isn't going to work for everyone. Start with the real basics
我是运动先驱 Mary 和 Tom Poppendieck 最近出版的精益文献的忠实粉丝：
这些都是非常实用的书籍，从软件团队的角度看待整个业务价值链，而不是在软件领域埋头苦干，忽视业务目标。
I'm a huge fan of the recent Lean literature by the forerunners of the movement, Mary and Tom Poppendieck:
These are very practical books that look at the whole business value chain from a software team's viewpoint, instead of being head-down in software land and ignoring business goals.
强烈推荐阅读：《敏捷宣言》和《务实程序员》。随后，您可能想要熟悉 Scrum 软件开发或测试驱动开发。至少您应该拥有：
用于沟通（维基往往是
流行的文档，这些
天），
很多事情都取决于您团队的技能以及您想要进入的应用程序领域。让自己熟悉一些方法，然后实践它们。一天开始时举行 15 分钟的站立会议。以编写失败的测试、使其通过、重复的心态逐步开发代码。等等等等.
Highly recommended reading includes : The Agile Manifesto and The Pragmatic Programmer. Subsequently, you'll probably want to get familiar with Scrum software development, or Test-Driven Development. At the very least you should have:
for communication (A wiki tends to be
popular for documentation, these
days),
A lot of things will depend on the skills of your team and the application domain that you're seeking to go into. Get yourselves familiar with some methodologies, then practice them. Have 15 minute standing meetings at the start of the day. Develop code incrementally with a write a failing test, make it pass, repeat mindset. Etc etc.