课程: Agile at Work: Planning with Agile User Stories
今天就学习课程吧!
今天就开通帐号,24,700 门业界名师课程任您挑!
Ready to implement state
- Over the project's timeline, most identified stories will become highly prioritized and ordered towards the top of the backlog. Once a story is high in priority and a candidate to pull into the next iteration or two, it needs to be in the state ready to implement. For the story to be in this state, the team must invest time to discuss it, and acceptance criteria must be written. Stories that meet a team's definition of ready are ready to be implemented. This helps ensure that the team has a high level of confidence and probability that if they pull a story into the workflow, they understand what is needed. The product owner constantly refines the backlog, and the team collaborates towards the end of each iteration to ensure readiness to move into the next iteration. This workflow is perpetual for the remainder of the project.
随堂练习,边学边练
下载课堂讲义。学练结合,紧跟进度,轻松巩固知识。
内容
-
-
-
-
-
(已锁定)
Ready to implement1 分钟 56 秒
-
(已锁定)
Identified state1 分钟 15 秒
-
(已锁定)
Sized state1 分钟 5 秒
-
(已锁定)
Relative sizing techniques3 分钟 34 秒
-
(已锁定)
Team estimation5 分钟 37 秒
-
(已锁定)
Size with points vs. estimate with hours2 分钟 13 秒
-
(已锁定)
Understand velocity3 分钟 10 秒
-
(已锁定)
Prioritized state52 秒
-
(已锁定)
Input to backlog prioritization and planning3 分钟 25 秒
-
(已锁定)
Ready to implement state1 分钟
-
(已锁定)
Acceptance criteria4 分钟 38 秒
-
(已锁定)
Story quality and the definition of ready4 分钟 39 秒
-
(已锁定)
-
-