Do you need a Documentation Manager when Technical Authors are embedded into Agile project teams?

Earlier this week, I was asked my opinion on whether a Documentation Manager was needed when the individual Technical Authors are embedded into Agile project teams.

My response was that a Documentation Manager mainly provides people management, project management, process management and content management. If a Technical Author is a member of a software project team, then that team’s Project Manager is probably providing the people management and the project management to the writer.

That leaves the need for someone to manage the processes and manage the content. I suggested managing the content could be done by someone with the role of Editor (or “Content Wrangler”). They might also look after the processes, or they could have another writer take on that responsibility.

It’s then a decision as to whether the organisation sees these roles as senior to the technical writing positions, or as a specialism and consequently on the same job grade.

It does leave the management of the writers’ career progression falling through the cracks, unfortunately.

How do others deal with this issue?

Managing documentation projects – Sage Technologies case study

Below is an interview between Ellis Pratt of Cherryleaf and Diana Logan, Documentation Manager at Sage Technologies. In the interview, we discuss Sage Technologies’ new platform for assisting users, the “Sage Ecosystem”, and how user documentation is developed by Diana’s team.


Managing documentation projects – links to useful information

Here are some links to useful information on managing documentation projects:

Support Call Cost Reduction Calculator

Six biggest mistakes Project Managers make with documentation and how to avoid them

Planning user documentation – a guide for software project managers

How many technical writers should we have in our organisation?

In a downturn, is it better to use contractors, permanent staff or an outsourcing company?

Trends in technical and user documentation

Aligning documentation with the business – free guide

Free guide for Project Managers on planning documentation projects

Managing documentation projects

Project Management of documentation projects

Managing content

If you need any advice or assistance in developing user documentation, you should contact Cherryleaf.

Case study:How user documentation is developed at Alfresco in an Agile environment, using wikis

This is the edited Cherryleaf interview with Briana Wherry, Information Manager of Alfresco. We discussed how user documentation is developed at Alfreso in an Agile environment, using wikis.

 

Questions to ask a Documentation Manager

We’re starting to conduct a series of interviews with Documentation Managers; our goal is to provide case studies of best practice and innovative ideas.

We’ll be publishing edited versions of these interviews on Cherryleaf’s YouTube channel.

So:

  • What questions do you think should we ask?
  • What would you like to know from Documentation Managers?

Email us your suggestions!

Also, if you’d like to be interviewed, then do email us.

Documentation Managers peer group meeting

The third Documentation Managers peer group meeting is scheduled for 2pm on Wednesday 13th January 2010, in Maidenhead, Berkshire.

Each meeting, one or two participants seek advice concerning a particular problem, or, possibly, the group discusses a previously agreed topic, under the Chatham House Rule of confidentiality.

This session is free of charge (there has been a notional fee for teas and coffees for the previous meetings).

Feedback on our 1st Documentation Managers/Leaders mentoring meeting.

If you might be interested in participating in future events, then do contact us.

Training programme for managers of documentation teams: an update

Earlier in the year, we asked a number of people in the technical writing community for their thoughts on what should be included in a training programme for managers of documentation teams. We received a lot of great ideas and ended up with a list of over 60 potential topics.

We’ve initiated the development of some training modules, but we’ve been wrestling with the issue of how this content should be best delivered. The questions we’ve been asking are not unique to ourselves, so we thought it might be useful to outline some the challenges we’ve been facing.

Should the way people consume information and learn via the Internet today affect the way we deliver our content?

Should we pay attention to the arguments of Michael Wesch (students of today learn differently from their predecessors) and Sir Ken Robinson (don’t kill creativity)?

 

How will new Web technologies, such as Web 2.0 and the Semantic Web, affect learning in the future?

Our training courses are in a niche market, for people with limited budget, and there are many new ways of delivering information emerging at the moment. So how do we avoid spending time and effort developing training modules that become obsolete in a short space of time?

Where should the topics fit within the curriculum?

We’ve found some topics fall into more than one area. For example, Web Analytics could be part of a Project Management (post project evaluation) and part of a Web technologies track. Wikis could fall under authoring tools, Web technologies and project management tracks.

How important is the ability to discuss ideas?

The greatest intellectual and scientific accomplishments in history have normally come about from where people have been able to:

  1. Question and debate their ideas with others; and
  2. Draw upon ideas from many different subjects.

For example:

  • The 18th Century Scottish Enlightenment (which laid down the mental foundations for the modern world) emerged from clubs and associations dotted around Edinburgh.  What’s more, their discussions ranged ranged from broad intellectual and economic topics to the specifically scientific –  again, topics fell into more than one subject area.
  • The early 20th Century industrialists in America used to meet in Mastermind groups to share and debate ideas and experiences.   

We’re experiencing a similar period of rapid change today.

Our conclusions

These considerations have lead us to the following conclusions:

  1. Learning how to manage documentation doesn’t finish at the end of a course - it’s a lifelong process.  So we’re now approaching this programme from the view of career development.
  2. Topics shouldn’t be pigeonholed into a single narrow track.
  3. There are benefits to people learning through exploration and discussion with their peers.

Is this the correct approach? What do you think?

Lessons for technical communicators from the telecommunications sector

It’s often useful to look at the economic and technological pressures in other industries, to see if the trends emerging there are relevant to the technical communications/publications sector. In recent Blogs, we’ve covered the issues emerging in education, but the telecommunications industry might also provide some useful insights.

Lee Dryburgh, organiser of the Emerging Communications Conference, has been interviewed by Skype Journal.com  about how he see the future of telecommunication. The key points in this interview are:

  • Widespread deployment of a method of communicating, long cultural embedment, extreme ease of use and very low barriers to usage, means it’s not going away in a big way, at any time least soon.
  • We are seeing software offer a new stronger “Relationships” between people. Distribution is relatively zero-cost and it achieves unprecedented scale.

He’s talking about telephony and Skype, but couldn’t that also be true for paper and Web-based online Help?

Dryburgh sees a new phase emerging that will have deeper impact yet.  He said:

“Phase two is built around an economic model that puts human time and attention at a premium. It’s the opposite of what we experience today with telephony, where human time and attention is wasted.”

“Phase two is about intention-based economics. It’s focused on fulfilling intentions and desires … I’m not saying we need to become psychologists and anthropologists. But what we need to build for is access to ever more personal information, i.e. about the human behind the endpoint. Privacy does not exist looking long-term. Ever more personal information is the new currency, which underlies intention-based economics, and people will increasingly trade it for free access to services. “

“If any of this seems abstract at the moment, think about what makes Google money, Ad Words. Google provides search free to the consumer in order to gain eyeballs (mass attention) and takes the search parameter to try and deduce intention. It then sells that attention and intention data upstream to advertisers.”

Could this also happen in the technical documentation arena? Would seeing technical documentation in the context of new economic ideas, such as  intention-based economics  and the economics of attention, affect how and what was created?  Would it change the nature of conversations with management and marketing?