对于产品负责人来说,新数据库的要求非常模糊。 在与客户进行了长时间的讨论后,你发现你对产品或构建产品的过程没有足够的了解,难以继续推进。 作为敏捷实践者,接下来应该怎么做?The requirements for the new database are very vague to the product owner. After lengthy discussions with the customer, you discovered that you don’t have enough knowledge about the product or the process of building the product to move forward. As an agile practitioner, what should you do next?

【单选题】
A 开始创建你的第一个用户故事,要求最终会发展清晰 Start creating your first user stories and requirements will eventually evolve
B “由于项目中的技术不确定性,开始刺探以理清当前的风险 Start a spike to clarify the current risk due to the technical uncertainty within the project #25.
C “继续细化待办事项列表,并将情况告知高级利益相关方” Carry on with backlog refinement and inform senior stakeholders about the situation
D “从零开始冲刺,你可以在其中完成项目设置、基础设施配置、项目文档存储库的设置、工具标准化和团队建设” Start a sprint Zero where you complete project setup, infrastructure provisioning, setting up of project document repository, standardizing tools, and building your team

查看更多