"Publishing" in (my understanding of) the agile sense doesn't necessarily mean "publishing to market". "Agile" primarily focuses on the project management, usually for one-off developments and not for mass-market software. Even when developing for the mass-market, publishing early (within your company) helps because you can avoid late integration problems and start usability testing early.
I don't draw the line, the product owner has that responsibility. I'm in the group building the product but I'm not the one to determine what is the minimum feature set to release into the wild. The half-baked idea has merit in that if the stakeholders don't understand "Agile" then they may not like the results as the whole point is to try to put in what they want in an orderly manner. On the other hand, if they do understand the point of "Agile" then they will give feedback that can be used to determine where the focus should be, fixing bugs, polishing the application, or implementing features/enhancements.
发布评论
评论（2）
（我的理解）敏捷意义上的“发布”并不一定意味着“发布到市场”。 “敏捷”主要关注项目管理，通常用于一次性开发，而不是大众市场软件。 即使在针对大众市场进行开发时，尽早发布（在公司内部）也会有所帮助，因为您可以避免后期集成问题并尽早开始可用性测试。
"Publishing" in (my understanding of) the agile sense doesn't necessarily mean "publishing to market". "Agile" primarily focuses on the project management, usually for one-off developments and not for mass-market software. Even when developing for the mass-market, publishing early (within your company) helps because you can avoid late integration problems and start usability testing early.
我不划清界限，产品负责人有责任。 我属于构建该产品的团队，但我不是确定要发布到野外的最低功能集的人。 这个不成熟的想法的优点在于，如果利益相关者不理解“敏捷”，那么他们可能不喜欢结果，因为重点是尝试以有序的方式投入他们想要的东西。 另一方面，如果他们确实理解“敏捷”的要点，那么他们将提供反馈，这些反馈可用于确定重点应该在哪里、修复错误、完善应用程序或实现功能/增强。
I don't draw the line, the product owner has that responsibility. I'm in the group building the product but I'm not the one to determine what is the minimum feature set to release into the wild. The half-baked idea has merit in that if the stakeholders don't understand "Agile" then they may not like the results as the whole point is to try to put in what they want in an orderly manner. On the other hand, if they do understand the point of "Agile" then they will give feedback that can be used to determine where the focus should be, fixing bugs, polishing the application, or implementing features/enhancements.