Hallo all
As Nick mentioned, DocOps is an initiative closely associated with
Confluence. I was aware of the movement when it started, although I decided
not to participate even though I was working at Atlassian and very involved
with tech docs on Confluence. There was just too much going on at that
time. I haven't seen any adopters of DocOps other than peopleworking on
Confluence, though I don't see any roadblocks to people adopting the ideas
using different technologies.
Interestingly, I saw this tweet a few weeks ago from K15t Technologies,
linking to a blog post about DocOps:
https://twitter.com/k15tsoftware/status/738392346048356352
As you can see in the above thread, I responded asking whether there are
any DocOps implementations other than on Confluence. The response was that
K15t doesn't know of any.
Here's the blog post mentioned in the tweet:
https://www.k15t.com/blog/2016/06/scroll-add-ons-power-docops-but-don-t-take-our-word-for-it
?
Background on K15t Software: They're a software house, based in Germany,
who develop extensions for Confluence targeted specifically at the
technical writing community. They're good folks, knowledgable and skilled
in Confluence, software, and tech docs.
Cheers
Sarah
On 8 July 2016 at 17:25, Nick Shears <nshears@xxxxxxxxxxx> wrote:
I’d not heard the term “DocOps” before, Stuart, but I’m grateful for the
introduction to it.
In many ways it describes what I do now. Our development environment is
Agile. It’s a SaaS product with frequent releases, which are deployed by
DevOps. The documentation is WebHelp, deployed independently of the app
itself. I can therefore update that after a release, for example. And
changes can be live within hours (or possibly even minutes) of the
requirement being identified.
I must explore DocOps further. First three links I’ve found:
James Turcotte (of CA), September 11, 2014 – the original post to which
Tom Johnson’s piece was a follow-up:
https://www.linkedin.com/pulse/20140911020510-10335988-the-ca-technologies-docops-platform-phase-1
James Turcotte, November 16, 2014 – linking to a sponsored webinar about
it:
https://www.linkedin.com/pulse/20141115160148-10335988-learn-how-ca-technologies-broke-the-rules-their-docops-approach-to-agile-technical-content
Will Kelly, October 13, 2015 – blog about DocOps in context of agile dev:
https://www.liquidplanner.com/blog/the-docops-trend-applying-agile-and-devops-to-technical-documentation/
Ironically, Turcotte developed CA’s DocOps approach using Confluence. We
use Confluence internally, but not for anything customer-facing.
Cheers,
Nick
*From:* austechwriter-bounce@xxxxxxxxxxxxx [mailto:
austechwriter-bounce@xxxxxxxxxxxxx] *On Behalf Of *Stuart Burnfield
*Sent:* Friday, 8 July 2016 3:49 PM
*To:* Austechwriter
*Subject:* atw: DocOps
I read this term today for the first time on a usability list: DocOps. The
name is by analogy with DevOps and it originated from CA.
DocOps: Interview with Jim Turcotte
http://idratherbewriting.com/2014/10/21/docops-interview-with-jim-turcotte/
*"DevOps provides an extremely agile development approach through a
combination ofcollaboration, automation, continuous integration and
analytics. The end result is the ability to change software in minutes
rather than days, weeks, or months ...DocOps is the content sibling of
DevOps. It's about having a highly-collaborative content platform that
allows product information to be continuously developed, even after the
product release."*
It sounds interesting. Does anyone have any experience with it?
--- Stuart
