We have 5256 guests and 10 members online
Featured Whitepapers
- Apples, Oranges, and Acorns - All Agile Development Tools Are Not the Same
- One's Enough for Agile Application Development Management
- Requirements Management 101 – 4 Basics Everyone Should Know
- Tips on Requirements Traceability – Learn How to Control Change and Improve Quality
- Scaling Continuous Integration to Large and Distributed Teams
|
"Being" Agile and Lean - December 2009Maneuvering your, the team's and organization's way on the super highway of "being" agile and lean is our focus in this month's edition of the Agile Journal.
Based on empirical knowledge, Agile and Lean system-software development and delivery is achievable but difficult to achieve partly because of individual, team, and organizational beliefs, understanding what it means to be agile and lean and, the willingness to change and adapt. Additionally, available evidence shows that most individuals, teams and organizations can become agile and lean, but often fail because becoming agile is a reengineering, re-strategizing and cultural renewal effort. They simply are not prepared for the degree of change required to meet such transformational challenges.
The reinforcement of this is exemplified in Chapter 1 of Mike Cohn’s latest book Succeeding With Agile - Software Development Using Scrum. In that chapter, Mike insightfully talks about why becoming Agile is difficult, but worth the effort. In this month’s edition, we provide you with articles that, once read, will give you insights and enable you to begin to answer such questions as:
Alan Shalloway and James R. Trott in their article "Where to Begin Your Transition to Lean-Agile" emphasize the importance of getting your bearings and keeping your eye on the big picture. Bob Aiello shares a real life story that exemplifies the essence of being adaptive. Don McGreal and Michael McCullough in their article "Agile, Lean, or Something in Between" present some of the promises of both agile and lean when implemented separately and also explore when one set may be a better fit over the other or how they may be optimally combined. My article "Implementing Agile – Described in less than 700 words" distills how to implement agile down to the bare bones. This month's Agile Journal will serve you well as sign posts as you, your teams and organization embark and maneuver your way towards the adoption and actualization of being agile and lean; collaboratively and adaptively developing and delivering value-based system-software in a continuous flow incrementally. One of the greatest joys of this season is the opportunity to say THANK YOU for your readership and contributions to the agile community and to wish you the very best for the New Year. Sincerely, Russell Pannone Editor Agile Journal
|
|||||||||||||||||||||||||||||||||||||||
| Last Updated on Wednesday, 08 September 2010 10:04 |
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



Additionally, available evidence shows that most individuals, teams and organizations can become agile and lean, but often fail because becoming agile is a reengineering, re-strategizing and cultural renewal effort. They simply are not prepared for the degree of change required to meet such transformational challenges.






