[teampractices] Good read on Dev Ops and empathy

[James Douglas]

Interesting article, thanks for sharing!

> It’s about understanding what other parts of the system are trying to
say: other people, certainly, but not just the people in your development
group, or in your development and operations groups. And once we grasp
that, we’re way beyond tools.

> There’s a value to structure, both in organizations and in code, and it’s
worth sacrificing some performance to gain the benefits of structure.

Together, I think these two points come fairly close to capturing the
essence of user stories: being deliberate about structure and organization
(e.g. by curation and prioritization of the backlog) and addressing the
needs of the user by truly understanding them in their contexts.

<plug>My take[1][2] on defining DevOps, though more development-focused,
shares much of the philosophy of this article and might be an interesting
follow-up.</plug>

1. Video: https://www.youtube.com/watch?v=sZYAFWTyOlE
2. Slides: http://earldouglas.github.io/scala-cd/sbtb-2014/

Cheers!
James


On Tue, Feb 10, 2015 at 1:31 PM, Max Binder <mxbndr at gmail.com> wrote:

> Arthur suggested this might be a good place to share this.
>
> http://radar.oreilly.com/2015/02/what-is-devops-yet-again.html
>
> _______________________________________________
> teampractices mailing list
> teampractices at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/teampractices
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.wikimedia.org/pipermail/teampractices/attachments/20150210/5ebc3538/attachment.html>