About the Book
Xanpan is… a cross between XP and Kanban… is an example of a roll-your-own method… is team centric agile software development... is distilled from Allan Kelly’s own experiences running development teams and then helping multiple teams adopt Agile working methods and practices. Xanpan draws ideas from Kanban and Lean, XP and Scrum, Product Management and Business Analysis, and many other places.
Allan tells the Xanpan story through a series of boards which tell the story of different teams. In between he fills in the principles, practices and thinking which together constitutes Xanpan.
-
Feedback
Share this book
Table of Contents
-
Twitter & other online media
- Please Tweet!
- Websites
- What people say about Xanpan….
- About the author
-
Introduction
- Why write another book about Agile?
- This and subsequent books
- Feedback
- Coupons & freebies
- References
-
Prologue
- Dear Customer: The Truth About IT Projects
-
1. Xanpan Principles
- 1.1 Work in iterations
- 1.2 Team-centric: flow the work to the team
- 1.3 Work to improve Flow
- 1.4 Quality is free (provided you invest in it)
- 1.5 Visualise
- 1.6 References
- 2. Board 1
-
3. Iterations
- 3.1 Releasable
- 3.2 Iteration sequence
- 3.3 Mid-week to mid-week
- 3.4 Iteration length
- 3.5 Release schedules
- 3.6 The CEO test
- 3.7 References
-
4. Planning Meetings
- 4.1 The Players
- 4.2 The Artefacts
- 4.3 The Meeting Sequence
- 4.4 The Planning Game
- 4.5 Velocity and currency
- 4.6 Product Owner Preparations (Homework)
- 4.7 References
-
5. More Planning and Estimation
- 5.1 Ballpark estimates
- 5.2 Pre-Planning Meeting
- 5.3 Planning Poker
- 5.4 Some Planning Poker theory
- 5.5 Why break down Blues?
- 5.6 Estimate in Points Not Hours
- 5.7 Ideal hours
- 5.8 And ‘Actuals’
- 5.9 Deadlines
- 5.10 References
-
6. Watching the numbers
- 6.1 Where does the time go?
- 6.2 Hitting a deadline
- 6.3 Other numbers
-
7. Board 2
- 7.1 Planned and Unplanned
- 7.2 Testers
- 7.3 Moving backwards
- 7.4 Planning
- 7.5 Specialists
- 7.6 Technical Debt (and tax)
- 7.7 Key points
-
8. Non-technical Practices
- 8.1 Work in routines
- 8.2 Multiple work streams per team
- 8.3 Benchmark against yourself
- 8.4 Break down stories to tasks
- 8.5 Small pieces of work
- 8.6 Planning horizons
- 8.7 Flow
- 8.8 Mental flow
- 8.9 Absolute Prioritisation
- 8.10 Product Ownership
- 8.11 Pick ‘n Mix
- 8.12 Action over words: ‘just-do-it’, experimentation
- 8.13 References
-
9. Technical Practices
- 9.1 Test-Driven Development
- 9.2 Test-Driven Development (Unit Testing)
- 9.3 Acceptance Test-Driven Development (ATDD)
- 9.4 Refactoring
- 9.5 Frequent builds
- 9.6 Continuous Integration
- 9.7 Source code control
- 9.8 Code Reviews
- 9.9 Pair programming
- 9.10 Static analysis
- 9.11 Coding Standards
- 9.12 Finally
- 9.13 References
-
10. Planning beyond the Iteration
- 10.1 Iteration Planning
- 10.2 Quarterly Plans
- 10.3 Release plans
- 10.4 Roadmaps
- 10.5 Too fast for planning?
- 10.6 Finally
- 10.7 References
-
11. Board 3 - planned, unplanned and improving
- 11.1 Planned and Unplanned
- 11.2 Blocked, dropped
- 11.3 Improving
- 11.4 Board philosophy
- 11.5 Extending the board
- 11.6 References
-
12. Origins of Xanpan
- 12.1 References
-
Appendix: Quality
- Internal and External quality
- Software quality
- Quality Onion
- Defects
- Changeability (Maintainability)
- Obtaining the qualities (design)
- Quality and business value
- Finally
- References
- Acknowledgements
- Version History and coupons
- Xanpan 2 - The Means of Production
About the Author
Allan Kelly has held just about every job in the software world, from system admin to development manager by way of programmer and product manager. Today he works helping teams adopt and deepen Agile practices, and writing far too much. He specialises in working with software product companies and aligning products and processes with company strategy.
He is the author of three books: "Xanpan - reflections on agile and software development" (https://leanpub.com/xanpan), "Business Patterns for Software Developers" and “Changing Software Development: Learning to be Agile”; the originator of Retrospective Dialogue Sheets (http://www.dialoguesheets.com), a regular conference speaker and frequent contributor to journals.
More about Allan at http://www.allankelly.net and on Twitter as @allankellynet (http://twitter.com/allankellynet).