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: SD Times: Tech Writers Should Be Pigs, Not Chickens
Subject:RE: SD Times: Tech Writers Should Be Pigs, Not Chickens From:"Jack DeLand" <jackdeland -at- comcast -dot- net> To:"'David Farbey'" <dfarbey -at- yahoo -dot- co -dot- uk>, "'Robert Lauriston'" <robert -at- lauriston -dot- com> Date:Mon, 16 Sep 2013 06:15:11 -0400
I agree and disagree with David and Chris. Yes, I think that Agile is best
adopted wholesale, as an organizational change. (For a terrific book on
organizational development, see Preferred Futuring by Dr. Larry Lippitt, but
note that, as a former intern, I am biased. It's still terrific.)
But I have been on a dev team that successfully implemented Agile methods
within an non-Agile org. In this case, it revolved around the scrum master,
who was able to maintain a balance of expectations with management, and the
project manager, who cleared the way. In my current situation, we have an
org that is wholly Agile, and life is definitely easier. Again (IMO) it
revolves around a very committed and very talented scrum master, but the
management support goes all the way up the ladder to the man with the
Carrera S. There is no way of subtracting or negating the human element,
unless you want to go to robotics.
I have never been in a waterfall environment where dates did not slip.
Agile, to me, is a terrific improvement over traditional methods, if only
because it gives voice and a real degree of control to the people who are
actually creating the product as a way of working daily, not as a happy
exception. This is key to the "preferred futuring" approach.
I would recommend scrumalliance.org to anyone interested in investigating
Agile further. Again, as a graduate, I am biased. But I am also definitely
committed. Oink.