Friday, September 23, 2005
Practices
Following are the list of XP practices. Note to self: I should also go look at the 12 points in James Shore's The Extreme Programmers' Oath. These were taking from XPEe2. Turns out we'll be following almost all of them. Where not, there will be comments. If there are no comments, then we are going to follow that practice.
Primary:
Corollary:
As noted previously, management had requested that the team (3 programmers, 1 customer proxy, 1 tester) get together and discuss all the primary principles and pick which ones we'd use. Note any issues we couldn't resolve on the team, and then invite management in to discuss with them which principles we had picked and get them to help us resolve issues.
We walked through the above and discussed them all. What we though they meant to us, how we thought they applied, etc. And as you can see, we picked almost all the principles (primary and corollary) - and we had no issues. There was complete agreement on all of them.
It took us most of the day - and it was a very successful start.
Tomorrow - we start with stories. Cool. :)
Primary:
- EnergeticWork
- IncrementalDesign
- PairProgramming
- Initially we are going to try SitTogether and see if we can get enough benefits from pair programming. We will pair at times - as needed. I know - folks would say that is Always. But we are going to ease into this. If we find pairing always works well for us, and we are comfortable with it, then we'll start doing it. But at first we will at least talk a lot, and look at each others stuff as we get little pieces done.
- TestFirstProgramming
- WholeTeam
- InformativeWorkspace
- SitTogether
- ContinuousIntegration
- TenMinuteBuild
- We don't believe this applies, because we are using a system that doesn't really "build". But we understand the philosophy of quick acceptance tests, etc. and so we'll keep an eye on that.
- WeeklyCycle
- QuarterlyCycle
- Usually our implementations are faster than quarterly. We'll go with the idea behind this though. Small releases that are quicker than normal, immediate customer feedback, etc.
- UserStories
- ProjectSlack
Corollary:
- NegotiatedScopeContract
- We don't think this applies in our environment.
- PayPerUse
- We don't think this applies in our environment.
- DailyDeployment
- We are going to try and be extreme... but not that extreme - at least for now
- RootCauseAnalysis
- RealCustomerInvolvement - CustomerProxy
- ShrinkingTeams
- We are starting with 3 people - so we don't think our team will shrink.
- TeamContinuity
- CodeAndTest
- SharedCode
- SingleCodeBase
As noted previously, management had requested that the team (3 programmers, 1 customer proxy, 1 tester) get together and discuss all the primary principles and pick which ones we'd use. Note any issues we couldn't resolve on the team, and then invite management in to discuss with them which principles we had picked and get them to help us resolve issues.
We walked through the above and discussed them all. What we though they meant to us, how we thought they applied, etc. And as you can see, we picked almost all the principles (primary and corollary) - and we had no issues. There was complete agreement on all of them.
It took us most of the day - and it was a very successful start.
Tomorrow - we start with stories. Cool. :)
