31
Scenarios for iCamp trial 2

Trial2scenarios

Embed Size (px)

DESCRIPTION

Ideas how we can plan activities of iCamp project trial 2

Citation preview

Page 1: Trial2scenarios

Scenarios for iCamp trial 2

Page 2: Trial2scenarios

Timeline

iCamp trial weblog

Project seeds in wiki

Establishing personal environments, forming project groups,assembling group environment

Project-work with self-reflection,commenting 1 peer’s contract

Project-work with self-reflection, commenting 1 peer’s contract

Gro

up

en

viro

nm

en

t is

ass

em

ble

dF

aci

lita

tion

en

viro

nm

en

t is

ass

em

ble

d

Pe

er

refle

ctio

n o

f co

ntr

act

s

Pe

er

eva

lua

tion

of

con

tra

cts

Fa

cilit

ato

r e

valu

atio

n o

f co

ntr

act

s

Pe

er

eva

lua

tion

of

oth

er

pro

ject

s?F

aci

lita

tor

eva

lua

tion

of

pro

ject

s

Fa

cilit

ato

r re

flect

ion

of

gro

up

la

nd

sca

pe

an

d a

ctiv

ity p

att

ern

s

Fa

cilit

ato

r re

flect

ion

of

gro

up

la

nd

sca

pe

an

d a

ctiv

ity p

att

ern

s

Support to form groups, assembling tools, selecting projectsFacilitator assembles itself into group environment

Monitoring and support of group-workand project,overview of group landscape and activities

Monitoring and support of group-work and project

Diary

Fill

ing

in t

he

dia

ryF

illin

g in

th

e d

iary

Fill

ing

in t

he

dia

ry

Fill

ing

in t

he

dia

ry

Fill

ing

in t

he

dia

ry

Fill

ing

in t

he

dia

ry

STUDENTS

FACILITATORS

Page 3: Trial2scenarios

TRIAL ORGANISERS LANDSCAPE

ICAMP TRIAL WEBLOGPROJECT WIKI

PROJECT SEEDS

FEED-ON-FEED

TOOLS AND HELPDESK

STUDENTS WEBLOGS

FACILITATORS WEBLOGS

SPECIFIC GROUP TAGGED FEEDS IN

ILOGUES

LINKS

LINKS

LINKS

LINKS

FEED

CALENDAR

FEED OR LINK

LINKS

LINKS

Page 4: Trial2scenarios

iCamp general trial monitoring• Facilitators could prepare iCamp trial weblog and project-wiki for trial 2. iCamp

weblog will contain links to tools, helpdesk, students’ contracts and facilitators’ personal weblogs, and to the project and trial information. Pages could be used for each project proposal idea introduction or alternatively separate wiki pages can be established for each project. The links from these wikipages are accessible at iCamp trial weblog. The function of pages is to collect the interested people’s weblog contacts and connect people project-based. Other static project information can be on wiki or weblog pages too.

• iCamp weblog blogroll is used to distribute general news. Blogroll feed can be subscribed with the students’ weblogs. Specific tags can be used to tag posts in the blogroll (eg. icampcontract, icampnews, iccampprojects, icampassignment etc.).

• If students’ and facilitator’s weblogs feeds are subscribed with tags, (group1, group 2) we will create for the distributed project area where all the mashed group regulation can be observed in separate threads.

Page 5: Trial2scenarios

General iCamp trial monitoring

Pages links for project seeds and important info

Blogroll for news,Can be subscribed as feed,Tagging news

Toolbox links, helpdesk

Specific tags

Participants contracts

Facilitator’s weblogs

Feed-on-feed link

iCamp trial weblog in wordpress

From wiki pages Students enter to get initial info

Subscription to group-tagged students’ and facilitator’s feeds for monitoring

calendar

Page 6: Trial2scenarios

Individual landscapes

iLogue for contracts

Videoblog

FlickrWordpress weblog

feeds

feeds

Feed to records page Feed-on-feeds

Scuttle

Publishing personal area: PROJECT X TAG

Self-introReflecting project tasks

Self-intro

Reflecting individual project tasks

Group x tag

Group x tag

Oth

er w

eblo

gs

Page 7: Trial2scenarios

Learners: Forming teams• Learners go back to the facilitation page and browse project

ideas at wiki seeds. They add their weblog coordinates under to the projects at wiki pages - by this we collect people who select certain projects. After this pre-selection, learners read each other’s weblogs and find teammates they like. They can organise synchronous meetings to talk with X-lite.

