Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

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

by tye (Sage)
on Jun 12, 2015 at 00:28 UTC ( #1130119=note: print w/replies, xml ) Need Help??


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

On the ground, in practice, in my experience, there isn't anything that Agile can accomplish that can't be accomplished without Agile. But it can also be a very useful toolset. It can be a burden if you have to fight too hard against coworkers who have too strong of a tendency to practice Agile soaked in too much Kool-Aid (that is, dogmatic attitudes will usually be a small problem but can also be a big pain).

It can be very useful to be able to get Agile adopted rather than work to get a whole laundry list of process changes adopted. And it can be particularly useful when you have to push back hard against Business/Product people who are aggressively impatient or demanding.

And I think there is some truth to the impression of Agile proponents that the various aspects of Agile work especially well when combined. And the principles of Agile can be useful for justifying improvements. But it is also my experience that refusing to "stray" from Agile is very harmful.

I think Agile makes a very good starting point for creating and maintaining a sane software development Process. You can also just study Agile and adopt parts of it or just use parts of it as inspiration to improve how your team works. But, in my experience, the teams that were based on Agile were closer to working well than the ones that weren't.

- tye        

  • Comment on Re^2: Nobody Expects the Agile Imposition (Part VIII): Software Craftsmanship (useful)

Replies are listed 'Best First'.
Re^3: Nobody Expects the Agile Imposition (Part VIII): Software Craftsmanship (useful)
by BrowserUk (Pope) on Jun 12, 2015 at 00:53 UTC

    Sounds like most 'sets of principles': read, understand, and apply judiciously; they can help you focus on what's important.

    But try to impose them; dogmatically or automatically; and they become the focus. To the detriment of all else.


    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority". I'm with torvalds on this
    In the absence of evidence, opinion is indistinguishable from prejudice. Agile (and TDD) debunked

      I think these two lines are perhaps the truest things I've read about software development or anything else all day.

      Dogmatically applying any set of guidelines as inflexible rules is both silly and against the definition of "agile" as a word and as the original movement. A team should make as much or as little use of a methodology or a mix of methodologies as works best for that team. Anything written in a book or taught in a class is just a starting point for a new team and shouldn't be an end goal.

Log In?
Username:
Password:

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

How do I use this? | Other CB clients
Other Users?
Others lurking in the Monastery: (4)
As of 2019-04-25 06:21 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    I am most likely to install a new module from CPAN if:
















    Results (125 votes). Check out past polls.

    Notices?
    • (Sep 10, 2018 at 22:53 UTC) Welcome new users!