From The Editor

    • try.


    • Human aspects: There is a growing body of knowledge in the community that examines human dynamics and relationships that underpin all successful teams. Much of this work is taken from other disciplines and will be translated into Agile-ese for our readers.


    • Basics: Introductory materials for those who want to learn the basics of Agile development and practices. For example, in this month, we have an article that goes over the basic responsibilities of the Product Owner role.


    • Adoption: How-to articles that examine the process of successfully using Agile practices.


    • Principles and values: Agile practices derive from a set of core principles and values. Understanding of these principles and values enable teams to adapt Agile practices to fit their contexts.


    • Large organizations: More than ever, Agile software development is being adopted in large organizations that have completely different contexts and constraints than the smaller projects and companies where Agile development got its start. To get the promised benefits from Agile, practices are changed, adapted, and sometimes dropped all together to survive these different environments.


    • New ideas: We will also be bringing you regular articles that might not fall in the accepted definition of Agile development. This is very important as practitioners mold their understanding of Agile development to increasingly diverse situations, and address an ever-growing set of issues and problems.


Just as importantly here's what we won't be doing at the Agile Journal:


  • We won't be reinventing the wheel. There are several publications and resources currently available that address issues that are not in our core offering: provide our readers regularly with insightful articles. We will create a resources section to link out to those other sites, but will not be directly recreating their work.


  • We won't be accepting all submissions, in an effort to keep the quality of the articles high. At the same time, we will be working with new authors to help hone and polish their messages to bring them to the public.


  • We won't be focusing solely on accepted, mainstream, definitions of Agile. We will be coloring outside the lines to help the community evolve and make sure the next ten years of the Agile community are as successful and productive as the last ten.

Getting Involved:

As the new Editor-in-Chief of the Agile Journal I'll leverage my experience and ties to the Agile community to bring you, our readers, the highest quality articles to help you with your real-world issues in understanding, adopting, and adapting Agile principles, values, and practices.

Now, here's the catch, we don't have a team of writers at the Agile Journal working hard through the night to bring you these articles (although a few of us do pull the occasional all-nighter). All of our articles are contributed by members of the community who share their thoughts, experiences, successes, and - yes - failures. I invite each and every reader of the Agile Journal to consider sharing their experiences with the rest of the community by contributing articles on any of the subjects listed above. For those of you who are not up to, or are not interested in writing full articles, I invite you to leave comments on the articles - both positive comments and constructive criticism.

Amr Elssamadisy


Agile Journal


About the author

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.