Your SlideShare is downloading. ×
Lean Programmer Anarchy
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Lean Programmer Anarchy

124
views

Published on

Pecha Kucha in TW Uganda on Culture and Mindset for software development. Inspired by Jules Parry @julesparry presentation at TW University in India.

Pecha Kucha in TW Uganda on Culture and Mindset for software development. Inspired by Jules Parry @julesparry presentation at TW University in India.

Published in: Technology

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
124
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • What is ThoughtWorks?
  • A background in Xtreme Programming and its values before joining ThoughtWorks
  • Joined TW, and found them doing this Agile buzzAgilequestioned the dogma of waterfall. It recognizes that the waterfall way of working reduces trust.
  • Agile attacked the cultural chasms that waterfall seemed to cause. Build cross-functional teams in close collaboration with clients/customers/users
  • In this agile world, there arose a strand of thinking called LPA.
  • What is Lean Programmer Anarchy
  • The values in LPA
  • Relooking at Agile thought the lens of Critical Thinking and with the anarchist view of LPA
  • 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?
  • Challenge this. Do you need it. Why? What is the aim. Is there a better way to achieve that aim.
  • What about roles in Agile and here in TW, Do we need all of them?
  • Challenge that. All you need to begin with is Customer and Dev. Forward is trying this out. So are a lot of other places.
  • 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.
  • 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.
  • I don’t want thisto be a factory for agile clones that don’t question the norm. Head for that higher peak.
  • Transcript

    • 1. I Stole this from Jules
    • 2. CRITICAL THINKING
    • 3. Anarchy the absence or non-recognition of authority freedom of the individual regarded as a political ideal
    • 4. TRUST with co-location RESULTS not blame CONTINUOUS DELIVERY SMALL APPS SHORT-LIVED
    • 5. AGILE TECHNIQUES stand ups retrospectives estimates iterations mandatory pairing unit tests acceptance tests refactoring patterns continuous integration
    • 6. AGILE TECHNIQUES stand ups retrospectives estimates iterations mandatory pairing unit tests acceptance tests refactoring patterns continuous integration WAT?
    • 7. WAT?
    • 8. You see, Mr. Anand, it works on my machine

    ×