10 Things That Suck When Writing Documentation in Agile Development: Part 2

Where Were We?

#6: Time Wasted on Useless Meetings

Technical Writers just sit at dev team meetings for 90% of the time.

#7: Being Taken for Granted

#8: Core Part of the Team… But Not Really

Three ways to groom issues and plan sprints. But no good one.

#9: Less Contact with Other Technical Writers

#10: You Limit Yourself to a By-Product

  • “Don’t save a buggy product with notes in the docs.”
  • “Don’t spend that much time on internal documentation.”

Break That Vicious Cycle

--

--

--

Customer Education team leader, occasional blogger, a movie person, comfortable traveler. Find all my articles at nosek.net.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Implementing an Event-Based Collaboration using HTTP

How To Upgrade The Kubernetes Version Of Your AKS Default Node Pool With Terraform

Meta Interview Question — LeetCode 1414 — Y Tech

Haskell Journey: Functions and Pattern Matching

Migrating from Cloud Endpoints to DB-less Kong

Using KNIME Recursive Loops with a GraphQL API

2020: Year in Review

Tokoin — Forgive Me Body & Soul Program

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Tomas Nosek

Tomas Nosek

Customer Education team leader, occasional blogger, a movie person, comfortable traveler. Find all my articles at nosek.net.

More from Medium

Which Systems Still Work And Which - Still Need Work.

Engineers “not-so-Lowkey” Need Effective Communication Too!

Genocide through Starvation — First Soviet Famine in Ukraine

What is Remote Monitoring & Management (RMM)?