Have a question? Get in touch.

To speak to a member of our team about how we can support you, click here.

In Agile, Haste Makes Waste

You’re in the final stretch towards completing the documentation for a set of products when you receive some last minute changes.

Since all of your content was built using DITA XML, you quickly open the affected topics, make the changes, tag the content based on the specific models affected, publish, and send it for review.

And you are done! Or are you?

Components of Agile

  • Welcome changing requirements, even late in development
  • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale

DITA XML was built for reuse and offers a perfect content development solution for an Agile team. But the short development times and constant delivery takes its toll on the writers – and the content. Often writers are left with little ‘on-time’ to plan or maintain content.

Which begs the question: In our haste to meet deadlines, are we creating more waste?

What is waste?

When content or topics are reused, more information is added over time to help identify the applicability of the content. For example, you may mark out sections of the doc that should be seen only in a specific model or release.

This can cause two potential waste scenarios. Either you spend more time figuring out where the content or topics belong and where it may be easier to create a whole new topic, or you have multiple topics talking about the same thing. In either case, you can end up contributing to documentation waste.

How can you eliminate or reduce documentation waste?

Create a Solution Matrix.

Customers no longer use products, they use solutions. With every iteration of a product, there will be tons of crossovers and dependencies. Hence, create a matrix of features and the products that support it. And maintain this Solution Matrix in a location that everyone can access.

Before you start working on a feature, a quick look at the Solutions Matrix can help you figure out who may have already created similar content or may be interested in the content you may be creating.

In Agile teams, use the release planning time to update and maintain the matrix.

Collaborate as you create content.

If you are creating new content and know there are other writers in your team who may need your content, notify them before you start work, and include these writers in the review of the content as well.

If you are looking to make updates to already existing content, notify the owner about the changes before make them, and include the content owner during the content reviews.

Involving other writers allows for issues and suggestions to be identified and managed earlier in content development, and reduces the possibility of mistakes. Writers in Agile teams can use planning and sprint meetings to identify topics that need to be updated, and other writers who will be able to help with the process.

Is it time to create all new reusable content?

Good writing is the core of all reusable content. Sticking to the basics of topic-based writing makes the content more portable and reduces the time we spend (or waste) trying to make it reusable.

  • Focus on the content that’s required
  • Think about the audience: what do they need?
  • Generalize content where applicable
  • Identify variance (audience, product, release) and separate it from common content

Know when to walk away.

Just because there is a similar topic, don’t feel you have to reuse it. If the variations in the content are significant, you’ll likely spend more time managing the variation than you would by creating and managing an entirely new topic.

Keep it clean and lean.

Most Agile teams use the last few sprints before the official release for regression. It’s a good time to do some end-to-end reviews of the content and some basic housekeeping before you start preparing for the next release. Look for duplication, filter metadata that is no longer required, and look for topics that can be retired.

By following some of the tips above, your content will be easier to manage, and leave you with more time for ‘on-time’ to plan your content. This will create a better experience for your team and better content for your clients.


Rashmi Ramaswamy is a part of Innovatia’s Information Architecture team with a varied experience – support, training, tech pubs, project management, and information architecture. Her experience working with different teams helps her bring the best practices from each team to achieve a common goal – customer satisfaction.


  1. Larry

    Very true Rashmi. Great suggestions – thanks!

  2. Ruchi

    Interesting piece Rashmi !! I liked your thoughts about knowing when to walk away , as we unknowingly waste lot of time reworking and modifying !!


Submit a Comment

Your email address will not be published. Required fields are marked *

Can Videos Replace Authoring?

The way we learn is changing, and so is our source for information. As the rate of technological adoption explodes globally, technical writers are left asking the question: can video replace the manual?
Read More

Investigate to Innovate

Research. Its value is unquestioned, yet its place in our business lives is often pushed to the bottom of our to-do list. How do we defend taking time for research? The simple answer is that research and investigation are critical to innovation.
Read More

Gone in (less than) 60 Seconds

You've got less than 59 seconds to capture a users attention online. How can you ensure that your users find what they need - quickly and efficiently?
Read More

The Demise of the Manual

Customers want more than the traditional manual. So what's next? From the transition to digital, to the internet influence, how we use content is changing. Along with it it how we expect content to act.
Read More

Motivating Through Gamification: Welcome to the New Age

How can we leverage that fun, or that desire to play, into our everyday tasks? It’s a fine dividing line. While we want to capture the enthusiasm in our daily lives, we must also be adults and be serious to get the task done.
Read More

Quality from Collaboration: Getting more from your documentation

Technical writers are experts in many things – writing, instructional design, audience analysis, feature testing and research – but it is our professional relationships, and our collaboration through them, that become the key to creating quality, usable content.
Read More

In Agile, Haste Makes Waste

DITA XML offers a perfect solution for the Agile team. But the short development times and constant delivery takes its toll on writers and content, creating waste along the way.
Read More

Human Editors vs. Tools: Finding common ground

If you are relying completely on automated editing tools, you could be compromising content quality. Consider the positive impact on your content when you combine the power of both automated tools and human editors.
Read More

Unitasking in a multitasking encouraged world

We live in societies that encourage the multitasker. The mentality invades our digital lives, too; productivity apps declare that we can get more done than ever. But are we truly getting more done? Whatever happened to the now quaint notion of focusing on one task (unitasking)?
Read More

Leveraging Analytics: Putting big data to good use

If senior innovation experts can see the value in analyzing big data, then perhaps you should too. According to GE Global Innovation Barometer 2016, 73% of senior innovation experts that participated in the survey have increased their ability to analyze big data. This is up from 43% reported in 2014. This is a dramatic and noteworthy increase.
Read More
Share This