A New Translation of the Agile Manifesto
summary
A team re-translates the Agile Manifesto into clearer Japanese using experience from many book translations and a side-by-side English/Japanese review. They propose wording changes: replace “working software” with “usable software,” interpret “interactions” as relational rather than only conversational, and keep the 12 principles while rephrasing points on early continuous delivery, sponsors’ responsibility for sustainable pace, emergent architecture and technical excellence, and the idea to “maximize the amount of work not done.”
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:16New translation needed
- 3:24Title and first paragraph
- 5:12Four values revisited
- 6:45Twelve principles clarified
- 10:30Motivated individuals
- 13:17Working software progress
- 15:02Sustainable development
- 16:11Simplicity in Agile
- 17:58Emergent architecture
- 18:40Regular reflection
related talks
39mWe're Agile, we don't do documentation
36mAgile documentation: A first class citizen
47mGlobalise the docs
20mOh My Docs!
26mJust-In-Time Documentation: Employing Agile Methodology To Create Living Documentation
42mThe GDD's Not Dead: Tips & Tricks for Agile Design Documents
15mContinuous Annoyment: Bringing More Zen to a Hectic Writing Environment
40mLessons Learned: arc42 in a Real Devops Team