21
1 1 DITA maturity model in a SCRUM environment May 2011, Crawley

Congility 2011

Embed Size (px)

DESCRIPTION

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

Citation preview

Page 1: Congility 2011

11

DITA maturity model in a SCRUM environment

May 2011, Crawley

Page 2: Congility 2011

2

Contents

• About Agfa HealthCare

• History

• DITA at Agfa

• DITA maturity model

• Content strategy – step-by-step

• Summary

• Q&A

C

Page 3: Congility 2011

3

About Agfa HealthCare

• Tailor made radiology solutions

• Specific solutions for • Women's care

• Cardiology

• Orthopaedics

• Hospital-wide solutions to optimize clinical and administrative processes

C

Page 4: Congility 2011

4

About us

• Members of the documentation team

• Scrum team

• Expert team – centre of excellence

C

Page 5: Congility 2011

5

History

• Content focus• Reuse and single sourcing

• Geared to translation/localization needs

• Problem• Limitations of method / structure

• Tool constraints

• Solution• Implement DITA

• Acquire CMS

C

Page 6: Congility 2011

6

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

Page 7: Congility 2011

7

DITA maturity model

• Investment vs return

• http://na.justsystems.com/files/Whitepaper-DITA_MM.pdf

E

Page 8: Congility 2011

8

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

C

Page 9: Congility 2011

9

Content strategy - Step 1

• Convert legacy content to CMS

• Apply DITA to our legacy content

• Train ourselves

E

Page 10: Congility 2011

10

Level 1: Reusable topics

E

Page 11: Congility 2011

11

Content strategy - Step 2

• Generate new content • Create templates

• Build further on legacy content• Reorganize

• Introduce minimalism• Refactor content

C

Page 12: Congility 2011

12

Level 2: Standardization

C

Page 13: Congility 2011

13

Content strategy - Step 3

• Different output formats

• Continuous integration• Bi-weekly builds

• Translation optimization• DITA to XLIFF

• Single sourcing / custom output• Filtering and flagging

E

Page 14: Congility 2011

14

Level 3: Automation and integration

E

Page 15: Congility 2011

15

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

C

Page 16: Congility 2011

16

Level 4: Collaborative content

C

Page 17: Congility 2011

17

Content strategy - Step 5

• Feedback loop with users• DITA to wiki or knowledge portal

• Workflow- and persona-baseddocumentation• Optimize metadata

• Semantic web technology

E

Page 18: Congility 2011

18

Level 5: Interactive content ecosystem

E

Page 19: Congility 2011

19

Content strategy - Step 6?

• Reuse unstructured content

• Text mining

C

Page 20: Congility 2011

20

Summary

E

Page 21: Congility 2011

2121

Q&A