Values
Communication
Simplicity
Feedback
Courage
Respect
Principles
Humanity
Reflection
Economics
Mutual Benefit (every Activity)
Flow (steady Software flox)
Self Similarity
Opportunity (Change)
Redundancy
Improvement
Diversity
Failure
12 Key Practices
Customer Satisfaction
On-Site Customer
Small Releases
Software Quality
Metaphor
Test-First Programming
Simple Design
Refactoring
PairProgramming
Project Management
Planning Game
Sustainable Development
Collective Code Ownership
Continuous Integration
Coding Standards
Circle of Life
build
define
estimate cost
choose
User Stories
Discription of a system behavior
specifies system
small
Spike (experiment)
Estimate
Planning
Release Planning (Define Deadline)
Iteration planning (high priority stuff)
Estimates
cost
time
scope
effort
try to be precise wc overestimate
convert counts to estimates
tracked data
use Story Points
Planning Poker
Code is simple enough when it:
Runs all the tests
Expresses every idea you need to express
Contains no duplicate code
Has the minimum number of classes and methods
Roles
customer
programmer
manager
Manager and Custormer Rights
overall plan
most possible value
see progress
change your mind
informed of schedule
Programmer Rights
know needs
produce quality
ask for help
estimate
accept your responsibilities
Zuletzt geändertvor 5 Monaten