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.
Before I read further in my list backlog, I'll bet that the "Agile" in
question is actually Oracle Agile, a system for configuration control and
related activity, and part of the overall Oracle enterprise systems.
It gets confusing around here, because we have gone over to Agile
methodology for our product development/test/release process, but we have
ALSO adopted the Oracle Agile system... and the two are not related.
As I mentioned in another post, we use Jira for our agile dev process, Git
for our repository, Fisheye, and some other tools. I don't get to touch
the Oracle Agile system, and I'm glad of it. Totally different animal.
On Wed, Oct 9, 2013 at 3:23 PM, Robert Lauriston <robert -at- lauriston -dot- com>wrote:
> It's not a proper noun.
>
> Doing agile development means using an agile methodology. I don't
> understand what "we're just using it for configuration control" would
> mean. Maybe the person who said that doesn't either?
>
>
>
> On Wed, Oct 9, 2013 at 12:14 PM, Lippincott, Richard
> <RLippincott -at- as-e -dot- com> wrote:
> > I know this is an elementary question, but up until recently I've been
> glossing over Agile topics as they haven't applied to my work situation.
> Apparently we're moving to an Agile work environment, and we're doing it
> soon.
> >
> > (We switched to Agile as a configuration control system about six months
> ago, at that time the standard response to my repeated question "Are we
> using the methodology?" was "No, we're just using it for configuration
> control, that's all. I learned that we're adopting the process about a half
> hour ago when I went to a meeting on a program, and noticed up on a wall
> were all sorts of yellow sticky notes arranged as "Sprint 1," "Sprint 2,"
> and so forth. "Oh yeah, we're adopting the process" said the program
> manager in the meeting.)
> >
> > I'm a lone writer, currently working at about 110% of capacity, managing
> the operator and field service manuals on about a dozen different complex
> products, and it's not unusual that I've got three or four different
> projects/product manuals in work at any given moment.
> >
> > Is my life about to get easier because of this, or is it likely I'm
> about to get overwhelmed by the pace of changes?
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> New! Doc-to-Help 2013 features the industry's first HTML5 editor for
> authoring.
>
> Learn more: http://bit.ly/ZeOZeQ
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as editorialstandards -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
--
__o
_`\<,_
(*)/ (*)
Don't go away. We'll be right back.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
