ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Is something rotten in the state of agile? creativity, Wicked problems, process and creativity.

Updated on May 17, 2015

Agile development

Agile emphasises rapid development cycles, tight feedback loops between customers and developers and includes practices such as extreme programming pair programming and test driven development. Properly implemented and managed Agile can increase developer productivity dramatically and reduce churn and rework. However there seem to be concerns at various levels that Agile can be implemented in a way that destroys, or at least damages developer creativity.

The key words here are “properly Implemented and managed”.

Agile works on the divide and conquer principle with each task split into smaller tasks and these are subdivided into units of work achievable (barring unforeseen circumstances) in a single sprint a period between one and three weeks for development.

And here is where problems start to arise with respect to creativity and innovation. The shorter the sprint the smaller the tasks. If the entire team is involved the breakdown feels like the checklist a single developer creates before starting work. If it is conducted by a single team member coding becomes as routine a task as coding ever can be which can lead to bored developers with no room for creative or innovative solutions other than those determined by the planner. Eventually this can burn creativity out of developers, who have scope for initiative and planners, who are expected to produce the Big Fat Plan Up Front.

Wicked Problems, Agile and Creativity

Software development is a wicked problem, that is one that resists solution, especially when it involves many stakeholders, multiple systems and difficult social, political, and other challenges such as re-engineering an enterprises core systems whilst still trying to run the business.[2]. One characteristic of a wicked problems is that understanding only comes with producing a solution to the problem, and this in turn reveals new aspects of the problem that demand a modified or totally new solution. As one developer stated

I know from personal experience that I can never get very far without writing code to better understand the problem I am trying to solve.” [3]

The standard convergent thinking approach to solving problems: Gather data, study options and pick a strategy do not work with wicked problems. These problems demand social processes that engage stakeholders, explore related issues and reevaluate the problem and stakeholder assumptions [4] . Excessive analysis is not the way to proceed. Instead an evolutionary process something like the adaptive tinkering described by Beinhocker [5] where analysis is used to take the investigator to the point where multiple options present themselves after which the only way forward is experimentation, aka trial and error or muddling through,

Wicked problems frequently, perhaps always require creativity. Goijko [6] notes that Lambert said that creativity is crucial for software development problem-solving and a key factor for exploration, adapting and iterating, which are some of the core values shared by successful agile software delivery teams. Some structure and process is needed to facilitate creativity, but excessive structure kills it.

Agile is recognised as an effective way to deal with wicked problems, largely due to its inherent flexibility. Some structure and process is needed to stop random people doing untracked random things, but, as with security and email, too much can get in the way of getting the job done and destroy not just creativity but the desire to be creative.

The problem is getting the right level of structure and process. Get it wrong and you have an Agile-hostile culture trying to implement Agile.

Traditional methods do not work with wicked problems
Traditional methods do not work with wicked problems

Signs of an agile hostile culture

A corporate culture that values comprehensive documentation, despite the second law of software thermodynamics - which means all good code turns bad, usually rapidly, and documentation and code diverge faster than politicians abandon promises that do not involve them getting more money - is Agile hostile.

A corporate culture that insists all activity be tracked (Tracking is what managers DO for heavens sake) and processes be followed regardless of circumstances is Agile hostile

Collaboration is good but a company with a strong email and meeting culture that finds developers spending more time collaborating than developing is agile hostile.

Each of these states can destroy creativity and stifle innovation.

A company that attempts to put creativity and innovation in different silos from the task of developing towards a release deadline may not be actively agile hostile but risks becoming creativity-hostile. Examples are where companies block off certain times for innovation, usually far too little time to do anything significant.

Observations

One developer [7] noted a severe decrease in motivation and creativity some months after a scrum based methodology was adopted saying

  1. I tend to search less to find a better solution, approach, or technique

  2. I don't wake up in the morning expecting to get to an enjoyable work. Rather, I feel like being forced to work in order to live

  3. I have more hunger to work on my own hobby projects after work

  4. I won't push the team anymore to get to the higher technological levels

  5. I spend more time now on dinner, or tea-times and have less enthusiasm to get back to work

  6. I'm now willing more for the work to finish sooner, so that I can get home

The comments on their stack overflow question suggested Agile was wrongly implemented in their organisation.

Gilb and Gilb [8] note that 90%-99% of all Agile, XP & Scrum practitioners and teachers teach 'Solutions' as if they were requirements, thus killing opportunity for developer creativity. This also tends to kill the fun of being a Developer. They also make a case that the current almost universal user story focussed approach is severely flawed.

Hazrati [9] picked up on Gilb's comment that Agile Baby talk kills developer creativity.

James Turner [10] stated

passionate programmers write great code, but process kills passion. Disaffected programmers write poor code, and poor code makes management add more process in an attempt to “make” their programmers write good code. That just makes morale worse, and so on”

Taken together these observations suggest that enterprises get Agile wrong and there are still flaws in the definition of Agile itself.

In Summary

The agile manifesto [1] is neutral with regards to creativity and innovation: it mentions neither.

Software development is a wicked problem that requires creativity, innovation and risk taking.

Properly done Agile can stimulate all three.

Wrongly done or in an Agile or creativity hostile culture Agile can destroy all three.

Focus on process is deadly to passion [10] and also creativity.

And [8],[9] there is a possibility Agile itself is being badly taught.


Comments

    0 of 8192 characters used
    Post Comment

    No comments yet.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: "https://hubpages.com/privacy-policy#gdpr"

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)