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.
Hi Moshe,
I've worked on ERP doc for several years, and here's my 2 cents:
1. ERP is a very broad term. First find out which modules they are including in their system.
2. What is the project duration and how many developers will work on it? Dev timelines will give you rough indication of doc estimates.
3. In addition to documenting of screens, you will most likely need to have descriptive sections that describe the workflow in the ERP for sales cycle, purchase cycle, inventory etc.
4. Reports are a big part of ERP, though the task may be as simple as click button x to generate report y.
Regards,
Reshma
Sent from my iPhone, please ignore typos.
> On 30-Oct-2014, at 5:07 pm, Moshe Kruger <moshe -dot- kruger -at- gmail -dot- com> wrote:
>
> Hello all,
>
> I hope members of this list can assist me.
>
> My challenge is to come up with a time estimation (in writer hours) for a
> certain writing project. Not being an expert in ERP, I would like to
> request the help of more experienced members in this forum.
>
> These are the (rough) parameters:
>
> 1. System: A full ERP implementation, meaning one that employs all the
> components you'd expect in a "best of breed" ERP solution.
>
> 2. The system is still under development. Writers will need to work a lot
> from specs/PPTs/demos and the like.
>
> 3. Deliverable scope: Not full-blown but also not minimal.
>
> 4. Deliverable format: online Help (HTML-based).
>
> 5. Authoring tools: Word, probably. Not single-source.
>
> Thanks in advance for your input.
>
> ----------------------
> Moshe Kruger
> Mobile: +972-52-770-7387
> ---------------------------------------
> LinkedIn Profile: www.linkedin.com/in/allwrite
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as reshma_pendse -at- yahoo -dot- co -dot- in -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
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l