• Alternatively, learners should write, which project interests them in their own weblogs.

• Alternatively learners can advertise their weblogs with icamptrial2 tag-feed in feed-on-feeds, find each other’s contacts and read about each other’s interests and select team-members.

Page 8: Trial2scenarios

PERSONAL LANDSCAPE

PERSONAL WEBLOG

ILOGUE FLICKRVIDEOWIKI SCUTTLE

XLITE

EMAIL

ICAMP WEBLOG

PROJECT WIKI PROJECT PAGE FEED

FEED-ON-FEEDS

FACILITATOR WEBLOG

STUDENT 2 WEBLOG

tagged feeds

LinksFeed

Feeds

Links

tagged feed?

tagged feed?

Page 9: Trial2scenarios

Facilitator and learners: Assembling the learning environment

• If the learners have chosen the project and found team-members, the question arises where is their shared environment. The options are many:

• A) To use shared Wordpress weblog as in trial 1 is less favourable because it decreases learners’ interest to continue keeping their individual weblogs

• B) To use distributed weblogs mashing feeds with Feed plugin is very good because people can monitor the activities of team-members taken in their individual weblogs. Also some other feeds from the facilitator’s and iCamp trial’s weblog can be added.

Page 10: Trial2scenarios

GROUP LANDSCAPE

STUDENT 1 WEBLOG

STUDENT 2 WEBLOG

STUDENT 3 WEBLOG

STUDENT 4 WEBLOG

FACILITATOR WEBLOG

ICAMP TRIAL WEBLOG

MASHED REGULATION WITH FEEDS

PROJECT PAGE FEED

FEED-ON-FEED

SPECIFIC PROJECT TAG FEED OUT FROM EACH STUDENT PAGE, FACILITATOR AND PROJECT PAGE

FEED IN TO WEBLOGS FROM PROJECT PAGE TO EACH STUDENT PAGE?

Page 11: Trial2scenarios

Distributed weblog as regulation tool

Activate feedBack plugin

Page 12: Trial2scenarios

Distributed weblog as a shared regulation tool

Offer subscriptions to team membersor

request subscriptions to form team

Page 13: Trial2scenarios

Distributed weblog as a shared regulation tool

If all the request/offers have been accepted the distributed group weblog is formed.

From read function the posts from team-members and facilitator’s weblogs will be mashed into one feed for monitoring group’s interaction.

Page 14: Trial2scenarios

Distributed weblog as a shared regulation tool

Reply posts are written in your own weblog

View whole post in peer’s weblog

People will know what their teammates want to do, what they did, and how they explain their ideas from posting in their own weblog and monitoring the mashed feed.

Page 15: Trial2scenarios

Distributed weblog as a shared regulation tool

Facilitator’s have the possiblity to mash separately 2 groups’ data if both group uses different tag (groupX, groupY)

Page 16: Trial2scenarios

Facilitator and learners: Assembling the learning environment

• C) If groups use different group tags and submit their feeds (from weblogs, scuttle, videowiki etc.) to the feed-on-feeds aggregator, the facilitator will have different tags for different project weblog feeds to monitor.

• This channel is broader compared with weblog feed mashup because also other tools’ feeds can be mashed like this. However, the minus of using only feed-on-feed for facilitators is that then they cannot interact with students in their regulation distributed space.

Page 17: Trial2scenarios

Aggregation with feed-on-feeds• Alternatively monitoring can be performed:• Each team-member uses in weblog posts always group tag

( eg. groupX).• Every person subscribes their feed in joint iCamp feed-on-feed.• Other tagged project materials (from Scuttle, videowiki,

projectwiki, iLogue pages) can be subscribed too.• If tag transfer is functioning (currently not) people can extract

each group’s posts and other contributions by clicking on specific tag-feed (eg groupX).

• Tags can be added to any feed to select certain feeds that will be related with certain project.

Page 18: Trial2scenarios

Add feeds from each students’ weblog, and other tools which have feeds. Each comment in feeds SHOULD come with the tag that was added in weblog. Right now out of order. But tags enable to sort information group-based.

Sort by tagYou can ad tag manually or it is imported (last is out of order now)

Feed-on-feed aggregator

Subscribed feeds must be updated to see comments

Page 19: Trial2scenarios

Facilitator and learners: Assembling the learning environment

• D) Learners might use the XOwiki (or google.docs or zoho) kind of applications for actual collaborative writing. Published documents from google-docs and zoho can be made available via personal weblogs.

