Congility 2011
Upcoming SlideShare
Loading in...5

Congility 2011



How DITA can help you to integrate in an agile development environment, illustrated by the DITA maturity model

How DITA can help you to integrate in an agile development environment, illustrated by the DITA maturity model



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • This presentation is not about our DITA implementation or migration. A short summary of why we migrated to DITA to provide a bit more context to the rest of the presentation.
  • So there we were with a brand-new CMS, DITA implemented, migrated content. Where would we go from here. How could we take this further?
  • Then we came across the following DITA maturity model. We noticed that we had already covered a few steps, and this inspired us to move on with DITA, getting more out of our content. It also helped us to phase and plan as the model provides logical incremental steps.
  • We started working on our own DITA maturity model.
  • We had already gone through this step – it is the one we discussed in an earlier slide on how we adopted and implemented DITA.
  • And this is how it reflects in our maturity model. Go over what we invested. And what we got out of it.
  • A few words on minimalism. Resulted from customer feedback and a content audit. Things to mention on minimalism? - - -
  • Go over what we invested. And what we got out of it.
  • Up to now, only PDF. We started experimenting by creating online output without having to tweak too much using the OT. CHM. We started to follow the build procedures that worked with bi-weekly builds -> process new developments coming from the sprints. Our bi-weekly contributions are not in line yet with development. We started using XLIFF to improve communication with our translation office (TO). And we started creating market-specific output using filtering and DITAVAL.
  • Go over what we invested. And what we got out of it.
  • Explain DoR. Docu in DoR = define what is needed in every user story to build documentation on. In acceptance criteria: define the expections wrt documentation in acceptance criteria. DoD: a user story is not ready until its documentation is ready. Start of bi-weekly documentation deliveries in line with development.
  • Go over what we invested. And what we got out of it.
  • Go over what we invested. And what we got out of it.

Congility 2011 Congility 2011 Presentation Transcript

  • DITA maturity model in a SCRUM environment May 2011, Crawley
  • Contents
    • About Agfa HealthCare
    • History
    • DITA at Agfa
    • DITA maturity model
    • Content strategy – step-by-step
    • Summary
    • Q&A
  • About Agfa HealthCare
    • Tailor made radiology solutions
    • Specific solutions for
      • Women's care
      • Cardiology
      • Orthopaedics
    • Hospital-wide solutions to optimize clinical and administrative processes
  • About us
    • Members of the documentation team
    • Scrum team
    • Expert team – centre of excellence
  • History
    • Content focus
      • Reuse and single sourcing
      • Geared to translation/localization needs
    • Problem
      • Limitations of method / structure
      • Tool constraints
    • Solution
      • Implement DITA
      • Acquire CMS
  • DITA at Agfa
    • Goal
      • Find a solution to our problem
    • Execution/roadmap
      • Map IMAP to DITA
      • Information model for Agfa
      • Train authors
      • Implement CMS
      • Migrate content
    • Where do we go from here?
    DITA E
  • DITA maturity model
    • Investment vs return
  • DITA maturity model at Agfa
    • Content strategy based on the model
    • Mapped to our needs
      • What are our goals?
      • Investment: what do we need to do?
      • Return: What does it deliver?
    • Scaled to our workflows
      • Move from waterfall to agile
      • Collaborative authoring
      • Path to acquire customer input
  • Content strategy - Step 1
    • Convert legacy content to CMS
    • Apply DITA to our legacy content
    • Train ourselves
  • Level 1: Reusable topics E
  • Content strategy - Step 2
    • Generate new content
      • Create templates
    • Build further on legacy content
      • Reorganize
    • Introduce minimalism
      • Refactor content
  • Level 2: Standardization C
  • Content strategy - Step 3
    • Different output formats
    • Continuous integration
      • Bi-weekly builds
    • Translation optimization
      • DITA to XLIFF
    • Single sourcing / custom output
      • Filtering and flagging
  • Level 3: Automation and integration E
  • Content strategy - Step 4
    • Content based on user stories
      • Documentation added to Definition of Ready
      • Documentation added to acceptance criteria
    • SMEs create draft content
      • DITA/form-based templates
      • Documentation added to Definition of Done
    • Integration with development
      • Link content to requirements
      • Metadata
  • Level 4: Collaborative content C
  • Content strategy - Step 5
    • Feedback loop with users
      • DITA to wiki or knowledge portal
    • Workflow- and persona-based documentation
      • Optimize metadata
      • Semantic web technology
  • Level 5: Interactive content ecosystem E
  • Content strategy - Step 6?
    • Reuse unstructured content
    • Text mining
  • Summary E
  • Q&A