You can assign the development tasks as best suits your available resources. Listed below are the major tasks and a suggested division of responsibility for each task. 

Develop standards
Project leaders. Includes content, formatting and styles, and naming conventions.

Create content
Content authors. Includes recording topics, adding Introduction and End frame text, creating and linking attachments, adding Glossary terms, Jump-in points, adding bubble text (including Know It? mode text) as necessary, and creating questions and assessments to test existing competency and learning.

Edit content (initial)
Content authors or Editors. Includes playing topics in all play modes in the Developer to check for correct screens, correct text, correct web pages and apply styles, and so on. May also need to publish and test Jump-in points and See Also links in the Player window. This task could be done by a separate team of editors, or the content authors could check each other's work.

Spelling/grammar check
Content authors. Includes checking spelling and grammar, or creating a printed reference document.

Create glossary terms
Editors, Project leaders, or Content authors. Includes creating glossary terms.

Create roles
Editors or Project leaders. Includes creating and attaching roles to the topics.

Attach keywords
Editors or Project leaders. Includes attaching keywords to the topics.

Testing (QA)
Project leaders. Includes playing the topics in all modes in the Player and testing questions and assessments linked to the outline.

In addition to assigning development tasks, you should create a development flow through the various tasks. A good flow can make the process smooth from first development through final editing. A bad flow can extend the process far longer than necessary. A recommended flow is shown below:

1. Create scripts for the transactions (Development Team)
    
2. Record initial content (Content authors)
    
3. Test the recorded frames (Content authors)
    
4. Make corrections or re-record frames as necessary (Content authors)
    
5. Add text to recorded topics (for example, Introduction/End frames, extra bubble text, Know It? mode text) (Content authors)
    
6. Create and link attachments (Content authors)
    
7. Create, link and set properties for questions and assessments (Content authors)
    
8. Create and update Glossary terms (Editors or Project leaders, Content authors)
    
9. Test the recorded topics (Editors)
    
10. Verify text in Introduction/End frames, bubbles, attachments (Editors)
     
11. Make necessary corrections (Content authors or Editors as appropriate)
     
12. Preview questions and assessments to verify answers, remediation, and content links. (Content authors or Editors as appropriate)
     
13. Create and associate Roles (Editors or Project leaders, Content authors)
     
14. Assign keywords (Editors or Project leaders, Content authors)
     
15. Perform spell check and final glossary update (Content authors)
     
16. Test topics in the Player
     
17. Test pre and post assessments in the Knowledge Center (available in the Professional edition only)

Table of Contents  Back