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.
Re: Useful training/certifications - not ST or just tech writing
Subject:Re: Useful training/certifications - not ST or just tech writing From:Robert Lauriston <robert -at- lauriston -dot- com> To:TECHWR-L Writing <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 18 Oct 2017 17:10:30 -0700
Having worked in with teams following Scrum by the book, I think
knowing how agile development teams are supposed to work is unlikely
to give a tech writer any insight into the real-world challenge of of
coupling deadlines for customer-facing docs with development sprints.
In a company that's not really agile, the people who could benefit
from training are the product owners and whoever will perform the role
of Scrum master. (Scrum is a proper noun, agile is just an adjective.)
On Wed, Oct 18, 2017 at 3:41 PM, Shari Punyon <sharipunyon -at- gmail -dot- com> wrote:
> I disagree with this statement. Very few workplaces implement Agile
> methodology effectively, and having training on the way Agile development is
> SUPPOSED to happen puts you way ahead of the curve right now.
>
> I also don't have a problem just calling Agile in casual conversation,
> although I'd never put it on a resume that way!
>
> Most amusing Agile quote to date: Yeah, we do Agile. Agile like an elephant
> in a tutu.
>
> On Wed, Oct 18, 2017 at 4:22 PM, Robert Lauriston <robert -at- lauriston -dot- com>
> wrote:
>>
>> Being certified for some flavor of agile (not a proper noun)
>> methodology seems like a waste of time if the developers are not
>> actually practicing it. Putting that on your resume could conceivably
>> get you in trouble if you don't have the real-world experience to
>> answer a hiring manager's questions about working with agile teams.
>>
>> What might stand out to me if looking through resumes of applications
>> for an open position would be programming classes that would be useful
>> on the job, such as SQL or CSS.
>>
>> On Wed, Oct 18, 2017 at 1:12 PM, Wroblewski, Victoria
>> <victoria -dot- wroblewski -at- necect -dot- com> wrote:
>> > Hello all -
>> >
>> > Boss stumbled across an Agile training course that looked of interest to
>> > our group (our division of the company is supposed to be following Agile
>> > methodology but it's still largely waterfall in the guise of Agile) and
>> > signed us up for it. Result of it will be an actual Agile
>> > certification-thingy (technical term) that will be a boost for our team that
>> > we are a little more than just writer monkeys, and one more thing to list on
>> > the resume. And it will hopefully get us better ideas on how to be more
>> > involved in the Agile process with documentation.
>> >
>> > Anyone out there done any other training/certification that is NOT
>> > specifically tool related or an attempt to prove we know technical writing
>> > when we've all been doing this for 20 years?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com