Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 10 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(3)
我之前已经建议过,并且会再次建议 - 敏捷开发的艺术 是一本很棒的书。
Mike Cohn 的应用的用户故事也是一本不错的读物。
About Face 总是建议用于交互设计,但我发现它有点乏味阅读。
至于可以帮助您“了解现代电子商务业务”的东西……您为什么不与了解该领域的人交谈呢?
另一件令我印象深刻的事情是,您似乎在不了解领域或需求的情况下却设法列出了技术选择列表。
I've suggested it before and I'll suggest it again - The Art of Agile Development is a great book.
Mike Cohn's User Stories Applied is also a good read.
About Face is always suggested for interaction design but I've found it a bit dull to read.
As for something that will help you 'understand modern ecommerce business' ... why aren't you talking to someone who understands the field?
The other thing that strikes me is how you've managed to come up with a list of technology choices without, it seems, having an understanding of the domain or the requirements.
我建议您使用敏捷估算和规划来了解如何组织项目。对于一本专注于.net的书,我建议应用领域驱动设计。还有许多其他可能有用的优秀书籍,但我会从这些开始。
另外请关注 InfoQ,获取源源不断的精彩材料和演讲。例如,这是最近关于项目指标的一项。
I would recommend Agile Estimating and Planning for an overview of how to organise the project. For a dot net focussed book I'd recommend Applying Domain-Driven Design. There are many other excellent books that could be useful, but I'd begin with those.
Additionally keep an eye on InfoQ for a constant barrage of excellent material and talks. For example, here's a recent one on project metrics.
我也强烈推荐 Shore 和 Warden 编写的《敏捷开发的艺术》一书。
从您所写的内容来看,我猜您是 Scrum 新手,所以我还会获得 Ken Schwaber 的《使用 Scrum 进行敏捷项目管理》。这是一本快速阅读的书,介绍了 Scrum 项目中的参与者。它通过案例研究和轶事进行教学。想知道谁应该创建产品待办事项列表及其目的。它就在这里。
关于产品日志的有用性有很多讨论。我喜欢此用户帖子中关于idealog的想法。我的产品日志遵循方法 A。
I too would highly recommend the Art of Agile Development book by Shore and Warden.
From what you've written i'm guessing you're new to Scrum so i'd also get Agile Project Management with Scrum by Ken Schwaber. Its a quick read and introduces the players in a Scrum project. It teaches through case studies and anecdotes. Want to know who is meant to create the product backlog and its purpose. Its in here.
There's quite a bit of discussion about the usefulness of product logs. I like the ideas about an idealog in this users post. A product log to me follows approach A.