Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?

Re^5: Nobody Expects the Agile Imposition (Part VIII): Software Craftsmanship

by jeffa (Bishop)
on Jun 12, 2015 at 00:14 UTC ( #1130118=note: print w/replies, xml ) Need Help??

in reply to Re^4: Nobody Expects the Agile Imposition (Part VIII): Software Craftsmanship
in thread Nobody Expects the Agile Imposition (Part VIII): Software Craftsmanship

"the promise of being able to replace temperamental, expensive craftsmen with fungible, cheaper assemblers"

Wait, are you suggesting that is the "promise" of Agile as well? Because that is not true:

"It is naive to think of human beings as resources. Adding people to a team will not reliably increase the intangible resources--and may detract from them. After a year of doing Scrum, one of my clients reported “Once a team is formed, we would rather lose a team member than add one!” In another case, when the Scrum team itself made the hiring decision, adding a new member went well. Even when giving the team hiring autonomy, it’s inadvisable to grow it much larger than seven people. In some circumstances, adding teams may result in more progress, if we’re mindful of the intangible resources"

These methodologies are built FOR programmers and FOR their craft. Most coders find these practices enjoyable and wonder why they had not used them sooner. The managers are the ones that take more convincing.


(the triplet paradiddle with high-hat)
  • Comment on Re^5: Nobody Expects the Agile Imposition (Part VIII): Software Craftsmanship

Replies are listed 'Best First'.
Re^6: Nobody Expects the Agile Imposition (Part VIII): Software Craftsmanship
by aaron_baugher (Curate) on Jun 12, 2015 at 00:55 UTC

    Craftsmen don't want to focus on methodologies; craftsmen want to be left alone to practice their craft. That's not to say there aren't methodologies that would be helpful for programmers; but I would expect them to develop and spread quietly through forums and word-of-mouth in the same way software improvements do, not through flashy marketing campaigns and company-wide rollouts.

    It's management that spends time thinking about methodologies, because tweaking methodologies is a major way management justifies its existence. I've seen management switch from salaried employees to contractors (and then back again a couple years later); from cubicles to open rooms to offices to cubicles; from email communications between team members to instant messenger to frequent personal meetings. I've seen management declare that all new software would be written in a certain language for maximum efficiency (in this case, Java, for the hope of "replaceable cogs" that I mentioned before). In every case, management insisted these changes would be critical for making everyone's job easier and raising productivity. In every case the programmers rolled their eyes and did their best to ignore it and get on with programming.

    So if you're saying programmers are excited about this particular methodology and are pushing it forward, while managers aren't interested in it....well, I guess there's a first time for everything.

    Aaron B.
    Available for small or large Perl jobs and *nix system administration; see my home node.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1130118]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (6)
As of 2020-07-13 15:13 GMT
Find Nodes?
    Voting Booth?

    No recent polls found