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:Re: Getting that info From:"William Sherman" <bsherman77 -at- embarqmail -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Mon, 4 Mar 2013 15:37:24 -0500
I understand that completely, and didn't mean to make it sound like anything less than doing it all yourself was less than acceptable. I've been places that you simply didn't have access to the equipment or applications. While I talked about logging time on a simulator, I worked one job we had full visual access to a simulator, and zero access to it running. Now how can you document anything as to how it works when all you can do is look at it sitting? You can't touch it, turn it on, run it, see it run, or anything. Yet you have to document all of that.
You do just like you do, trust the part of the team that does have access to get what you need.
Your mention of scrum team is interesting as lately, I have had a few job calls that used "scrum team" as a job requirement, not as a nice way to get a team to run. As such, I looked up scrum teams to find what I could, and came to the conclusion that while I have never been officially in one or worked where they were used, I have been on several projects that ran that way. It is too bad that the communications within a team has dropped such that they now have to have a process such as scrum to get people to work how they should, and used to, work.
Worse is that job recruiters are using it as a job requirement, since they obviously do not know what it is.
----- Original Message -----
From: Charlotte Branth Claussen
To: Editor in Chief
Cc: William Sherman ; techwr-l -at- lists -dot- techwr-l -dot- com >> TECHWR-L
Sent: Monday, March 04, 2013 2:14 PM
Subject: Re: Getting that info
I depend on the developers for information and for creating screenshots.
Our software is made for programming hardware, and it has a lot of constraints - depending on the condition on hardware and programming devices - that make it next to impossible to create all scenarios. I can do my own exploring, which I of course do, as well as working closely with our requirements team. Still, some scenarios I cannot create on my own. I need help from the few specialists who can tamper with the hardware. Or I need one of the developers to simulate for me, as I don't have the proper tools. The developers know that, and I experience that they are always willing to help me out.
To be honest, I don't think any of them care deeply for documentation. But they do want to help out a colleague. I am part of a scrum team, and I believe it is a great advantage to be "one of the guys".
/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.
