I wish there was a book entitled "How to Write Your First Letter as an Editor", unfortunately there is none that I am aware of, so please bear with me. As the new Editor-in-Chief of the Agile Journal, I would like to introduce myself and tell you a little about where we will be going with the Agile Journal over the next few months.
I have been in the Agile field as a practitioner since 1999 when I was in a team that learned about a little known process called eXtreme Programming to save a death march project. I've been infected with the Agile bug ever since and have been sharing my knowledge ever since. Throughout the years I've been lucky enough to learn from many talented people and teams learning about, adopting, and adapting Agile techniques to build better software. A little over a year ago, I co-founded Gemba Systems and have been focusing exclusively on helping teams select, adapt, and adopt Agile practices to transition to a more effective software development process.
When the Agile Journal started up a little over two years ago, I became an avid reader and an occasional contributor. The Agile Journal was one of the mainstays of my reading to keep up with what others were doing in the field; what was working, and just as importantly, what was not. I've also written two books focused on adopting Agile practices: Patterns of Agile Practice Adoption: The Technical Cluster and Agile Adoption Patterns: A Roadmap to Organizational Success .
To summarize, I am a hands-on practitioner of Agile software development techniques actively helping organizations leverage Agile practices in context to build better software. I also have been and continue to be an active participant in the Agile community. And now, I am also Editor-in-Chief of the Agile Journal.
The Vision for the Future of the Agile Journal
There is currently no one place online that I can recommend when one of my clients wants to start reading about Agile development. My vision for the Agile Journal is to be that one place to visit when thinking about Agile software development. The only way to realistically achieve that goal is to do one thing really well, and link to other sites for those issues that we don't cover.
The Agile Journal's main focus is to provide our readers regularly with insightful articles; that's what we do well and what we will continue to improve upon. Furthermore, we are planning a redesign of our site to make the wealth of information more accessible. Finally, we plan to add and regularly maintain several reference sections to help our readers find other useful resources online.
What to expect:
Over the next few months we will be incrementally introducing the following changes to the Agile Journal, think of it as a backlog for the project of taking things to the next level:
- Starting next with the month of October 2008, we will be publishing articles throughout the month instead of all at once. This will keep things fresh and give our readers at least one new article to read every week.
- We will be going towards a column format, where every issue will have a variety of topics covered instead of one issue per topic. This will give everyone something that is of potential interest and value in every edition. Here are the different columns that we have in mind to more accurately reflect the current state of Agile development and serve the needs of the community:
- Business case: "Business value" is an all too easily promised result of adopting Agile practices, but we have yet to build an effective vocabulary with executives with responsibilities vastly larger than the success of one or two software teams. We will be bringing you articles that you can give to your boss, or your boss's boss, to help them understand how Agile development can help and why they should seriously give it a