1. Topic
2. Deliver the highest business value features first
   1. Start using the prioritized functionalities which creates business value
   2. End-user receives the most important features that she will actually use
      1. Avoid building features that will never be used
3. Changes for
   1. Change the features as you
      1. Learn
      2. See your product grow
      3. There are still options for delivering business value at dates before the end of the project
4. Time To Market
   1. Better time to market for new, differentiating ideas
5. Potentially shippable product delivery after every 1-4 weeks
   1. Frequently review ensure that what customer was expecting is what he is getting by monitoring the progress frequently
   2. Ability to set development priorities at the beginning of every sprint
   3. Need not to risk for committing and paying the funds without looking at actual progress of the delivery
   4. Ability to cancel the project at the end of any iteration if you are not happy and still have delivered business value
   5. As Customer is involved frequent reviews which updates him about the progress, good, bad. Based on the same Customer can change his minds without paying heavy costs
   6. At the end of each iteration product is tested properly
   7. Delivery high quality work
6. Productivity increases
   1. Self-managed teams
   2. Motivation
      1. People are most productive when they manage themselves
      2. People take their commitment more seriously than other people’s commitment for them
      3. Under pressure to “work harder,” developers automatically and increasingly reduce quality
      4. People always do the best they can
   3. Performance
      1. Teams and people do their best work when they aren’t interrupted
      2. Teams improve most when they solve their own problems
      3. Broad-band, face-to-face communications is the most productive way for teams to work together
   4. Composition
      1. Teams are more productive than the same number of individuals
      2. Products are more robust when a team has all of the cross-functional skills focused on the work
7. Determine the product cost based on the progress and during the development
8. Continuous improvement
   1. Scrum enables continuous, rapid, bottom-up reengineering
9. Leverages the chaos
   1. The product becomes a series of manageable chunks
      1. Progress is made, even when requirements are not stable
   2. Everything is visible to everyone
   3. Team communication improves
   4. The team shares successes along the way and at the end
      1. A culture is created where everyone expects the project to succeed
   5. Customers see on-time delivery of increments
      1. Customer relationship
         1. Develops
         2. Trust builds
         3. Knowledge grows