Lean Programmer Anarchy
Download as PPTX, PDF1 like779 views
This document discusses various topics such as anarchy, trust, continuous delivery, agile techniques and issues with software development. It notes anarchy as the absence of authority and freedom of the individual as a political ideal. For software development, it mentions using agile techniques like stand ups, retrospectives and tests alongside continuous delivery of small applications through short iterations. However, it also notes issues like things working differently on individual machines than expected.
Lean Programmer Anarchy
- 1. I Stole this from Jules
- 7. Anarchy the absence or non-recognition of authority freedom of the individual regarded as a political ideal
- 10. AGILE TECHNIQUES stand ups retrospectives estimates iterations mandatory pairing unit tests acceptance tests refactoring patterns continuous integration
- 11. AGILE TECHNIQUES stand ups retrospectives estimates iterations mandatory pairing unit tests acceptance tests refactoring patterns continuous integration WAT?
- 13. WAT?
- 19. You see, Mr. Anand, it works on my machine
Editor's Notes
- #3: What is ThoughtWorks?
- #4: A background in Xtreme Programming and its values before joining ThoughtWorks
- #5: Joined TW, and found them doing this Agile buzzAgilequestioned the dogma of waterfall. It recognizes that the waterfall way of working reduces trust.
- #6: Agile attacked the cultural chasms that waterfall seemed to cause. Build cross-functional teams in close collaboration with clients/customers/users
- #7: In this agile world, there arose a strand of thinking called LPA.
- #8: What is Lean Programmer Anarchy
- #9: The values in LPA
- #10: Relooking at Agile thought the lens of Critical Thinking and with the anarchist view of LPA
- #11: Lets start with the practices that seem to follow wherever Agile goes. Have you ever been asked if you are following these on your TW team?
- #12: Challenge this. Do you need it. Why? What is the aim. Is there a better way to achieve that aim.
- #13: What about roles in Agile and here in TW, Do we need all of them?
- #14: Challenge that. All you need to begin with is Customer and Dev. Forward is trying this out. So are a lot of other places.
- #15: It’s not about the tools. Culture is the differentiator.A culture of critical thinking is better than the culture of blame.It’s about not asking “is it ok?It’s about thinking for yourself and making a decision.
- #16: We’ve questioned the waterfall enough such that we realized that there was a better way.But there is a higher peak out there. Let talk about things we can do push ourselves to that peak.
- #21: I don’t want thisto be a factory for agile clones that don’t question the norm. Head for that higher peak.