A Story is Sprint ready (Rally Defined) when.............

The story has well defined and testable acceptance criteria agreed with the Product Owner (PO) / Business

Specification By Example (SBE) is complete

The team understands the context and scope of the story

The team and PO can answer the question "How will we test this Story?"

The team understands how the story will be implemented -

The team has estimated and entered Story Point

We have tasks broken down for completion, including hour estimates

Answered the question - Are there any dependencies (other systems, teams, vendor feeds, technical constraints, etc.) which need to be considered when implementing this story?

Answered the question - Are any KB articles for PS required for this story?

Answered the question - Are any Training material updates required for this story?

A Story is DONE (Rally Complete) when................

All code / migration scripts complete, checked in and merged to trunk

Unit testing complete

Builds on the Continuous Integration server are green

Code peer reviewed (or pairing during build)

Test scripts written, agreed and executed with the team and PO

Required system / integration / targeted regression testing complete

All Acceptence Criteria are met

Deployed to UAT

Demo'd to the PO

PS Knowledge Base articles updated, as required

The TEAM are happy for the change to go into production

A Story is Sprint ready (Rally Defined) when.............

The story has well defined and testable acceptance criteria agreed with the Product Owner (PO) / Business

Specification By Example (SBE) is complete

The team understands the context and scope of the story

The team and PO can answer the question "How will we test this Story?"

The team understands how the story will be implemented -

The team has estimated and entered Story Point

We have tasks broken down for completion, including hour estimates

Answered the question - Are there any dependencies (other systems, teams, vendor feeds, technical constraints, etc.) which need to be considered when implementing this story?

Answered the question - Are any KB articles for PS required for this story?

Answered the question - Are any Training material updates required for this story?

A Story is DONE (Rally Complete) when................

All code / migration scripts complete, checked in and merged to trunk

Unit testing complete

Builds on the Continuous Integration server are green

Code peer reviewed (or pairing during build)

Test scripts written, agreed and executed with the team and PO

Required system / integration / targeted regression testing complete

All Acceptence Criteria are met

Deployed to UAT

Demo'd to the PO

PS Knowledge Base articles updated, as required

The TEAM are happy for the change to go into production

A Story is DONE DONE (Rally Accepted) when

Signed off received from the Product Owner

Zero known defects or approval from the PO to move forward with any defects and/or missing functionality which will be completed in subsequent sprints

SNOW approval & release management pre-requisites complete

Release notes updated as required

PS Knowledge Base articles reviewed/approved by PS, as required

A Story is (Rally) Released when

It's deployed to the production environment

Signed off received from the Product Owner

Zero known defects or approval from the PO to move forward with any defects and/or missing functionality which will be completed in subsequent sprints

SNOW approval & release management pre-requisites complete

Release notes updated as required

PS Knowledge Base articles reviewed/approved by PS, as required

A Story is (Rally) Released when

It's deployed to the production environment

Difinition Of Done的更多相关文章

  1. 场景服务只创建了 Service Difinition 和feature layer

    环境:物理机 pro1.4:虚拟机 (server + datastore + portal + adaptor) 10.4.1 发布场景服务,正常情况应portal中查看,应包含四部分内容:Serv ...

  2. android 传感器应用

    本章讲述Android开发中,传感器应用相关的知识点. 1.功能需求 做一个基于传感器的水平尺应用. 2.软件实现

  3. PHP 依赖注入,从此不再考虑加载顺序

    说这个话题之前先讲一个比较高端的思想--'依赖倒置原则' "依赖倒置是一种软件设计思想,在传统软件中,上层代码依赖于下层代码,当下层代码有所改动时,上层代码也要相应进行改动,因此维护成本较高 ...

  4. 重载赋值运算符 && 对象

    class CMessage { private: char * m_pMessage; public: void showIt()const { cout << m_pMessage & ...

  5. PHP 依赖注入 (转)

    说这个话题之前先讲一个比较高端的思想--'依赖倒置原则' "依赖倒置是一种软件设计思想,在传统软件中,上层代码依赖于下层代码,当下层代码有所改动时,上层代码也要相应进行改动,因此维护成本较高 ...

  6. linux设备驱动程序该添加哪些头文件以及驱动常用头文件介绍(转)

    原文链接:http://blog.chinaunix.net/uid-22609852-id-3506475.html 驱动常用头文件介绍 #include <linux/***.h> 是 ...

  7. PowerDesigner(六)-物理数据模型(PDM逆向工程)(转)

    物理数据模型PDM 物理数据模型(Physical Data Model,PDM):在数据库的逻辑结构设计好之后,就需要完成其物理设计,PDM就是为实现这一目的而设计的. 物理数据模型是以常用的DBM ...

  8. 译 - 第 1 章:EF入门

    章节信息 Entity Framework 6 Recipes 第二版第一章: Chapter 1: Getting Started with Entity Framework ----------- ...

  9. Python全栈开发-Day3-Python基础3

    本节内容 1. 函数基本语法及特性 2. 参数与局部变量 3.递归 4.函数式编程介绍 5.高阶函数 1.函数基本语法及特性 三种编程范式: 1.面向过程:过程——> def 2.面向对象:类— ...

随机推荐

  1. angularjs自带过滤器

    filter: filter过滤器第一个参数若是对象: <ul> <li ng-repeat="friend in friends | filter:{'name':'Jo ...

  2. Math类

    Math类:用于执行基本数学运算的方法 方法: public static int abs(int a):绝对值 public static double ceil(double a):向上取整   ...

  3. 面试题目——《CC150》高等难题

    面试题18.1:编写一个函数,将两个数字相加.不得使用+或其他算数运算符. package cc150.high; public class Add { public static void main ...

  4. live555库中的testH264VideoStreamer实例

    1.h264文件的推送 testH264VideoStreamer.cpp文件的开头就定义了 char const* inputFileName = "test.264"; 后面接 ...

  5. rsync快速删除海量文件

    rsync --delete-before -avH --progress --stats /tmp/empty/ /var/spool/postfix/maildrop/ 由于业务侧使用时,一些脚本 ...

  6. 进入OS前的两步之PendSV(任务切换)

    先了解下如何使用PendSV异常.(为何要使用PendSV而不是其他的异常,请参考<cortex-M3权威指南>) 1,如何设定PendSV优先级? NVIC_SYSPRI14 EQU 0 ...

  7. github提交代码时,报permission denied publickey

    在像github提交代码时,报permission denied publickey. 查找了一下,可能是因为github的key失效了. 按照以下步骤,重新生成key. ssh-keygen 一路默 ...

  8. 关于Azure带宽的测试

    以前见客户经常会碰到一些客户问我们你们Azure的带宽是多少,每次回答这个问题我们只能含糊地告诉客户一个大概数值,这样就会留给客户一个认为我们很不专业的印象,其实站在客户的角度我们也能理解,连这样的一 ...

  9. TouchSlide1.1,手机上的幻灯片

    TouchSlide 是纯javascript打造的触屏滑动特效插件 http://pan.baidu.com/s/1bpoWNin 官网:http://www.superslide2.com/Tou ...

  10. word20161209

    failback / 故障回复 failback policy / 故障回复策略 failed / 失败 failover / 故障转移 failover policy / 故障转移策略 failov ...