I'm proud to announce that as of php|architect Magazine's November issue, I will have a monthly column on the subject of Enterprise PHP.

The series of columns will follow the contents of the book, but from a different angle. I will interview people from the field to see how they do things in their environment. This should give practical insights and tips directly from people that are involved with PHP on a daily basis.

If you are willing to be interviewed for one of the articles (on anything related to the PHP development lifecycle), send me an email at enterprisephp @ phparch.com.

You can subscribe to the magazine here.

Marco Tabini from php|architect has notified me that the Enterprise PHP book is now in print. Those of you who have pre-ordered should receive your copy shortly.

I'm quite happy that the initial feedback on the PDF version has been positive. Here are the first 2 reviews of the book:

Review by Chris Cornutt of phpdeveloper.org
Review by David Bernal of htmlist.com

If you purchased the book, thanks, and remember that any feedback is welcome!

Greetings,
Ivo

The Enterprise PHP book contains my recommendations for a PHP development life-cycle. But my view is certainly not the only view. If you have opposing views, recommendations, additions, please let me know by posting a comment to this post.

Also, any general comments and criticism on the book are very welcome. Feel free to post your comments below.

If you rather send me private feedback, please send an email to ivo at jansch dot nl.

I got a few requests for the table of contest of the Enterprise PHP book. Here it is:

Part 1 - Background

1. From the attic to the cubicle
2. PHP in the enterprise

Part 2 - Enterprise Development

3. The team
4. Requirements Gathering
5. Planning
6. Architecture
7. Tools
8. Building blocks
9. Security
10. Development
11. Quality Assurance
12. Optimization
13. Deployment
14. Implementation
15. Operations
16. Maintenance

Part 3 - the big picture

17. Development Methodologies
18. Project Management

As you can see, the entire development lifecycle is covered. Many of this applies to other languages than PHP as well, but I've focussed it on PHP development projects.