• The feed from XOWiki can be subscribed to the aggregator. • (E) Learners can use for projectwork other central community

environments like Ning, which enable to integrate profiles with external feeds of materials and weblogs.)

Page 20: Trial2scenarios

Learners (and facilitator): Projectwork: individual contracting• After integrating the initial project team environment, facilitators send

an assignment to groups in weblog post to discuss in project teams their general aims of the project and how they are going to distribute work to achieve the aims.

• Next, on the bases of grounded ideas and tasks, each individual in team will generate the iLogue account, fill in the first draft of their individual contract and integrate the iLogue with their weblog.

• Learner’s task is to reflect their doings in personal weblog and keep the iLogue contract.

• Facilitator’s and other team-members view each project-member’s contract before it is approved and the project-work starts.

Page 21: Trial2scenarios

iLogue registration

Students registrate their iLogue account for individual self-reflection during the project.

Page 22: Trial2scenarios

{{recordlog -feed <your_feed_uri>}}

{{recordlog -feed http://blog.course.isikun.edu.tr/katse/feed/}}

Add here

Get your weblog feed into iLogue

Select Configure my weblog

Feed from your weblog will appear in Your records page

Page 23: Trial2scenarios

Records in iLogue

Records feed from weblog

Alternatively posts to the records can be added in Ilogue

Idea is that in iLogue both the activity and the contract can be monitored

Page 24: Trial2scenarios

Personal contract in iLogueAfter the group has discussed who does what in the project team, the student fills in personal contract.

In the middle of the project another student and the facilitator will comment students’ success in the contract.

In the end of the project contract is used as part of evaluation?Fill in contract areas in iLogue page

Page 25: Trial2scenarios

My birdeye in iLogue

My birdeye enables to follow records from my records’ page in timeline. This function is additional compared with if only weblog was used for recording the students’ progress. Timeline view enables to see how often and what student did.

It is normal that student makes corrections in the contract objectives and other parts during the progress of the project.

Page 26: Trial2scenarios

Learners (and facilitator): Projectwork: peer (and facilitator)

monitoring of contracts• Facilitators submit in the facilitation weblog

assignment to select inside each project-team pair of peers who will observe each other’s contracts in the middle and in the end of the activity.

• Team-members keep working individually in their weblogs for reflecting their ideas, and they observe each other’s weblogs and comment if needed in the mashed area of the feed reader in weblog.

• Facilitator will observe the contracts in the end of the project and can use them for evaluating person’s success.

Page 27: Trial2scenarios

Learners: Projectwork: actual projectwork

• Depending of the nature of actual projectwork the teams can use:• A most suggested) distributed weblog mashing feeds together with

Read plugin (good choice for regulative and social tasks).• D most suggested) shared wiki (good choice for generating

project content) • C) shared specific tag to collect information links with bookmarking

tool scuttle• D) shared aggregator feed-on-feeds to monitor all the participants’

individual progress with project which is reflected in their weblogs and contracts

• E not suggested) shared weblog (it may attract learners away from individual weblogs)

Page 28: Trial2scenarios

We need project seeds from the facilitators.Later, from each project seed the new project with (several) pages can grow out.

In this area all the projects can be viewed, however each project uses its own pages

Xo wiki for project content

Page 29: Trial2scenarios

Learners: Projectwork: actual projectwork

• Synchronous communication will be conducted with X-lite

• However we should not totally restrict the learners (like we didn’t restrict them in trial 1) to use other tools if they fail with X-lite

• Learners can use additional tools for shared activities if the project topic prescribes it.

Page 30: Trial2scenarios

Facilitator (and learners): Project level team monitoring and support

• A) Facilitator will add comments for the general audience or projects with specific tags to the Facilitation weblog. In addition, facilitator can comment in own weblog. If facilitator’s weblog feed is subscribed in students’ weblogs, they will see the posts in mashed feed in weblog reader. Facilitator can monitor project-work in weblog mashed feed of the group.

• B) If facilitator is using the aggregator like feed-in-feed, project level monitoring can happen using separate tags for feeds coming from weblogs, wikipages, scuttle etc. (currently out of order!).

Page 31: Trial2scenarios

Facilitator (and learners): Evaluation of projects

• The project materials may consist of the published collaboratively written pages in wiki.

• Learners must make the project materials accessible for the audience in the weblogs and in feed-in-feed aggregator

• When projects are completed, facilitators (and other students) will evaluate the whole project, commenting it in facilitation weblog by using specific projecttag.