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.
- Spark大數據分析實戰
- Access 2007數據庫應用上機指導與練習
- Python數據分析、挖掘與可視化從入門到精通
- MySQL基礎教程
- 數據庫應用基礎教程(Visual FoxPro 9.0)
- Mastering Machine Learning with R(Second Edition)
- 大數據:從概念到運營
- 城市計算
- Learning Proxmox VE
- Mastering LOB Development for Silverlight 5:A Case Study in Action
- MySQL技術內幕:SQL編程
- Python數據分析從小白到專家
- 中文版Access 2007實例與操作
- SIEMENS數控技術應用工程師:SINUMERIK 840D-810D數控系統功能應用與維修調整教程
- 數據分析思維:產品經理的成長筆記