微软Team Foundation Service 的Scrum模板中的Feature和Backlog Items 的区别【转载】

Features help us plan work better in Team Foundation Service Scrum process

【原文:http://www.nsilverbullet.net/2013/06/04/features-help-us-plan-work-better-in-team-foundation-service-scrum-process/】

Recently a new work item type named “Feature” popped up in the web UI for Team Foundation Service in both the Scrum and generic Agile process templates. Unfortunately it was not included in any of the backlogs or standard queries by default and I have been experimenting with using it for solving some issues we have been having with longer term planning and the Scrum process template and I believe I have found a good way to use them.

Looking for guidelines on how Microsoft have intended it to be used has not uncovered anything… there is no information available about it in the TFS (server) Scrum process guidance. Yesterday a new post was published on Microsofts TFS site detailing that it exists and that a new backlog has been added to display and manage features but no guidance.

This is my own guidance for when to use Features and Product Backlog Items.

Product Backlog Items represent work that can be completed within one sprint (like user stories) they are broken down into the tasks that need to be done to complete the work. PBIs are estimated to enable planning & forecasting using our velocity.

If you think that the work can be completed in a single sprint it is a Product Backlog Item.

Features represent work that cannot be completed within one sprint and instead will run over a longer period of time before it is complete (like epics). They are broken down into Product Backlog Items that we hope will fit into a single sprint. Features are not estimated as they are by definition large and unwieldily, instead they have a target date to help prioritise and plan releases over time. Features are not used in sprint planning as they are too big – only the Features children in the form of Product Backlog Items are used for sprint planning and forecasting.

If you think or know that the work cannot be completed in a single sprint then it is a Feature.

Tags – There is one more tool that has been crucial for us while working with our backlog in Team Foundation Service. Tags! Tags can be used for cross-cutting feature categorisation (like themes) or for just general indications as to what a Product Backlog Item or Feature relates to. We have been experimenting with Tags to indicate all kinds of different things but have generally landed in the following:

  • Epics (before Features became available) we tagged anything that was big and should be broken down
  • Skill-set required to work on an item (UX, UI, DB etc)
  • General categorisation to illustrate what in the mobile app the item will affect (Map, Contact, Start screen etc)

Update: I have also answered a question on StackOverflow about this read it here.

时间: 2024-11-05 16:33:47

微软Team Foundation Service 的Scrum模板中的Feature和Backlog Items 的区别【转载】的相关文章

oracle 中 cursor 与refcursor及sys_refcursor的区别 (转载)

http://blog.csdn.net/gyflyx/article/details/6889028 引用一.显式cursor 显式是相对与隐式cursor而言的,就是有一个明确的声明的cursor.显式游标的声明类似如下(详细的语法参加plsql ref doc ): cursor cursor_name (parameter list) is select ... 游标从declare.open.fetch.close是一个完整的生命旅程.当然了一个这样的游标是可以被多次open进行使用的

css中单位px和em,rem的区别[转载]

PX特点 1. IE无法调整那些使用px作为单位的字体大小: 2. 国外的大部分网站能够调整的原因在于其使用了em或rem作为字体单位: 3. Firefox能够调整px和em,rem,但是96%以上的中国网民使用IE浏览器(或内核). px像素(Pixel).相对长度单位.像素px是相对于显示器屏幕分辨率而言的.(引自CSS2.0手册) em是相对长度单位.相对于当前对象内文本的字体尺寸.如当前对行内文本的字体尺寸未被人为设置,则相对于浏览器的默认字体尺寸.(引自CSS2.0手册) 任意浏览器

Team Foundation Server 2013 with Update 3 Install LOG

[Info   @10:14:58.155] ====================================================================[Info   @10:14:58.163] Team Foundation Server Administration Log[Info   @10:14:58.175] Version  : 12.0.30723.0[Info   @10:14:58.175] DateTime : 10/03/2014 18:1

VSTS中版本控制系统Git与TFVC的区别

VSTS(Visual Studio Team Services) VSTS简单说就是微软TFS(Team Foundation Services)的升级云版,不用像TFS需要在企业内部服务器上部署,并且是免费提供给用户使用的. 每个有微软账号(也是免费注册的)的用户都可以申请VSTS,官网申请入口.当然,免费用户是有一定限制的,比如:每个项目的成员不能超过5个等.不过一般中小型开发项目,5个人也够用了. VSTS有一点比GitHub好,免费用户也可以拥有private空间:GitHub上免费的

在域信任环境中使用 Team Foundation Server (TFS 2013)

原文:在域信任环境中使用 Team Foundation Server (TFS 2013) 1. 用户情景和方案: XX公司的大部分软件产品通过软件外包的方式由开发商完成.为加强对软件开发的进度和质量管理,XX公司部署了一套基于微软TFS 2013的研发平台,并将这个平台与活动目录域test.local集成在一起,在 test.local中为所有软件外包人员创建了登陆账户. 但是XX公司内部已经部署了一套用于企业管理的活动目录域test2.local.为了避免在研发环境的域(test.loca

在Sublime中集成Team Foundation Server (TFS),实现版本管理

Sublime是一款具有代码高亮.语法提示.自动完成且反应快速的编辑器软件,由于它开发的技术架构.丰富的插件,和轻盈而快速的编程响应,Sublime广受程序员的爱好.在C, C++, Javascript等编程邻域,许多开发人员使用Sublime作为自己的集成开发环境(IDE).在源代码的版本管理上,Sublime具有丰富的插件支持,例如SVN, Git, CVS,TFS等.在这个博客中,我给大家介绍如何使用Sublime连接Team Foundation Server,实现源代码的版本管理.

在Team Foundation Server中查找文件或代码

很多用户在使用TFS的过程中,都抱怨一个问题,不能在TFS的代码库中查找文件!虽然TFS的所有数据都存储在数据库中(SQL Server),但是由于代码文件存储的特殊性,你不能通过全文搜索的功能直接在数据库里查询.当前最新版本TFS 2013 update 4和TFS Online,也没法在界面上找到与代码有关的搜索功能. 但是通过调研,发现TFS代码库中的查询功能,有以下几中方法: 1. 利用TFS代码的命令行工具TF.exe查询代码库中文件 TFS代码的命令行工具TF.exe几乎可以完成在U

你好,Azure DevOps Server 2019;再见,Team Foundation Server

微软正式发布Azure DevOps Server 2019的第一个版本,作为Team Foundation Server (TFS)2018的升级版本和替代产品. 这是目前市面上唯一一款将产品名称冠上DevOps的企业级软件研发平台产品.产品名称的变化,强化了微软在研发运维工具上的投入,体现了微软研发管理平台产品在软件开发管理.质量管理和自动化交付和测试方面的巨大提升. 作为TFS系统的下一代产品,DevOps Server 2019不只是在名称的改动,在用户习惯.持续集成方面做出了巨大调整,

TFS(Team Foundation Server)介绍和入门

在本文的两个部分中,我将介绍Team Foundation Server的一些核心特征,重点介绍在本产品的日常应用中是怎样将这些特性结合在一起使用的. 作为一名软件开发者,在我的职业生涯中,我常常会用到支持软件开发过程的大量开发工具,如版本号控制工具.漏洞跟踪包.生成脚本语言.单元測试框架和需求分析工具等等.在.NET平台上,大量的支持工具可以非常好地独立工作,可是,为了使得各种工具之间都够互相协作,还是常常须要一些手动工作. 随着Visual Studio产品线中Team Foundation