Thursday 1st October, 2015
2:30pm to 3:10pm
Many companies embrace agile methodologies, and the technical documentation department usually follows, with some reluctance, using agile methods to change their workflow and appointing scrum masters to try and meet the deadlines that come up in rapid succession. Automated builds and Github repositories for technical documents are no exception anymore.
But why would you republish everything when only one or two topics have changed? Why copy the behaviour of the software department when the documentation workflow has slightly different requirements and dependencies?
This presentation shows how rethinking the publication workflow may lead to a situation where documentation is much faster than the average agile development department. Instead of automating the publication workflow, this approach allows immediate changes without losing the level of control that you might need over the content that is available to the users.
3:30pm Keynote Speakers Closing Panel: What's the Next Boundary to Break? by Chris Atherton, Murray Cox and Andrea L. Ames
Sign in to add slides, notes or videos to this session