We have 5249 guests and 9 members online
Home > Articles > Current Edition > The business case for agile

The business case for agile

E-mail
Written by CMC Media Staff   
Saturday, 09 May 2009 01:00

The business case for agile - may 2009Welcome to the May, 2009 edition of the Agile Journal.  As always we’ve got a lineup of great articles that will help you understand, apply, and adapt Agile software techniques to your day-to-day environment.

To start us off this month, John Rudd, the CFO of Solutions IQ, writes about the bottom-line value of Agile practices in The Business Case For Agility.  He describes how different aspects of agility – especially reducing work in process – can help reduce investment and lead time in an organization.

may-09-coversmallLaszlo Szalvay is back with the second article in his introductory series to Scrum.  In How Scrum Generates Increased Productivity, Part Two, Laszlo takes a look at arguably the most critical role on a Scrum team – that of the product owner.  Read this article to get an introduction to the responsibilities of a product owner and understand how that leads to the promised gains of Scrum.

Dan Mezick in Scrum and SVO-p will have you thinking hard about your vocabulary.  Dan relates the structure of our sentences that we use for everyday communication to our effectiveness in facing reality and ties that directly to the values espoused by Scrum.  This is a must read article that addresses the foundations of effective communication.

Robert Williams digs deep in Three Strategies for Task Allocation to describe different patterns teams split up their work during an iteration.  This is an insightful article that weighs the pros and cons of different task allocation strategies and their effects on team productivity, accountability, and self-organization.

Chris Matts has put together another comic strip for us on Feature Injection and furthers our understanding of feature injection, requirements gathering and their proper timing.

Brad Appleton reviews Agile Testing by Lisa Crispin and Janet Gregory and is very excited about the book and can’t recommend it enough.

Finally, this issue is my last issue as editor in chief of the Agile Journal.  I’ve thoroughly enjoyed the opportunity to help bring these marvelous ideas of our writers to the community.  If you need to contact me, you can do so on my website at http://www.elssamadisy.com/contact-amr.html.

Amr Elssamadisy
Editor in Chief
Agile Journal


Featured articles...

Agile Journal November 2009

The Business Case for Agility
Too many technology projects fail to deliver the promised value, and some do not deliver at all. Traditional project management methods when applied to software initiatives continue to frustrate financial professionals and offer poor risk mitigation. In the current economic environment, businesses are forced to reduce their capital budgets and cannot afford to make significant investments without more certainty of appropriate return.
Read More >>

Agile Journal November 2009

How Scrum Generates Increased Productivity
Part Two: The Product OwnerAs discussed in part one of this series, the Scrum framework is designed to be a lightweight management wrapper-a minimal set of practices that complement and hopefully improve an organization's existing business practices, processes and culture. However, because the Scrum framework is composed of relatively few roles, meetings, and artifacts, none of them are redundant or expendable. For organizations to unlock Scrum's potential-such as its ability to boost productivi...
Read More >>

Agile Journal November 2009

Scrum and SVO-p
Scrum is unique in that the management method is consistently direct. All communication in authentic Scrum is concise, direct and clear. Scrum encourages responsibility. The daily stand-up meeting actively encourages personal responsibility to execute on specific work, and to be accountable to the Team. The three questions of Scrum are questions related to accountability for specific commitments.
Read More >>

More articles...
Agile Journal November 2009
Three Strategies for Task Allocation
Iteration and release planning are keys to successful agile projects, but overall have a relatively small impact on a developer's day-to-day life, compared to the daily planning that takes place each morning.  The strategy a team uses to sign up for work has significant implications for what a developer's day will look like, impacts his work style and habits, and ultimately can significantly impact the overall success of the iteration.  Unfortunately, the agile community gives relatively littl...
Read More >>

Agile Journal November 2009
Second look, Requirements come second
My article, Requirements come second, in the February issue of the Agile Journal caused something of a fuss.  The piece was picked up by several more sites and was widely commented on - both on websites an in my inbox. I'm not entirely surprised by this reaction, I've been discussing this research for a year or so now and often find it surprises people.  Given this level of interest it is worth looking at how people responded. ...
Read More >>


Feature Injection - Part 3
So we've fixed the process, and we've identified the value. Now, how dowe identify the minimum set of features to deliver that value?
Read More >>

Agile Journal November 2009
FEATURED BOOK: Agile Testing - A Practical Guide for Testers and Agile Teams
Lisa Crispin, author of the 2002 book Testing eXtreme Programming, and Janet Gregory have collaborated together to create a magnificently pragmatic tome that is a true tour de force in its field: Agile Testing: A Practical Guide for Testers and Agile Teams. The book is exactly what its title says, and should quickly become “the bible” for all would-be agile testers. ...
Read More >>

Last Updated on Wednesday, 08 September 2010 10:08
 
Cialis

Agile Marketplace - Announcements and Special Offers

The Business Case for ALM Transformation
Are legacy systems holding your company back?  Breakthrough these technical constraints with an open and scalable environment that meets your unique business need to transform. There is no reason to be locked into an obsolete platform. The output of a number of recent transitions from legacy systems, this is practical white paper shares lessons learned and illustrates how guidance and enablement can pave the way for change.
Download this Whitepaper