Comments
4 Signs You're Doing Agile Development Wrong
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 3 / 3
holavana
50%
50%
holavana,
User Rank: Apprentice
4/7/2014 | 3:55:13 PM
Re: Releases Every Few Weeks
@DavidNIL

I was in a similar environment where a regular Change Request process took minimum of 3-4 weeks. But we still had agile teams delivering in sprints of 2-4 weeks. The trick is to invest time and effort to plan ahead and anticipate the needs a few sprints down the road. This can be facilitated by the Scrum Master as part of removing road blocks.

ALso in our organization, we were able to adapt a modified Change Request Contorl policy so that some of the change requests ( with moderate impacts)  could be approved by a representative of the Change control Board working closely with the teams. but is not a formal member of Change Approval Group. The scope of such changes allowed were explicitly defined as part of a Master Change Request and had to be approved by the board. The validity of approval was provided for six months and renwable.

 
Somedude8
50%
50%
Somedude8,
User Rank: Ninja
4/7/2014 | 1:54:33 PM
Agile or...
Friend of mine was at a large shop that was making the transition to agile. One day in a meeting, a frustrated PM said "Are we gonna be agile or are we gonna get this project done?"

I am not making this up!
2h74webere
50%
50%
2h74webere,
User Rank: Strategist
4/7/2014 | 1:40:46 PM
Re: The 5th Sign....
Bob - I agree!  Hopefully doing 1-4 makes getting real feedback from actual customers a cheaper, easier, and more pleasant endevour.  Almost like we want customers to be able to tell us what they want in the product next!
Bob Schatz
100%
0%
Bob Schatz,
User Rank: Apprentice
4/7/2014 | 1:21:20 PM
The 5th Sign....
Great article Erik! I would add just one more thing that I feel is important enough to be the 5th sign...Are Your Customers Happy?

None of this means anything if you can't solve your customers problems. Are you doing the right things, and doing them right. You certainly need to do 1 thru 4 ultimately leading to the biggest test...5.
DAVIDINIL
50%
50%
DAVIDINIL,
User Rank: Strategist
4/7/2014 | 1:09:15 PM
Releases Every Few Weeks
The change control process takes 3-4 weeks at my company.  In order to release 3 weeks from today, I have to have proof of testing completed today.  Agile is just not possible in this kind of environment.  At large companies with ultra complex/ultra integrated app flows, executives are much too afraid to let very many rapidly developed apps to be released into the production environment for fear that they would bring down mission critical apps. 
ChrisMurphy
50%
50%
ChrisMurphy,
User Rank: Author
4/7/2014 | 10:00:57 AM
The Unhappiness Red Flag
This "unhappy developer" warning sign really resonates with IT execs I've spoken to recently. Developers are motivated by knowing they're building something that will be used and appreciated. If they get that feedback -- good or bad -- every few weeks or months, rather than after a 6 or 12 or 18 month dev cycle, they're more likely to be happy. 
<<   <   Page 3 / 3


IT's Reputation: What the Data Says
IT's Reputation: What the Data Says
InformationWeek's IT Perception Survey seeks to quantify how IT thinks it's doing versus how the business really views IT's performance in delivering services - and, more important, powering innovation. Our results suggest IT leaders should worry less about whether they're getting enough resources and more about the relationships they have with business unit peers.
Register for InformationWeek Newsletters
White Papers
Current Issue
InformationWeek Must Reads Oct. 21, 2014
InformationWeek's new Must Reads is a compendium of our best recent coverage of digital strategy. Learn why you should learn to embrace DevOps, how to avoid roadblocks for digital projects, what the five steps to API management are, and more.
Video
Slideshows
Twitter Feed
InformationWeek Radio
Archived InformationWeek Radio
A roundup of the top stories and trends on InformationWeek.com
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.