Architects Zone

Marion is one of the founders of agile42 who specialize in Agile Coaching and Lean Management. In collaboration with an international team, Marion supports companies worldwide in introducing agile and lean methods, coaches and trains management teams and participates in the agile community. After finishing her pedagogical studies Marion specialized in marketing, communication and business development focusing in the IT and software development sector. Being in charge of marketing and press relations for several companies like TogetherSoft, Borland and NCH International she furthered her knowledge in the area of “Solution Selling”. She also published several articles on topics relating to traceability, collaboration and agile management. Marion has posted 3 posts at DZone. You can read more from them at their website. View Full User Profile

Agile Transition, what you need to know before starting

08.09.2012
| 1764 views |
  • submit to reddit
Published by: Apple iBook
ISBN: Apple ID: 550957382

Reviewer Ratings

Relevance:
5

Readability:
4

Overall:
5

Buy it now

One Minute Bottom Line

  1. There is no Blueprint to become agile or an agile organization.
  2. In truth, agile is not a well-qualified term, for it is often misused as a cool synonym for “reacting fast to changes."
  3. It is important to know that while Scrum is agile, the contrary is not true.

 

Review

You cannot "buy" agile. That's the main message of the eBook from Andrea Tomasini and Martin Kearns. To become an agile team, i.e. an agile organization, you need a cultural change. The responsibility, the communication, and the collaboration of everybody involved will probably need to change. Because each and every company or team works differently, many people find it helpful to see how becoming agile really looks. Andrea and Martin, both CSC and CST, give a lot of insight into actual projects, providing you with a quick understanding of an agile team structure. The four parts of the "Agile Reading Glasses (R)" are the foundation for every "Agile Change":
  • Empirical Process Control
  • Lean Principles
  • Pull-versus-Push System
  • Incremental Value Delivery
They also talk about helpful tools that can be used on a daily basis, and they make clear that there is no Blueprint for agility. Download the PDF or iTunes iBook
Published at DZone with permission of its author, Marion Eickmann.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

"Starting from scratch" is seductive but disease ridden
-Pithy Advice for Programmers