我们的博客

这是来自VersionOne的Joe Woods的客座博客文章… When I first started using agile project management, my stories didn’t have enough detail. In my office we use 敏捷 to manage our marketing department with 2 week iterations. Even from the beginning, I could see the value of bite size goals that you could accomplish in a short

我最近在一篇博客文章中发表评论，询问敏捷用户故事，主题，史诗和功能之间的区别，以及这些术语之间的关系或层次结构？诚然，这有点令人困惑，因为这些短语通常可以互换使用（至少我是这样）。这里’我认为有什么区别… A user story may

敏捷 software development teams often use User Stories as a simple and concise way to express user requirements. Ideally these User Stories are broken down as small as possible, whilst also trying to minimise dependencies. Naturally, though, as you break User Stories down smaller, they become increasingly inter-dependent. Like most things in software development, it’是一种平衡的行为。打破

Tyner Blain的Scott Sehlhorst是我最喜欢的博客之一。他’撰写了一篇关于“用户故事与用例”的出色文章。当我第一次使用用例时，我喜欢它们…我喜欢他们对功能进行了如此清晰的描述，以及每个用例可以独立存在的事实。他们真的很容易

乔·奥坎波（‘AgileJoe’）最近写了一个他称之为的概念‘Role Storming‘… I’我不确定我喜欢这个名字–听起来有点时髦– but I think the concept is really great! When you first start a project, you need to build out the initial 产品 Backlog. 角色风暴 would be a great way to start, ensuring the

在过去的几周里，我’关于写好的用户故事，我写了很多–您可以在此处查看所有内容：用户故事。用户故事是一种在整个项目中捕获用户需求的简单方法–替代所有预先编写冗长的需求规范的方法。作为编写用户故事的人们的指导，他们可以遵循以下基本结构：