• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Paul Clapham
  • Bear Bibeault
  • Jeanne Boyarsky
  • Ron McLeod
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Jj Roberts
  • Stephan van Hulst
  • Carey Brown
  • salvin francis
  • Scott Selikoff
  • fred rosenberger

"Agile Adoption Patterns: A Roadmap to Organizational Success"

Ranch Hand
Posts: 76
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Amr,

So glad the title wasn't: "Agile Adoption Patterns: A Roadmap to Organizational Effectiveness".

Why this book?
Why now?

Will having "Agility Patterns" defined make it easier to convince management about the need to change?

Posts: 37
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Mike,

Good questions. Let's get the title question out of the way first, this is a hands-on, how-to, book focused at adoption - hence Agile ADOPTION Patterns. That is, it helps you answer the question "what practices should I adopt given my environment" and "how do I go about adopting those practices". There are tens of books out there that answer "what is" Agile development, but precious few that tell you how to get from wanting to adopt Agile to the point where you are successfully practicing Agile and getting the business value from it.

Now, as for convincing management, it really comes down to speaking their language and knowing their priorities. The language of business values and current pains or smells.

Check out the freely available chapter 5 on InformIT to get an idea of what I mean. Furthermore, each patterns starts with a description of the business value it delivers, therefore it helps you decide/convince which practices are good for your given context and your organization's goals (and hopefully this coincides with your manager's goals).
There are no more "hours", it's centi-days. They say it's better, but this tiny ad says it's stupid:
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic