Implementing PROGRAMMER ANARCHY

30 Pages·2014·5.23 MB·English

by  Geeta Schmidt

I mplementi ng
PROGRAMMER ANARCHY
Fred George
[email protected]
@fgeorge52
Copyright © 2011-2014 by Fred George 1
Emergi ng Experiences at. . .
CCooppyyrriigghhtt ©© 22001112--22001143 bbyy FFrreedd GGeeoorrggee. All rights reserved. 2
✦ C-level executives understand this
Agile is a So cial Cha nge
✦ Middle management scared of this
✦ Result: Half-baked Agile implemented
Copyright © 2011-2014 by Fred George 3
✦ Development driven by stories
✦ Stories small

Agile Side Effect:
✦ Priority set by customer
Story Tyra n ny
✦ Story-level estimates and metrics
Problem
:
Developers become disconnected
from business problem (Drones)
Copyright © 2011-2014 by Fred George 4
Initiatives
Projects
Requirements Hierarchy
Features
Stories
Tasks
Copyright © 2011-2014 by Fred George Credit: Greg Reiser, ThoughtWorks, 2005 5
Agile Roles
project
manager
iteration
management
manager
!
Agile
Roles
business development
customer architect
progrdamevmeelroper
QA
BA UI designer
DBA
Copyright © 2011-2014 by Fred George 6
A narchy Roles
✓

✦ Customer
X
✦ Project manager
X
✦ Business analyst

✓

✦ Developer
X
✦ Quality assurance / tester
X
✦ Manager of programmers
Copyright © 2011-2014 by Fred George 7
Fate of Roles: QA
project
manager
iteration
management
manager
✦ QA tools are Programming tools
✦ Selenium
!
✦ Cucumber
Agile
Roles
✦ Service Architecture creates complex systems
✦ Need architecture skills to properly test
business development
✦ Shift toward monitoring over acceptance testing
customer
developer
QA
BA
Copyright © 2011-2014 by Fred George 8
Fate of Roles: BA
project
manager
Too complex for
Programmers
iteration
management
manager
programmers!
lack “social
skills”
!
Agile
Roles
business development
Programmers
customer
developer
can’t talk
BA
Copyright © 2011-2014 by Fred George 9
Fate of Roles:
project
manager
X
iteration
management
manager
!
Agile
Roles
business development
customer
developer
Copyright © 2011-2014 by Fred George 10