Achieve Your Content Performance Goals
Agility isn’t difficult. What is difficult is sustaining a rapid work pace without knowing why, without having context. Context is especially important for product content developers. That is why my proposed ideal for an agile content development system continuously provides context for the work at hand.
I’ll explain in detail here. But first let me provide context for this blog post.
Read more
Sad as it is to say, self-directed, collaborative, and agile product development teams often don’t get content. That is, they don’t really understand where content comes from, how it is best developed, how to work with content creators, what’s required of the team as a whole, and why developing content can sometimes take longer than a 2-week sprint.
So it is often up to content professionals to educate (constantly), adapt (when necessary) and, above all, speak up about their requirements.
Read more
As product teams have adopted Agile development methodologies, product content professionals often find themselves stuck between agility and review cycles.
How can quality product content be developed in two-week sprints? Where do content strategy, content operations, and content standards fit into the constant evolution of software products? Where do the various disciplines within the content continuum fit in? (For example, UI, Help, API, and Services content?) How can everyone work together to deliver product content that is consistent, useful, accessible – and agile?
Read more
DK Consulting of Colorado 