• “People think computer will keep them from making mistakes, They are wrong, with computers you just make mistakes faster” - Adam Osborne
• good assumption: “The customer will only know what they want when they see it.”
• fragile = fake agile that means it is an agile project in which not all buzzwords are used.
• “We have no plans, therefore nothing can go wrong” - Spike Milligan
• Scrum General Practices:
  • Customer must be a part of the development team
  • there should be frequent intermediate deliveries with working functionalities
  • Problems issues and risks must not be swept under the carpet
  • The project environment and work time must be energized => working more hours does not mean producing more output
• Pig roles:
  • product owner: voice of the customer and ensures that the Scrum team is focused on the right issues from a business perspective
  • Scrummaster: primary job is to remove impediments to the ability of the team to define the sprint-goal; they are not the leader hat and acts as a buffer between the team and any distracting influences; they ensure that the Scrum process is used as intended
  • Scrum team: 5–9 people with cross-functional skills (tester, developer, designer, …)
• Chicken roles:
  • the user:
    • write software for them
    • Scrum Mantra: “Never forget that software that is not used is like a tree falling in the forest - was it ever written?”
  • Stakeholders: people enable the project but are not directly involved in the process
• Sprint:
  • 15 - 30 days
  • the team creates an increment of the software
  • the set of features that go into the sprint comes form the product backlog
• Scrum Artifacts
  • User Stories
    • capturing user requirements
    • written in simple, non technical , jargon free language
    • template: As a (Role) I want to (Goal) so that I can (Reason)
  • product backlog
    • high-level document of the entire project
    • contains: wish-list items and so on
  • Sprint backlog
    • document gathering information about how the team is going to implement the requirements for the upcoming sprint
    • tasks are broken down into hours with no task being more than sixteen hours
  • Burndown
    • is publicity displayed chart showing the effort remaining over time