Success
... 3. Help with potential conflicts that arise Let us get a code together. When we refresh, I tend to write information in another post that may have a different question. Help/1 may mean a assignment problem. Help/2 may mean a new barrier has come up. You see what I am aiming at, if we can agree, or if there is another solution. 4. Document commitment We should all post our commitment to a project. I sent an earlier post about an outline that is due. I read it in the syllabus, but I haven't seen any conversation about this. I could be all wrong in my thinking, but I need that syllabus to keep up. 5. Chart the path of the team Every time we accomplish an assignment or work on a project together that is completed by that team member, we need to document this. We could put in the subject area: allocated about 45% to the Prewriting and Planning. 25% to the > Writing. 10% to Revising and Formatting. 15% to the Proofreading. 5% > to...