Video based Quiz

Notes for Quiz

• To plan a release, the team starts with this, the product backlog, and they identify the user-stories they want to put into this release. These user stories then become part of the release backlog.
• The team then prioritizes the user-stories and estimates the amount of work involved for each item.
• There are a lot of techniques for creating good estimates. Some prefer estimating in story points where estimates are made about building a small component with a known level of difficulty.
• The best technique is to estimate work in hours but to use some standards in how estimates are done.
• Sprints are short duration milestones that allow team to tackle a manageable chunk of the project and get it to a ship ready state.
• Sprints range from a couple of days to as much as 30 days in length, depending on the product's release cycles.
• The shorter the release cycles, the shorter each sprint should be.
• At the end of each sprint, you should have a fully tested product with all the features of that sprint 100% complete.
• Since sprints are a very short, but realistic representation of part of the product a late finish of the sprint is a great indication that the project is not on the schedule and something needs to be done. Therefore, it's critical to monitor the progress of each sprint with THIS: A burndown chart.
• The burndown chart is the number one reason for scrum's popularity, and one of the best project visibility tools to ensure a project is progressing smoothly. The burndown chart provides a day-by-day measure of the amount of work that remains in a given sprint or release.
• The amount of work remaining bounces up and down from day to day, but is trending towards zero. Because historical information is provided in the burndown chart, it's easy to see if the team is on the right track.