projects 2013 02-01

Venla Vallivaara & Aino-Maaria PalosaariLET – Learning and Educational Technology Research UnitUniversity of Oulu2013-02-01

Educational Projects(PROJECTS)Friday 1st of February

IT’S TIME TO START PLANNING! :)


2013-01-18Friday08:15-14:00KTK215

2013-02-01Friday08:15-14:00KTK215

2013-02-15Friday08:15-14:00KTK215

2013-03-22Friday08:15-14:00KTK215

2013-04-12Friday08:15-14:00HU206

2013-05-03Friday08:15-14:00KTK215KTK207

2013-05-17Friday08:15-11:30KTK305KTK215

Course info Lecture: Planning a project

Lecture: Educational projects

Lectures: Project funding, Project reports

Lecture: Evaluating projects

Project presentations

Summing up the course

Meeting with the client

Meeting with the client

All the clients present

Teamwork BRAINSTORMING AND PLANNING THE PROJECT IN TEAMS

Teamwork

Consulting appointments

PLANNING THE PROJECT IN TEAMS

Teamwork


PLANNING AND IMPLEMENTING THE PROJECT IN TEAMS

Teamwork


IMPLEMENTING AND REPORTING THE PROJECT IN TEAMS

Teamwork IMPLEMENTING AND REPORTING THE PROJECT IN TEAMS

ICTWorkshop: digital stories

FINALIZING THE PROJECT IN TEAMS

Finalizing the teamwork

PECHA KUCHA

POSTER DIGITAL STORY

IDEA PAPER

PROJECT PLAN

MID PROJECT REPORT

FINAL PROJECT REPORT


Today’s schedule:

Friday 2013-02-01

08:15-09:45 KTK215

Pecha Kucha -presentations

10:00-11:30 KTK215

Project Plan Aino-Maaria PalosaariVenla Vallivaara

12:30-14:00KTK215

Teamwork • Six thinking hats for

planning the projects


PECHA KUCHA’s

• About 15 minutes for each presentation + discussion

• Peer assessment with the evaluation form – Does the presentation follow the basic rules of Pecha

Kucha and does the oral presentation support the slides and vice versa?

– Is the presentation clear and well-structured and does it give the basic information about the project?

– Does the presentation include team’s own ideas about the project implementation and is the presentation interesting, entertaining and creative?


PROJECT PLANNING


PROJECT PLANNING

• Why is it important to make a project plan?

• A well-defined and structured plan will guide your work, facilitating operational action, monitoring and finally evaluation of your project


PROJECT PLAN

• A written document with certain structure

• Course assignment evaluated by teachers

• Final version ready before 22nd of March

• Return your first versions (for peer-feedback and discussion) to Aino-Maaria by noon on Thursday 14 February


The structure of the project plan

1.) Name of the project

2.) Background of the project– Context and the background of the project– Assess the need, why is it that this project is being

implemented?– Theoretical framework



3.) Aim and goals of the project

– Name and define the main goal and the sub goals of the project

– Be clear with your goals

4.) Target group– For whom is the project done and what for?



5.) Implementation and the timetable– Define the procedures you will use to reach your

goals– How do you plan to implement the project?– Define your challenges and prepare yourself– Schedule your implementation by outlining the

project piece by piece and define a sub goal and deadline for each piece

6.) Resources of the project– Define the literature and other references, use of

expert consulting if necessary, technology resources– Time– Project group’s own inner resources



7.) Expected results– What are the expected results?

8.) Monitoring and Evaluation

9.) Reporting the project results


Timetable for your project

In this project course the active project work is implemented in February-April (finalizing in May)

What is the timetable for your project? • What are the main things you are going to do

in your project?• What kind of deadlines do you have

– from the client or context of the project?– in this course?

• What you should do in February? What needs to be done in March? How should you proceed in April? What is left for May?


HOW COULD YOU

VISUALLY PRESENT

YOUR TIMETABLE

IN YOUR PROJECT PLAN?

Google for example:” 10 Free Project

Management Tools to Fit

Your Needs” or “10 Free Tools For Effective

Project Management”

YOU MIGHT LIKE TO TRY

SOME PROJECT MANAGEMENT

TOOLS? OR FOR THIS

COURSE BASIC OFFICE TOOLS

ARE OK TOO :)”


Edward de Bono’s

SIX THINKING HATS FOR PLANNING YOUR PROJECT

• The red hat signifies feelings, hunches and intuition – the place where emotions are placed without explanation.

