Ever been invited to a project kickoff party only to find out that you’re flying solo? Congratulations, you’ve just become the ultimate co-located, self-organized, cross-functional, energized agile team of one. Join us for this session where we explore how the lone coder can take advantage of the best agile has to offer in this era of ever shrinking budgets.

6. What are the practices relevant to a solo developer?
How can we tell if we’re winning?
Where should I start first?

9. Vision document
User stories
Single project backlog
Customer contact

10. Browse Catalog Biz Value: 5 Acceptance Criteria:
As a shopper I want to browse the − Shopper is shown a list of product
Tailspin Toys catalog so that I may categories.
purchase some toys. − Shopper can view details for each
product in catalog, including :
name, inventory #, description,
price, and related items.
Estimate: 3

12. Colocation
Relative size estimates
Small batch sizes
Continuous integration
Frequent releases
Research spikes

13. Relative size
estimates

14. Small
batch sizes

15. Test driven requirements
Test driven development
(Red-Green-Refactor)
Done Done state
Bugs before features

16. Emergent architecture
Simple design (YAGNI)
Aggressive refactoring
(green code only)

17. Simple
design
(YAGNI)

18. Simple
design
(YAGNI)

19. Single project backlog
Information radiators
Customer demos

22. Coding standards
Automated functional
tests
Sustainable pace

23. Sustainable
pace

25. Collaboration with customer
Attention to quality
Incrementalism
Automation
Continuous improvement
Energized workforce

26. No definitive process
Huge cases
Technical debt
Large, complex, high-risk
projects

28. User stories
Single project backlog
Relative size estimation
Small batch sizes
Simple design (YAGNI)
Sustainable pace

30. https://tfspreview.com/

31. Buckaroo Banzai