问HN：一个小团队能省去的最少流程是什么？
在我们围坐在屏幕前之前，我们曾围坐在篝火旁讲述故事。我们天生就是讲故事的人，这正是我们与他人建立联系和理解世界的基本方式。
我一直在思考一个小团队如何保持简单高效，同时又能保持生产力和一致性。以下是我的看法：
1) 故事展开。定期召开会议，团队讨论在下次会议之前需要完成的下一步工作。
2) 情节。一个在代码库中的纯文本文档，显示已完成的工作、待完成的任务以及相关的备注或评论。
以下是项目的纯文本故事/叙述示例：
```
# 项目：云成本仪表板
为团队提供便捷的云成本数据访问。
## 集成
DONE 云成本API已与计费系统集成 @bob
## 仪表板
仪表板必须从AWS、Azure和GCP拉取数据以进行比较。
TODO 设置云成本报告仪表板 @alice
TODO 培训团队如何使用仪表板 @alice
```
以下规则适用：
- 任务状态为TODO或DONE，并且每个任务恰好占一行。
- 添加@姓名以分配任务。
- 新的TODO任务添加在底部（因此请查看底部以选择任务）。
- 可以随意在文件中添加任何自由文本/备注等，以提供上下文和见解。
随着项目的推进，故事逐渐展开并自我记录。
额外提示：使用任务行作为提交信息。
一些问题：
- 这种方法是否足以让小团队保持生产力和专注？
- 在小团队的背景下，有哪些必要的元素缺失？
期待听到你的想法！
查看原文
Before we sat around screens we sat around campfires telling stories. We’re hardwired to be storytellers, and that’s how we fundamentally connect with other people and understand the world.<p>I’ve been thinking about how KISS a small team could go and still stay productive and aligned. This is my take:<p>1) The story unfolds. Repeating meetings where team hash out the next steps to be done before the next meeting<p>2) The plot. A plain text document in the repo showing what has been done, what needs doing, and any related notes or comments<p>Here is an example of the plain text story/narrative of the project:<p>```<p># Project: Cloud Cost Dashboard<p>Enable easy access to cloud cost data for the team.<p>## Integration<p>DONE Cloud cost API integrated with billing system @bob<p>## Dash board<p>Dashboard must pull data from AWS, Azure, and GCP for comparison.<p>TODO Set up a cloud cost reporting dashboard @alice
TODO Train team on how to use the dashboard @alice<p>```<p>The following rules apply:<p>- A task is either in status TODO or DONE and it fits exactly on one line<p>- Add @name to assign tasks<p>- New TODOs are added at the bottom (so look there for tasks to pick)<p>- Feel free to add any free text/notes etc to the file to provide context and insight<p>As the project progresses the story unfolds and self documents.<p>BONUS: Use the task line for the commit message<p>Some questions:<p>- Does this approach seem like enough to keep a small team productive and focused?<p>- What essentials are missing (given a small team context)?<p>Would love to hear your thoughts!