Programmer Anarchy

Agile Manifesto✦ Individuals and interactions over processes and tools✓✦ Working software over comprehensive documentation ✓✦ Customer collaboration over contract negotiation ✓✦ Responding to change over following a plan ✓Copyright © 2011 by Forward Internet Group, Ltd 5

Agile Best Practices Not Used✦ Stand ups ✦ Unit tests✦ Story narratives ✦ Acceptance tests✦ Retrospectives ✦ Refactoring✦ Estimates ✦ Patterns✦ Iterations ✦ Continuous integration✦ Mandatory pairingCopyright © 2011 by Forward Internet Group, Ltd 7

✦ Frequency of interaction ✦ Process impact ✦ Fewer roles (& titles!) agile/lean Lean KanbanTrust SCRUM Agile XP Cultural Chasm waterfall Copyright © 2011 by Forward Internet Group, Ltd Idea from Mark Durrand, uSwitch 10

Role impact project manager iteration management manager Agile Roles business development customer programmer architect QA developer BA UI designer DBACopyright © 2011 by Forward Internet Group, Ltd 11

✦ EMPOWERMENT ✦ ANARCHY ✦ Somebody “gives” it ✦ Nobody to askWhy “ANARCHY” ✦ Somebody can “take it away” ✦ Can’t stop someone else ✦ Leads to “Can I ... ?” ✦ Disagreements expectedCopyright © 2011 by Forward Internet Group, Ltd 15

✦ Development driven by stories✦ Stories smallAgile Side Effect:✦ Priority set by customerStory Tyrannymetrics✦Story-level estimates and Problem: Developers become disconnected from business problem (Drones)Copyright © 2011 by Forward Internet Group, Ltd 17

✦ Ruby for energy calculation - big improvement!✦ Rewrote in ClojureExample: Energy Revolution✦Rewrote in Clojure (again) Question: What manager would let them to do it? Hence: No manager!Copyright © 2011 by Forward Internet Group, Ltd 21

✦ Old system:Example:32Clickwith 40% utilization Ruby-based, ✦ servers Tracking✦ New system: ✦ Node.js, 22 servers with 10% utilization and lower latencyCopyright © 2011 by Forward Internet Group, Ltd 22

Do or not do,Sound finances there is no try Like risk Experimentation Fear is the Cultural Enablers drives innovation mind killer are not failing, If you you are not tryingClarity of Developer success focused The greatest barrier to success is Respected peers the fear of failure Copyright © 2011 by Forward Internet Group, Ltd 23

Agile Best Practices Not Used Trust w✦ Stand ups collocation ✦ Unit tests✦ Story narratives ✦ Acceptance tests Small,✦ Retrospectives ✦ Refactoring short-lived✦ Estimates ✦ Patterns apps Results,✦ Iterations not blame ✦ Continuous integration✦ Mandatory pairing Continuous deploymentCopyright © 2011 by Forward Internet Group, Ltd 24

✦ Different extent by teamReality Check ✦ Talent, experience, apprehension ✦ Anarchy exists in how Anarchy is implemented✦ Even our best Anarchists “ask” on occasion✦ Commercial success driving freedomCopyright © 2011 by Forward Internet Group, Ltd 25

http://blog.redturtle.it	627
http://agileee.org	224
http://graywolf.org.ua	119
http://localhost	8
http://translate.googleusercontent.com	2
http://feeds2.feedburner.com	1
http://webcache.googleusercontent.com	1
http://castell.hosting.redturtle.it	1

Programmer Anarchy

by Antonio Terreno on Sep 25, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

8 Embeds 983

Statistics

Programmer Anarchy — Presentation Transcript