We have 5245 guests and 8 members online
Home > Articles > Current Edition > Post-Agilism

Post-Agilism

 E-mail
Written by CMC Media Staff   
Tuesday, 11 May 2010 01:00
Post-Agilism - May  2010

Agility

“When it comes to the future, there are three kinds of people: those who let it happen, those who make it happen, and those who wonder what happened.”  -  John M. Richardson, Jr.

We use to have the pony express delivering letters helping to keep folks in touch with one another. Then came the telegraph and telephone. Now we've gone back to letter writing, in the form of email, text messaging, or Twitter to keep in touch.

Just like the seventeen like minded individuals did in 2001, when they came up with the Manifesto for Agile Software Development, it is time to reflect on today’s reality, specific to the fundamental practices underlying our industry’s and your system-software development approach and look to the future.

This issue of the Agile Journal is all about reflecting on our past and present and shaping the vision of the future for system-software development.

Bulletin:  CIO speaks to us from the year 2020, as reported in the article 2020 Best CIO Acceptance Speech, written by Anupam Kundu & Tiffany Lentz.

Geoffrey Bourne in his article The Marriage of Lean, Scrum and Extreme Programming (XP) - How to Align Agile Across an Organization, pragmatically and insightfully describes for us a bright future for system-software development where we leverage the symbiotic relationship of Lean, Scrum and XP across an organization.

In my article Agile Software Development – Past, Present, Future, I reflect upon and leverage what we know about and can learn from the past and present system-software development approaches and propose an updated version of the agile manifesto, based on today’s reality.

In the article Insights from three Agile/Lean Product Development Thought Leaders, Mark Lines (Unified Process Mentors, Co-Founder), Ryan Martens (Rally, CTO & Founder) and Jean Tabaka (Rally, Agile Fellow), industry thought leaders and agile/lean product development experts, share insights on their perspective with respect to the past, present and future of system-software development.

Rowan McCann, in his article Successful Agile Needs Teamwork, shares insights on:

  • Work values
  • Shared values
  • Distributed teams

Carson Holmes, in his article SDLC 3.0 Provides a Platform for Integration, offers insights on putting an end to the iterative method wars of the SDLC 2.0 generation and offers a vision for a pragmatic centrist platform to unify the process of system-software development.

Have a great reading experience!

Your agile buddy and editor,
Russell Pannone
Editor
Agile Journal
Featured articles...


2010 Best CIO Acceptance Speech
by Anupam Kundu & Tiffany Lentz
For people who do not know me, it must be difficult to comprehend how I became the CIO of this mega multinational conglomerate. It has been an uphill task to move from the server rooms to this boardroom; believe me that technology skills alone were not good enough to make this gradual but sure leap. Looking back, I give credit to a heady concoction of Portfolio Management experience, stead fast communication, and adoption of Agile principles and practices across all the IT divisions that made this happen. And also a lot of good old luck.
Read More >>


The Marriage of Lean, Scrum and Extreme Programming (XP): How to Align Agile Across an Organization
by Geoffrey Bourne
“If you don’t know where you’re going, you’ll end up somewhere else.”

- Yogi Berra

Over the years, many flavors of Agile have emerged: Scrum, Lean, Feature Driven Development (FDD), Agile Unified Process (AUP) and Extreme Programming just to name a few. These methods have numerous complementary and distinguishing features, but the gamut of choices can be confusing and disorienting - as if being told to choose the best from 31 flavors of ice cream.  Return on Investment (ROI) is important to me, so Lean must be the answer.  But wait, I also want to be agile with my business priorities so I’ll choose Scrum.  On the other hand AUP facilitates scaling, so... we are left wanting a simple question answered: “Which Agile method should I choose for my organization?”

Read More >>



Agile Software Development – Past, Present, Future
by Russell Pannone
I’ve come to realize system-software development methodologies have in common with nature the life span of infancy, childhood, adolescence, adulthood, and aging. I have also come to realize methodologies, sometimes as part of their life span, enter into a relationship or marriage with other methodologies; like has happened with Agile Software Development and Lean Manufacturing.

Additionally, methodologies of the past and present have an associated taxonomy, new jargon and technical terminology or idiomatic expressions of the practitioner. They also tend to reuse old jargon but with different connotations.
Read More >>

More articles...

Insights From Three Agile/Lean Product Development Thought Leaders
by Mark Lines, Ryan Martens, and Jean Tabaka
Here is what Mark Lines (Unified Process Mentors, Co-Founder) has to say: The fact that basic agile concepts are so easy to learn, as well as the proliferation of certification courses with very little investment required has had both positive and negative effects.  Certainly the mindshare of methods such as Scrum has exploded in our industry and people are excited about the benefits that agile can deliver in terms of elimination of waste and timely delivery of systems with immediate ROI.
Read More >>


Successful Agile Needs Teamwork
by Rowan McCann
Agile embraces the concept of self-organizing teams but they are inherently unstable and are only successful when the ‘Leadership – Self-Management’ dilemma is understood and dealt with.  Too much central control destroys agility, inhibits creativity and resists change.  Too much self-management leads to chaos and anarchy and destroys a team.  A successful Agile Team needs to operate as far along the continuum towards self-management as it can, without tipping over into chaos. You can’t just eliminate the PM role and say to a software development team, “OK, you’re now an Agile Team – you need to self-organize”. This is a recipe for failure, and one of the reasons why many organizations resist the Agile approach.
Read More >>


SDLC 3.0 Provides a Platform for Method Integration
by Carson Holmes
Even before written history, mankind has followed methods to invent, build, and use tools.  As our tools have evolved so have our methods, and in today's software industry there are lots of articulations and communities built around software development methodologies.  Despite the zealous beliefs within some of these communities, no single method is the silver bullet or the one truth from which to engineer and craft software in all contexts.
Read More >>





Last Updated on Wednesday, 08 September 2010 09:58
 
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