Yes, you can use agile to develop software that doesn't have a front end UI used by human users. First, because you don't have to use user stories to be agile. Even Scrum doesn't prescribe that the backlog has to be expressed in user stories. It just says there should be a backlog, it should have one order of priority and items on top of it should be small enough to fit into one sprint. They can be expressed in any way that is understandable to both the Product Owner and the team.
But, second, you can write user stories for libraries too. You just think of potential pieces of software as roles - or even create imaginary personas that could be using this library directly. "As a text editor I can call this library to encode strings in Base64" would be an off the bat example of the former technique.
To sum it all up: any type of software can be developed with agile, user stories are not key to agile - they are just one pretty useful technique frequently used by agile teams.
发布评论
评论（4）
是的，您可以使用敏捷开发没有人类用户使用的前端 UI 的软件。首先，因为您不必使用用户故事来保持敏捷。即使 Scrum 也没有规定积压工作必须在用户故事中表达。它只是说应该有一个积压工作，它应该有一个优先级顺序，并且其之上的项目应该足够小以适合一个冲刺。它们可以用产品负责人和团队都能理解的任何方式来表达。
但是，其次，您也可以为库编写用户故事。您只需将潜在的软件片段视为角色 - 甚至创建可以直接使用该库的虚构角色。 “作为文本编辑器，我可以调用这个库来对 Base64 中的字符串进行编码”将是前一种技术的一个即时示例。
总而言之：任何类型的软件都可以通过敏捷开发，用户故事并不是敏捷的关键——它们只是敏捷团队经常使用的一种非常有用的技术。
Yes, you can use agile to develop software that doesn't have a front end UI used by human users. First, because you don't have to use user stories to be agile. Even Scrum doesn't prescribe that the backlog has to be expressed in user stories. It just says there should be a backlog, it should have one order of priority and items on top of it should be small enough to fit into one sprint. They can be expressed in any way that is understandable to both the Product Owner and the team.
But, second, you can write user stories for libraries too. You just think of potential pieces of software as roles - or even create imaginary personas that could be using this library directly. "As a text editor I can call this library to encode strings in Base64" would be an off the bat example of the former technique.
To sum it all up: any type of software can be developed with agile, user stories are not key to agile - they are just one pretty useful technique frequently used by agile teams.
与您对基于业务的需求所做的相同，除了需求由 API 消费者/技术人员优先考虑？
The same as you do for business-based requirements, except the reqs are prioritized by the API consumers/technical people?
如果您谈论的是 Spring 或游戏引擎，那么您仍然可以从客户/产品所有者的角度来编写您的故事。
那就是您可以谈论您的 API、其他开发人员将如何使用接口或您的暴露的内容黑匣子
If you're talking about Spring or Game engine, you still have a customer/product owner point of view to write your stories from..
That's you'd talk about your API, how other developers will use interfaces or what is exposed of your black-box
许多组件供应商使用 Scrum 来管理其库的开发。
我可以告诉您，StackOverflow.com 的两个赞助商正在积极使用它。
They are many component vendors that use Scrum to manage the development of their libraries.
I can tell you two of the StackOverflow.com sponsors are using it actively.