• The blue hat is used to manage the thinking process. It ensures that the ’Six thinking hats’ guidelines are observed.

• The yellow hat symbolizes brightness and optimism. You can explore the positives and probe for value and benefit.

• The green hat focuses on creativity, possibilities, alternatives and new ideas. It is an opportunity to express new concepts and new perceptions – lateral thinking could be used here.

• The black hat signifies caution and critical thinking – do not overuse! Why something may not work.

• The white hat calls for information known or needed. ”The facts, just the facts”.

Instructions by Paul Foreman at www.inspiration.moonfruit.com


THE RED HAT

10 MINUTES OF DISCUSSION AND NOTES

Wearing the red hat allows you to put forward your feelings and intuitions without the need for justification, explanation or apology.

Putting on the red hat, you express what you feel about the project…



THE WHITE HAT


Calls for information known or needed – gathering just the facts.

Wearing your white hat allows you to present information in a neutral and objective way.

Proposals, opinions, beliefs and arguments should be put aside!



THE GREEN HAT


The green hat is specifically concerned with creating new ideas and new ways of looking at things:• Creative thinking• Additional alternatives• Putting forward possibilities and hypotheses• Interesting proposals• New approaches• Provocations and changes



THE BLACK HAT


Wearing the black hat allows you to consider your proposals critically and logically.

The black hat is used to reflect on why a suggestion does not fit the facts, the available experience, or the system in use.

Judgement, caution and evaluation



THE YELLOW HAT


Wearing the yellow hat allows you to look for benefits, feasibility and how something can be done.

Yellow hat thinking is a deliberate search for the positive. Benefits are not always immediately obvious and you might have to search for them.

Every creative idea deserves some yellow hat attention :)



THE BLUE HAT

10 MINUTES OF DISCUSSION AND CONCLUSION

The blue hat is for organizing and controlling the thinking process so that it becomes more productive.

In this case wearing a blue hat you can ask for a summary, conclusion, or decision:

What did we benefit from using these six thinking hats? How should we proceed with these ideas?



For the next time:

• Start writing your project plan as a team by using the instructions given today

• Send the plan (as it is at that moment) to Aino-Maaria (aino-maaria.palosaari(at)oulu.fi) by Thursday 14th of February before 12:00

• If you have any questions, don’t hesitate to contact your instructor

• If you want to have a consulting appointment (about technology or learning theory), send your request to Venla (venla.vallivaara(at)oulu.fi)


If you want something to read…

• Designing Education Projects (2009). A Comprehensive approach to Needs Assessment, Project Planning and Implementation, and Evaluation http://www.oesd.noaa.gov/leadership/DEP_Manual_2ndEdt_Final.pdf

• Designing Evaluation for education projects http://wateroutreach.uwex.edu/use/documents/NOAAEvalmanualFINAL.pdf

Suomenkielistä lukemistoa:

• Anttila, P. (2001). Se on projekti – vai onko? Kulttuurialan tuotanto- ja palveluprojektien hallinta. Hamina: Vammalan Kirjapaino Oy.

• Lind, O. (2001). Näin tehdään onnistunut projekti. Tampere: Ruottukka Oy.

• Ruuska, K. (1999). Projekti hallintaan, Suomen ATK-Kustannus Oy, Jyväskylä.

• Vanhatalo, E. (2007). Projektimallin kehittäminen proakatemialle. Opinnäytetyöraportti. Tampereen Ammattikorkeakoulu. https://oa.doria.fi/bitstream/handle/10024/7036/Vanhatalo.Eija.pdf?sequence=1

• Virkki, P. & Somermeri, A. (2002 tai vanhempi). Projektityö - kehittämisen moottori. Oy Edita Ab, Helsinki.

• Viirkorpi. P. (2000). Onnistunut projekti– opas kunta-alan projektityöskentelyyn. Suomen kuntaliitto. Helsinki. http://hosted.kuntaliitto.fi/intra/julkaisut/pdf/p071005095633P.pdf

http://www.oesd.noaa.gov/leadership/DEP_Manual_2ndEdt_Final.pdf



http://wateroutreach.uwex.edu/use/documents/NOAAEvalmanualFINAL.pdf



https://oa.doria.fi/bitstream/handle/10024/7036/Vanhatalo.Eija.pdf?sequence=1



http://hosted.kuntaliitto.fi/intra/julkaisut/pdf/p071005095633P.pdf

http://hosted.kuntaliitto.fi/intra/julkaisut/pdf/p071005095633P.pdf

projects 2013 02-01

Documents