Agile Development: Ask The Customer - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
IoT
IT Leadership // CIO Insights & Innovation
News
5/29/2014
03:45 PM
Pollyanna Pixton
Pollyanna Pixton
News
50%
50%

Agile Development: Ask The Customer

If we don't learn from our customers -- especially what unique value they expect -- how can we compete successfully in the market?

In a recent conversation at a conference lunch, I asked my peers what one word they would use to describe Agile. There were a few suggestions such as "flexible," "disciplined," and "responsive." When someone pointed the question at me, my answer was, "Learning." By that I mean, "continuous learning."

Have we lost sight of this? Is an adherence to the practices of Agile getting in our way of learning? Is the Agile community learning and evolving?

Without a culture of learning, processes take over that allow us to wriggle out of responsibility -- a mindset encapsulated in the phrase: "I didn't fail. The Agile methods don't work." I have heard variations of this many times. However, if a specific process doesn't work, the Agile team must learn what needs to be changed to succeed and possess the collective ownership to make the change.

Let's go back to what we are really trying to do with Agile Development: delight our customers and provide business value. Mary Poppendieck, of lean-development fame, offers many keys to accomplishing this through the removal of waste. We learn what waste is in our internal processes and remove it. We learn that the sooner we look for defects, the cheaper they are to fix. Sometimes people say, "We get to done, done, done and then we do a system test." Have they learned the value of getting to done, done, done? In starting to use Agile methods, one leader's teams complained that they could not get to done, done, done in just two weeks. Her reply? "Then let's figure out how to do it in one week." And they learned how to do just that.

Read the rest of this article on Dr. Dobb's.

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
batye
50%
50%
batye,
User Rank: Ninja
6/2/2014 | 2:08:15 AM
Re: Common challenges
could not agree more interesting information, thank you... it like for everyone it a learning curve this days... I get overwhelmed with most upgrades and changes... like everyone else...
jagibbons
100%
0%
jagibbons,
User Rank: Ninja
5/30/2014 | 12:43:52 PM
Common challenges
Thanks for sharing this article. These are challenges that I'm seeing as we've moved our shop to agile over the past 18 months. We're still learning and still looking at ways to get it right. However, we do sometimes lose track of the value to the customer. That's when our wheels start to spin.
Slideshows
Top-Paying U.S. Cities for Data Scientists and Data Analysts
Cynthia Harvey, Freelance Journalist, InformationWeek,  11/5/2019
Slideshows
10 Strategic Technology Trends for 2020
Jessica Davis, Senior Editor, Enterprise Apps,  11/1/2019
Commentary
Is the Computer Science Degree Dead?
Guest Commentary, Guest Commentary,  11/6/2019
White Papers
Register for InformationWeek Newsletters
Video
Current Issue
Getting Started With Emerging Technologies
Looking to help your enterprise IT team ease the stress of putting new/emerging technologies such as AI, machine learning and IoT to work for their organizations? There are a few ways to get off on the right foot. In this report we share some expert advice on how to approach some of these seemingly daunting tech challenges.
Slideshows
Flash Poll