TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Scrum as a Job Requirement From:"William Sherman" <bsherman77 -at- embarqmail -dot- com> To:"Charlotte Branth Claussen" <charlotteclaussen -at- gmail -dot- com> Date:Tue, 5 Mar 2013 13:39:50 -0500
Here is one that came today.
> Prior experience authoring IT documentation within the Agile SDLC
>From what I have read on scrum, it is basically a policy of daily meetings of the team, to be sure no one is lost and that everyone is accomplishing something. I know that is a great simplification of the process, but really, does anyone think they couldn't work in a group that has regular meetings so we can keep progress flowing?
On many projects I have been on, I have been handling multiple projects, so there would be some days I may not work on Project ABC as I was working on XYZ that day due to meetings or access to the system, so I wouldn't have progress on a daily level. But saying I couldn't do a daily meeting is preposterous.
Now other sites list scrum not so much as daily meetings but as sprints, which can be defined as almost any length, such as week sprints, two-week sprints, and so on. The idea is the product is more or less a deliverable at the end of each sprint and is re-evaluated as to being on track in case the direction of the company or product has changed.
That is almost like saying the job requirements are:
1. Must attend meetings with team
2. Must attend meetings with boss
3. Must be able to use a computer
4. Must be able to travel between buildings for meetings
I think we have been naming too many things to promote self-importance when the reality is getting the job done and done right is the only real value. Just because someone hasn't done scrum doesn't mean they couldn't do it. It isn't like you need to go for a 4 year degree in it.
It would be better to say.
1. We have weekly meetings to access where we are.
2. At these meetings, you need a functioning draft.
3. The direction of the product could change at any meeting, and you must be flexible to change.
----- Original Message -----
From: Charlotte Branth Claussen
To: William Sherman
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Sent: Tuesday, March 05, 2013 4:28 AM
Subject: Re: Getting that info
William, I know, and I did not take it like that. I agree completely that an interest in exploring the software yourself is part of making a good techwriter. Also, like Anne says, it gives a lot more respect among the developers that you actually put an effort into learning.
Regarding scrum, I believe there is many ways of doing it, none exactly like it is described in whatever you read. Hopefully, any workplace will implement scrum in the form and degree that suits the workplace and the tasks at hand.
To me it sounds strange that scrum is a job requirement, unless they are looking for a scrummaster or lead developer. But it can be important in the sense that you would only fit in, if you work well in an environment with daily standup meetings, collaboration with a team, and planning in so called sprints. What I particulaly like about scrum is that everything is visible, both to your team and to your manager.
/Charlotte
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
EPUB Webinar: Join STC Vice President Nicky Bleiel as she discusses tips for creating EPUB, the file format used for e-readers, tablets, smartphones, and more.
