Difference between revisions of "Manage the Project"
Jump to navigation
Jump to search
***
Sfrancisco (talk | contribs) (Created patlet for pattern) |
Sfrancisco (talk | contribs) m (Edited format) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
{{Infobox_designpattern | {{Infobox_designpattern | ||
|image= <!-- Provide the filename of the image to be displayed (e.g., Design_pattern.png) --> | |image= <!-- Provide the filename of the image to be displayed (e.g., Design_pattern.png) --> | ||
|contributor= | |contributor= [[Christian Köppe]], [[Thomas de Cortie]], [[Ronald van Broeckhuijsen]], [[Gerard Bosma]] | ||
|source= Köppe (2012)<ref name="Koppe2012">Patlet first mentioned in 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>de Cortie, van Broeckhuijsen, Bosma & Köppe (2013)<ref>Pattern published 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> | |source= Köppe (2012)<ref name="Koppe2012">Patlet first mentioned in 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>; de Cortie, van Broeckhuijsen, Bosma & Köppe (2013)<ref>Pattern published 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 --> | |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) --> | |domain= <!-- Learning domain the design pattern belongs to (e.g., General, Math, Algebra) --> | ||
| Line 20: | Line 20: | ||
Therefore: Manage your project by keeping track of who is assigned to what tasks and work products, and what the status of these is. Come in action if things are not progressing as planned. | Therefore: Manage your project by keeping track of who is assigned to what tasks and work products, and what the status of these is. Come in action if things are not progressing as planned. | ||
==Context== | |||
<!-- Context of the design pattern --> | |||
==Problem== | |||
<!-- Problem the design pattern solves --> | |||
==Forces== | |||
<!-- List of forces affecting the solution. Each entry is preceded by an * For example: | |||
# Entry 1 | |||
# Entry 2 --> | |||
==Solution== | |||
<!-- Solution to the design problem --> | |||
==Consequences== | |||
===Benefits=== | |||
<!-- List of benefits from applying the solution to the problem Each entry is preceded by an * For example: | |||
# Entry 1 | |||
# Entry 2 --> | |||
===Liabilities=== | |||
<!-- List of liabilities from applying the solution to the problem Each entry is preceded by an * For example: | |||
# Entry 1 | |||
# Entry 2 --> | |||
==Evidence== | |||
===Literature=== | |||
<!-- Evidence from literature that was used in producing the pattern or evaluating the pattern--> | |||
===Discussion=== | |||
<!-- Discussion with experts or stakeholders used in producing the pattern --> | |||
===Data=== | |||
<!-- Evidence from data that was used in producing the pattern --> | |||
===Applied evaluation=== | |||
<!-- Results from randomized controlled trials (RCTs) or similar tests that measures the pattern's effectiveness in an actual application. For example, compare student learning gains in an online learning system with and without applying the pattern. --> | |||
==Related patterns== | |||
<!-- Other design patterns related to the current design pattern and a description of how it is related --> | |||
==Example== | |||
<!-- Example of applying the design pattern --> | |||
==References== | ==References== | ||
<references/> | <references/> | ||
[[Category:Design_patterns]] <!-- List of other categories the design pattern belongs to. The syntax for linking to a category is: [[Category:<Name of category]] --> | [[Category:Design_patterns]] [[Category:Patlet]] [[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]] --> | ||
Latest revision as of 21:29, 5 June 2017
| Manage the Project | |
| Contributors | Christian Köppe, Thomas de Cortie, Ronald van Broeckhuijsen, Gerard Bosma |
|---|---|
| Last modification | June 5, 2017 |
| Source | Köppe (2012)[1]; de Cortie, van Broeckhuijsen, Bosma & Köppe (2013)[2] |
| Pattern formats | OPR Alexandrian |
| Usability | |
| Learning domain | |
| Stakeholders | |
Without knowing who is working on what tasks and work products and what the status is of these it is hard to judge if everything is progressing as planned and the project can be finished successfully.
Therefore: Manage your project by keeping track of who is assigned to what tasks and work products, and what the status of these is. Come in action if things are not progressing as planned.
Context
Problem
Forces
Solution
Consequences
Benefits
Liabilities
Evidence
Literature
Discussion
Data
Applied evaluation
Related patterns
Example
References
- ↑ Patlet first mentioned in Köppe, C. (2012). Learning patterns for group assignments: part 1. In Proceedings of the 19th Conference on Pattern Languages of Programs (PLoP 2012). The Hillside Group.
- ↑ Pattern published in de Cortie, T., van Broeckhuijsen, R., Bosma, G., & Köppe, C. (2013). Learning patterns for group assignments: part 2. In Proceedings of the 20th Conference on Pattern Languages of Programs (PLoP 2013). The Hillside Group.