[图解]需求排序：先做容易的还是难的

00:07:33,410 --> 00:07:36,470
很多开发人员在这里经常有问题的

143
00:07:36,910 --> 00:07:38,020
挑容易做的

144
00:07:39,170 --> 00:07:40,810
所以我看很多团队经常是什么

145
00:07:40,820 --> 00:07:44,220
做一大堆什么用户管理

146
00:07:44,520 --> 00:07:45,930
权限管理什么之类的

147
00:07:45,940 --> 00:07:47,290
基本数据管理这种

148
00:07:47,300 --> 00:07:52,000
先做一大堆，几十个功能

149
00:07:52,010 --> 00:07:52,960
而且很有成就感

150
00:07:52,970 --> 00:07:54,400
你看，我都做了这么多了

151
00:07:55,060 --> 00:07:58,660
结果跟愿景相关的功能一个都没有

152
00:08:00,070 --> 00:08:02,100
那不就是自己骗自己嘛

153
00:08:03,910 --> 00:08:05,320
不能说找容易的做

154
00:08:07,140 --> 00:08:09,170
也不能说，我专门找难的做

155
00:08:09,180 --> 00:08:11,010
有的开发人员是什么

156
00:08:11,020 --> 00:08:13,290
他专门找最难的做，为什么

157
00:08:13,300 --> 00:08:14,930
因为最难的是他不懂的

158
00:08:15,630 --> 00:08:18,350
然后做的过程中，他能够学到东西

159
00:08:19,130 --> 00:08:22,160
然后简历就丰富

160
00:08:22,610 --> 00:08:26,240
所以他一看这个东西涉及到

161
00:08:26,250 --> 00:08:27,480
很多他没有学过的技术

162
00:08:27,890 --> 00:08:29,200
他就喜欢去做

163
00:08:33,240 --> 00:08:37,450
但是，如果说这个东西跟愿景

164
00:08:37,460 --> 00:08:38,330
关系并不是很大

165
00:08:38,340 --> 00:08:42,020
你投大量精力去做，不值得的

166
00:08:43,050 --> 00:08:45,920
应该先做跟愿景最相关的

167
00:08:45,930 --> 00:08:48,640
跟愿景最相关的，越容易做，说明什么

168
00:08:49,210 --> 00:08:52,490
你赚大了，你看，你以最小的投入

169
00:08:52,500 --> 00:08:56,320
就轻易实现愿景目标

170
00:08:57,440 --> 00:08:58,840
那不就赚大了

171
00:08:59,840 --> 00:09:01,050
然后你爱钻研技术

172
00:09:01,060 --> 00:09:03,810
你可以把剩下的资源拿去钻研都可以

173
00:09:04,420 --> 00:09:04,720

174
00:09:04,730 --> 00:09:07,710
或者说，找另外一个更合适的系统

175
00:09:07,720 --> 00:09:09,150
结合它来钻研

176
00:09:09,400 --> 00:09:10,590
不要把它带到

177
00:09:11,530 --> 00:09:12,800
不要把这两个混在一起

178
00:09:13,010 --> 00:09:14,560
带到你这个项目里面来

179
00:09:16,420 --> 00:09:19,130
以这个为依据来排序

180
00:09:19,800 --> 00:09:20,720
一旦排错了

181
00:09:21,340 --> 00:09:22,680
钱就扔到水里面去了

182
00:09:25,050 --> 00:09:27,400
通过排序，我们就挑出一个用例来

183
00:09:28,320 --> 00:09:29,670
写用例规约了

184
00:09:30,040 --> 00:09:32,710
用例规约里面包含的内容这么多，都要写的

185
00:09:34,410 --> 00:09:36,970
这些都要写，因为这就是需求规约

186
00:09:36,980 --> 00:09:42,780
用例规约，就是以用例来组织的需求规约

187
00:09:43,680 --> 00:09:46,830
有了这个，就不用写其他的需求规约了

188
00:09:48,430 --> 00:09:51,340
除非你为了行政方面去应付别人

189
00:09:52,340 --> 00:09:54,690
凑一个出来，那就无所谓

190
00:09:54,700 --> 00:09:56,930
你随便找人炮制一个

191
00:09:56,940 --> 00:09:58,490
AI给你搞一个，都可以

192
00:09:59,010 --> 00:10:00,720
但是真正有用的，这个就够了