Sprint planning
The team selects the items that have the highest priority and that are ready for work to start. The team can only commit to stories that have clear objectives, and that are not blocked by anything else. Also, the team can commit only to a limited number of stories during a sprint. That means that the team needs to know how much work will be involved with these stories, and how much work can be done during a sprint.
To determine how much work can go into a sprint, we need to know the team's velocity, which is a number that expresses the total effort a team is capable of in a sprint. That number comes from evaluating and determining the average amount of work done (sum of story points) in previous sprints. Of course, seasonal influences (holidays) and other things that could determine the team's capacity need to be taken into account. No extra work should be added to a sprint once the team has committed to start.
- Oracle RAC 11g實戰(zhàn)指南
- 大數(shù)據(jù)導(dǎo)論
- Oracle高性能自動化運維
- 辦公應(yīng)用與計算思維案例教程
- 智慧的云計算
- 菜鳥學(xué)SPSS數(shù)據(jù)分析
- Hands-On Deep Learning for Games
- Access 2016數(shù)據(jù)庫應(yīng)用基礎(chǔ)
- Google Cloud Platform for Architects
- 大數(shù)據(jù)用戶行為畫像分析實操指南
- 產(chǎn)品經(jīng)理數(shù)據(jù)修煉30問
- Working with OpenERP
- Getting Started with Review Board
- MySQL必知必會
- 實用計算機基礎(chǔ)