The Limited Red Society
•2 likes•6,215 views
Report
Share
Download to read offline
You've heard about limiting WIP (Work-In-Progress) but how good are you at limiting red time? Red time is when you have compilation errors and/or failing tests. A growing group of practitioners have learned how to effectively reduce red time while test-driving and refactoring code. To understand how to limit red time, it helps to visualize it. In this talk, Naresh Jain demonstrates various strategies to limit your time in Red. He analyzes live programming sessions using graphs that clearly visualize red time. You'll learn what programming processes help or hurt our ability to limit red time and you'll gain an appreciation for the visual cues that can help make you a better programmer and fellow member of the Limited Red Society.
More Related Content
Viewers also liked
Viewers also liked(20)
Similar to The Limited Red Society
Similar to The Limited Red Society(12)
More from Naresh Jain
More from Naresh Jain(20)
Recently uploaded
Recently uploaded(20)
The Limited Red Society
- 1. The Limited Red Society Agile Hyderabad, August Naresh Jain http://nareshjain.com Twitter: @nashjain Original Presentation by Joshua Kerievsky Copyright © 2010, Industrial Logic, Inc. All Rights Reserved. Sunday 15 August 2010 1
- 2. Profitability Sunday 15 August 2010 2
- 3. Decrease Inventory Sunday 15 August 2010 3
- 4. Decrease Operating Cost Sunday 15 August 2010 4
- 5. Increase Throughput Sunday 15 August 2010 5
- 6. Reducing Waste Sunday 15 August 2010 6
- 7. Extra Feature Sunday 15 August 2010 7
- 8. Inventory Sunday 15 August 2010 8
- 9. Heavy Weight Process Sunday 15 August 2010 9
- 10. Finding Information Sunday 15 August 2010 10
- 11. Defects Sunday 15 August 2010 11
- 12. Waiting Sunday 15 August 2010 12
- 13. Hand-offs Sunday 15 August 2010 13
- 14. Tools We Use Sunday 15 August 2010 14
- 15. Src: ThoughtWorks Sunday 15 August 2010 15
- 16. Kanban Board @ Yamaha Motor Src: Kenji Hiranabe Sunday 15 August 2010 16
- 17. Continuous Integration Sunday 15 August 2010 17
- 18. Sunday 15 August 2010 18
- 19. Sunday 15 August 2010 18
- 20. TO DO IN PROGRESS DONE Sunday 15 August 2010 19
- 21. In Progress = Red Sunday 15 August 2010 20
- 22. Me Sunday 15 August 2010 21
- 23. Sunday 15 August 2010 22
- 24. Mumbai Sunday 15 August 2010 23
- 25. Sunday 15 August 2010 24
- 26. Sunday 15 August 2010 25
- 27. We don’t travel like this Sunday 15 August 2010 26
- 28. We are getting there... Sunday 15 August 2010 27
- 29. AgilePhilly Tech Talks! Sunday 15 August 2010 28
- 30. FitNesse ProTest DBFit FitDecorator ProFIT La"u Patang QWick Sunday 15 August 2010 29
- 31. Sunday 15 August 2010 30
- 32. Sunday 15 August 2010 31
- 33. Sunday 15 August 2010 32
- 34. Sunday 15 August 2010 33
- 35. Sunday 15 August 2010 34
- 36. Sunday 15 August 2010 35
- 37. Sunday 15 August 2010 36
- 38. Visualization Sunday 15 August 2010 37
- 39. Sunday 15 August 2010 38
- 40. Sunday 15 August 2010 39
- 41. Sunday 15 August 2010 40
- 42. Sunday 15 August 2010 41
- 43. “Can we predict a winning team based on its passing pattern?” Sunday 15 August 2010 42
- 44. Sunday 15 August 2010 43
- 45. 462 total passes (twice as many as Holland) Centrality well distributed among players Impressive concentration in midfield Sunday 15 August 2010 44
- 46. Demo Sunday 15 August 2010 45
- 47. Sunday 15 August 2010 46
- 48. Sunday 15 August 2010 47
- 49. Sunday 15 August 2010 48
- 50. “A good retreat is better than a bad stand” -- Irish Proverb Sunday 15 August 2010 49
- 51. Narrowed Change Sunday 15 August 2010 50
- 52. Sunday 15 August 2010 51
- 53. Sunday 15 August 2010 52
- 54. Parallel Change Sunday 15 August 2010 53
- 55. Limiting Time in Red Other Examples Sunday 15 August 2010 54
- 56. Sunday 15 August 2010 55
- 57. Unavailable = Red Sunday 15 August 2010 56
- 58. Sunday 15 August 2010 57
- 59. Sunday 15 August 2010 58
- 60. Sunday 15 August 2010 59
- 61. Questions? • Thank You! • naresh@industriallogic.com • Twitter: @nashjain • http://blogs.agilefaqs.com Sunday 15 August 2010 60