PM Power Hour presentation
27 March 2018
- Kent Beck
- Chrysler Comprehensive Compensation System (i.e., payroll)
- Take agile and crank it to 11.
- What if the customer were always available, always in the room.
- What if we always were communicating F2F?
- What if we reviewed each others' code constantly?
- What if we tested everything? Not just systems, but even small parts of systems? What if we didn't write code unless a broken test requires it?
Looks like Agile because it is Agile.
(Not necessarily going into all of these.)
- User stories
- Release planning creates the release schedule
- Frequent, small releases
- Iteration planning
- Open, dedicated workspace
- Sustainable pace
- Measure velocity
- Move people around
- When it breaks, fix XP
- System metaphor
- CRC cards (class-responsibilities-collaboration) to design system
- Spike solutions
- JIT functionality. Don't add early. YNGTNI.
- Refactor aggressively
- Customer always available
- Code written to standards
- Unit test first
- Pair programming
- One pair integrates at a time
- Integrate often
- Dedicated integration computer
- Collective ownership
- All code must be unit tested
- All code must pass all unit tests
- When bugs are found, create tests
- Acceptance tests are run often and results broadcast
- Formed 2012
- Spun off from Dell EMC Corporation and VMWare
- Well-known, respected consultancy
- Produces a number of products that their consulting leverages
- Pivotal Tracker
- Cloud Foundry
- Spring Boot
- lots of opinions about everything, including testing
- not dogmatic about languages, frameworks
- not dogmatic about lots of weird things
- adding new categories of work
- very dogmatic about others
lots shared values
- doctors, not waiters
- delivering value to clients
- availability vs flow
XP, WT, Synchrony
How are we using it weirdly?
- ramp-up time
- team size
- project time length
not about XP, per se, but...
about empowering developers/teams
in place of code review
Mis-named. It's a design tool, not QA.
It's a code maintenance tool.