Agile

Question 1

Manifesto

Answer 1

1. individuals and interactions over processes and tools
   
   2. working software over comprehensive documentation
   3. customer collaboration over contract negotiation
   4. responding to change over following a plan

Question 2

Werte für Extreme Programming (XP):

Answer 2

• Simplicity: We will do what is needed and asked for, but no more.
  
  • Communication / Collaboration: Everyone is part of the team and we communicate face to face daily.
  • Feedback: We demonstrate our software early and often then listen carefully and make any changes needed.
  • Respect: Developers respect the expertise of the customers and vice versa.
  • Courage: We will tell the truth about progress and estimates.

Question 3

Prinzipien der XP: - ca. 3 - 5

Answer 3

• Pair Programming: Usually two programmers are building the same source code together.
• User Stories: Requirements are not defined by use cases (as RUP does), but within user stories – a description of graphical user interfaces (GUI), functionality and testing scenarios.
  • On-site Customer: A competent and high experienced representative of the customer supports the developer permanently.
  • Collective Ownership: Source code belongs to the whole team and not to a single programmer. Every programmer – every team member – is responsible for the source code.
  • Continuous Integration: Source code should be integrated and consolidated permanently. Problems of missing or wrong compatibility can be detected and corrected very early.
  • Testing: Each module needs its individual unit test that should be run automatically.
  • Simple Design: No unnecessary features should be implemented.
  • Small Releases: Many iterations should be done with executable results that can be evaluated by the customer.

Question 4

Scrum - SCHAUBILD

Answer 4

• Sprint
• Scrum Team
• Scrum Master
• Scrum Meetings
• Scrum Backlogs
• User Story
• (Vs. Enabler)