View source for Clear Up Questions/alx

<!-- Design pattern template
 Fill in all succeeding fields that are either surrounded by a comment tag (<!--  - ->) or angle brackets (< >) when applicable -->

{{Infobox_designpattern
|image= <!-- Provide the filename of the image to be displayed (e.g., Design_pattern.png) -->
|contributor= [[Christian Köppe]]
|source=  Köppe (2012)<ref name="Koppe2012">Köppe, C. (2012). [http://dl.acm.org/citation.cfm?id=2831272 Learning patterns for group assignments: part 1.] In ''Proceedings of the 19th Conference on Pattern Languages of Programs (PLoP 2012)''. The Hillside Group.</ref><ref name="deCortie">Also mentioned in de Cortie, T., van Broeckhuijsen, R., Bosma, G., & Köppe, C. (2013). [http://dl.acm.org/citation.cfm?id=2725701 Learning patterns for group assignments: part 2.] In ''Proceedings of the 20th Conference on Pattern Languages of Programs (PLoP 2013).'' The Hillside Group.</ref>
|dataanalysis= <!-- If applicable, list of data analyses used for mining the pattern separated by a " , "comma -->
|domain= <!-- Learning domain the design pattern belongs to (e.g., General, Math, Algebra) -->
|stakeholders= <!-- List of stakeholders separated by a " , "comma -->
|evaluation = <!-- List of evaluations on the pattern separated by a " , "comma -->
|application = <!-- List of environments where the pattern was applied separated by a " , "comma -->
|appliedevaluation = <!-- List of environments where the pattern was applied and evaluated separated by a " , "comma -->
}}



A group assignment has been given to you and some fellow students, including a description of what has to be done and what is expected from you.


<center><nowiki>***</nowiki></center>

'''Some — or all — parts of the assignment description are vague and not understandable. Starting the assignment under these circumstances can lead to a wrong start of the work and also lead to time loss if things are done the wrong way.'''


''Teacher Specifics.'' Each teacher has her or his own way of describing and giving assignments. What seems to be clear for the teacher, does not necessarily have to for the student too.


''Student Interpretation.'' Sometimes students have different interpretations for the same description. They don’t agree on what the teacher is asking for. It is also the case you can start working on an assignment, and only when you get into it do things become unclear or open to multiple interpretations.


''Incomplete Instructions.'' It is possible that the teacher forgot a part in the assignment description which is important for the students to know.


''Inconsistent Instructions.'' Even though the instructions are complete, it might be that parts of the instructions are inconsistent or conflicting.


''Wrong Work Done.'' Doing work that is not requested by the teacher and therefore also (often) not taken into account for grading is a waste of time. Furthermore, this time is not available anymore for working on the required parts of the assignment.

<center><nowiki>***</nowiki></center>

'''Therefore: After the assignment is given, summarize what is clear about the assignment and try to identify what is not. Check this with all team members. If parts stay — or become — unclear, ask the teacher for clarification.'''


It is always better to ask than to just assume whenever there is uncertainty. Without knowing what is asked from you in an assignment, there is a high chance that what you finally deliver is not sufficient. In some cases you also can get this information from your peer students, in other cases you need to ask the teacher for clarification. Either way, it is recommended to {{Patternlink|Nominate One Communicator}} who’s responsible for asking the teacher or other peer teams.

In some cases it is not possible to clarify all assignment aspects at one time. In that case start with clarifying these aspects first which you need for being able to start with the assignment and postpone the clarification of the other aspects to a later moment.

After all — or enough — assignment parts are clear to you, you should be able to {{Patternlink|Deliver High Quality Products}}. Perhaps you have to {{Patternlink|Fill Knowledge Gaps}} of some group members.



''In an assignment that comprised both the requirements elicitation and the development of an online banking system, two groups had to collaborate. One group played hereby the role of the customer, while the other group had to analyze the requirements and to build the system (and vice versa). It was not clear to the groups if they should test the system of the other group in their role as users or if they should test the system developed by them, as the instructional material only stated that the developed system should be tested and that a test-report is expected as part of the deliverables. After asking the teacher what exactly was expected from them, they discovered that each group had to do two tests: a system test of their own system and an acceptance test of the system of the other group, which also had to be documented in a test-report. After this clarification all students knew what to do and they were able to finish this part of the assignment as expected.''




==References==
<references/>

[[Category:Design_patterns]] [[Category:Full_Pattern]] [[Category:Learning Patterns for Group Assignments]] [[Category:Traditional Classroom]]<!-- List of other categories the design pattern belongs to. The syntax for linking to a category is: [[Category:<Name of category]] -->