| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Dokkio Sidebar (from the makers of PBworks) is a Chrome extension that eliminates the need for endless browser tabs. You can search all your online stuff without any extra effort. And Sidebar was #1 on Product Hunt! Check out what people are saying by clicking here.

View
 

Team Roles Summary

Page history last edited by Ms. Edwards 13 years, 1 month ago

Team Roles

 

Team Roles Summary

 

As you work in teams, each person participates for group success.  How can you all succeed?  Remember, each project's evaluation considers each team member's contribution to the wiki project.  These roles will help us be leaders and help us all succeed -- and that is the most important goal of all: Class Success!

 

Discussion Director/Task Tracker, Link Leader, Flow Foreman, Spelling Superintendent, Style Supervisor




 


 

Team Roles in Brief

 

The Discussion Director/Task Tracker

Good group projects start and end with conversations.  What do you do?

  1. Keep a discussion moving. 
  2. Ask constant questions about what your group is producing (valid, reliable, accurate, interesting), how the project is progressing, what needs to be done or re-done, etc.
  3. Be a good planner: help your group set due dates, reflect and review the progress of your project, and complete required tasks.
  4. Questions:
    1. What are we supposed to do?
    2. Are we on task?
    3. Is this helping us?
    4. What do we do next?
    5. Are we accurate?
    6. Will people understand this?
    7. What are others doing? (send runner)
    8. Have we included everything?
    9. What did we learn?

 

The Link Leader/Project Protector

A high quality wiki provides "a heaping cheese-load worth of links to outside sources." The link leader of your group is responsible for all of the links included in your document.  What do you do? 

Link, Check, Protect, Cite

  1. Link: Find links.
    1. Use the checklist found here  evalmidd.pdf  to evaluate
    2. Find where to put them on your page.
  2. Check and Protect: Look for plagiarism as a protection of the integrity of the wiki. You are "The Protector." Notify your teacher of any spamming or inappropriate editing/commenting.
  3. Cite: and link to the source for your ideas and graphics. Use footnotes.[1] [2]

 

The Flow Foreman

Review your work for clarity and content.  Make revisions so your reader is not frustrated. What do you do?

  1. Look for new ideas that relate to the topic and include those ideas into the wiki. (innovator)
  2. Look for sentences that don't make sense.
  3. Look for places that make readers go, "Huh?"
  4. Look for missing words and phrases.
  5. Look for missing explanations and details.
  6. Look for rambling on and on and on.
  7. Look for unnecessary repetition.
  8. Read---and reread---and reread again and again and again---after all, wikis change every day. 
  9. Revise the "readability" of your group's document.

 

The Spelling Superintendent

"Nothing ruins a good piece more than 8,000 spelling errors." My, we kant reed cuz u kan't spel enyting korektlee! What do you do?

  1. The spelling superintendent checks the spelling of every single word that is added to your group's document.
  2. When a change is made, the spelling superintendent checks the spelling of every single word that is added to your group's document.
  3. Repeat 1 and 2 until the final publication, and check again!

 

The Style Supervisor (or Eye Candy Chairperson)

Think about all those pages you left within two clicks. The style supervisor seriously ensures that doesn't happen to you!  What do you do?

  1. Find images and graphics that support your ideas.
  2. Cite sources for you images and graphics.
  3. KISS: Keep it simple, succinct.
  4. Remember who the audience is----and choose appropriate graphics, images and layout for that specific group of people!


 

Think Ahead: Team Tactics

Remember these tips:

  1. Regardless of the role that you are assigned, your wiki page is a group project.
  2. If you can help a partner complete their task too, you're really just helping yourself! 
  3. If you can help another team complete their task too, you're really just helping the whole class.
  4. When you come across resources or ideas that might improve your final product, be sure to use the discussion board of your group's page to share ideas.
  5. If you find excellent resources, add your idea in the form of a question/answer to the Problems Page (Wiki Problem Page for wiki solutions or Project Problem Page for project ideas/solutions).

 



| FrontPage | Read Me | SandBox |Team Roles |

 

Adapted from the work of Bill Ferriter, who teaches 6th grade language arts in North Carolina and was named Teacher of the Year for 2005-2006.

Footnotes

  1. Teaching Hacks; Assigning Roles; http://www.teachinghacks.com/wiki/index.php?title=Wikis CC
  2. Adapted from the work of Bill Ferriter, who teaches 6th grade language arts in North Caroline and was named Teacher of the Year for 2005-2006.

Comments (0)

You don't have permission to comment on this page.