[Fuxy]

I think there is a fundamental disconnect between what DevOps is and the classical business organization structure.

DevOps is not a department and it will not work if it is a department DevOps is a way of doing things to achieve maximum efficiency and everyone on development and operations must embrace it for it to work.

If either development or operations resist the change then either the resisting members should be eliminated or the switch over to the DevOps way aborted.

DevOps doesn't work without cooperation and effort from all team members.

[digi_owl]

So in essence, devops treat every projects as if it was a startup? That is, to hell with departments, managers and lines of communications, one project, one team, one office?

[Fuxy]

Not quite, Managers can be separate, accounts can be separate, advertizing can be separate etc. but Development and Operations must be treated as one unit no separation.

In other words anything that can have a line of communication and still work can stay as it is but in order for DevOps to work development and operations must essentially become one with both developers and sysadmins working together on architecting a flow that works for both of them.

One office and one project is not really a requirement but it helps a lot in the beginning however if you can keep the cooperation a culture alive even working remotely could work.

The key is people who are always willing to learn and try new things and putting effort into change and staying on the same page with their teammates.

[michaelt]

So who gets the production system and database root passwords?