Scrum teams develop in blocks of time called sprints. Sprint times can vary but the average is 30 calendar days. The goal of each sprint is to have developed something that could be put into production as is.
The technical writer must have documentation for each sprint. This is great because they can be small pieces of a larger application. You are working in the group with the developers, probably regression testing, and living and breathing the application for the 30 days.
The bad news is when you are supporting more than one Scrum team. Since I am a member of one scrum team, they get my full support and I have to tear myself away in order to help other teams.
One of the critical elements of a scrum team is that everyone does whatever is necessary to reach the goal. I do not code but I can test the UI. No one on the team is up for technical writing.
The quandry is that there are nine teams producing workable app's on a 30 day cycle. This means that the shared resource (me) is forced to decide what minimum amount of documentation is necessary for each team. Has anyone else come to terms with this dilemma?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment