Methodology tutorial - planning techniques: Difference between revisions

The educational technology and digital learning wiki
Jump to navigation Jump to search
 
Line 20: Line 20:
</div>
</div>


It is not necessary to use some real [[project management]] technique, but it could help getting your thesis done in time. The main advantages of doing some good planning are:
It is not necessary to use some real [[project management]] technique, but doing so could help getting your thesis done in time. The main advantages good planning are:
* Estimation of resources (time), i.e. a good planning effort will likely tell you to reduce the scope of your research.
* Better estimation of resources (time), i.e. a good planning effort will likely tell you to reduce the scope of your research.
* Self-control. If at some point your really are way behind schedule you have an opportunity to act.
* A tool for elf-control. If at some point you really are way behind schedule you have an opportunity to act.


=== The minimum ===
=== The minimum ===
Line 40: Line 40:
Scheduling means to do the following.
Scheduling means to do the following.


Divide the research plan  
* You will have to divide a project into task, called "work packages" (WPs)
* For each WP, you should provide an estimation in man/days or man/weeks it takes to finish
* A work package usually relates to a stage of the research plan, e.g. "the research plan", "field work", "development work".
* If possible, a work package should depend little on parrallel work packages
* Each work package can lead to a "milestone" (an important stage in your research plan") and/or to deliverables, e.g. tangible products such as "research plan".


* On découpe un projet en '' tâches'' (“Work packages”, WPs) et on estime le temps et les
To manage this scheduling process you then work with two (related kinds of graphics):
ressources nécessaires pour chaque “WP”
* An activity diagram that shows dependencies of work packages and a critical path.
** un “WP” correspond normalement à une étape de projet (design, travail de terrain,
* A bar diagram that illustrates activities over time
analyse) à un but de recherche ou combinaison des deux (étape X pour le but Y).
* On essaye d’éviter des trop grandes dépendances entre WPs, ainsi on peut les poursuivre
en parallèle et/ou de façon autonôme.
* Plusieurs WP peuvent aboutir à des “'' milestones'' ” et/ou “'' deliverables'' ”
** un “milestone” est une étape importante (par ex. déposition du projet)
** un “deliverable” est un objet fourni (par ex. un texte)
* Pour le scheduling on élabore 2 types de graphiques:
** un '' graphique d’activités'' qui montre les dépendances et le “chemin critique” <br />
(le chemin le plus long qui risque de poser un problème)
** un '' diagramme de barres'' qui montre le déroulement dans le temps


A retenir:
Planning also can include taking into account possible disasters.


* Planifier l’inattendu (perte de vos fichiers, sous-estimation de difficultés)
=== Activity diagrams ===


Activity diagrmas allow to better estimate the time it takes to reach an important stage and the global time needed.


 
The most well know methods are:
=== Les graphiques d’activités ===
 
* Ces graphiques vous permettent de mieux estimer le temps et de planifier vos activités,
mais ils servent également à monitorer (au moins une fois par mois) le statut de votre
projet !!
 
 
 
=== Les plus connus: ===
 
* PERT (Program Evaluation and Review Technique)
* PERT (Program Evaluation and Review Technique)
* CPM (Critical Path Method)
* CPM (Critical Path Method)


; A simple example:


* Each project is represented as a directed graph of tasks (the rectangles)
* Some tasks depend on other tasks
* For each task you must estimate its duration. Often you do this with three figures: expected minimum, most expected time and expected worst case.
* Then you also add mile stones, i.e. the completion of a group of tasks and that represent the end of an important stage.


=== Un graphique simple: ===
Here is a simple PERT-like graphic. It's in French, but should be easy to understant "jour" means "day". "Milestone 1 - Exploration" is done after you completed becoming familiar with the domain of study (5 days), after you studied an example (3 days), you found some references (3 days) and you though hard about finding an appropriate approach (3 days). "Milestone 2 - a project draft" needs and extra 5 days.
 
* Chaque projet est un réseau de tâches [ rectangles ]
* Certaines tâches dépendent d’autres tâches
* Pour chaque tâche on estime la durée, parfois on estime 3 chiffres:<br /> le minimum ,
le maximum et le temps le plus probable.
* Chaque “milestone”, c.a.d. groupe de tâches dépendantes achevés doit être daté [ovals]
* Avant de dessiner il est parfois plus simple de résumer la situation dans un tableau.
* Dessinez à la main ou avec un logiciel de dessin
 
 
 
=== Graphique “Pert” (à ne pas recopier tel quel !) ===


[[Image:book-research-design-257.png]]
[[Image:book-research-design-257.png]]


=== Les diagrammes de barres (Bar Charts) ===
=== Bar Charts ===
 
Le plus connu: Le Gantt Chart
 
 
 
=== Une proposition simple ===


Inscriptions:
Bar charts, also called GANTT Charts are easier to produce


* sur l’axe horizontale:
You can create a simple version simply with a word processor or a spreadsheet software:
** le temps (jours, demi-semaines, semaines, mois selon la taille du projet
* sur l’axe verticale:
** les “workpackages” (WP)
** On peut différencier pour chaque WP: intensité, participants, etc.
** les “milestones”


Construction du diagramme avec des moyens simples:
The horizontal axis is organized either by days, weeks or month (depending on the size of the project). For a master thesis we suggest to use weeks or month.


** avec des “___xxxx____” dans un éditeur
The vertical axis includes a list of work packages (WPs) and milestones.
** avec des tableaux (Excel, HTML, Word, etc.)
** avec un outil de dessin
** à la main en utilisant un calendrier de planning <br /> (on peut en bricoler un avec un
traitement de texte)


You then can fill in the table like this:
* use "XXX"” during the weeks you plan to work hard
* use "xxx" during the weeks you plan to work a bit on it




Line 123: Line 89:


{| border="1"
{| border="1"
! rowspan="1" colspan="1" |WP’s et milestones
! rowspan="1" colspan="1" |oct 6  08
! rowspan="1" colspan="1" |oct 13 08
! rowspan="1" colspan="1" |oct 20 08
! rowspan="1" colspan="1" |oct 27 08
! rowspan="1" colspan="1" |...
! rowspan="1" colspan="1" |...
! rowspan="1" colspan="1" |...
! rowspan="1" colspan="1" |
! rowspan="1" colspan="1" |
WP’s et milestones
! rowspan="1" colspan="1" |
26/5
! rowspan="1" colspan="1" |
29/5
! rowspan="1" colspan="1" |
! rowspan="1" colspan="1" |
2/6
! rowspan="1" colspan="1" |
! rowspan="1" colspan="1" |
5/6
! rowspan="1" colspan="1" |
! rowspan="1" colspan="1" |
 
! rowspan="1" colspan="1" |jun 1 09
! rowspan="1" colspan="1" |
 
! rowspan="1" colspan="1" |
 
! rowspan="1" colspan="1" |
 
! rowspan="1" colspan="1" |
 
! rowspan="1" colspan="1" |
 
! rowspan="1" colspan="1" |
 
! rowspan="1" colspan="1" |
 
|-
|-
| rowspan="1" colspan="1" |Exploration of the subject area
| rowspan="1" colspan="2" |xxxxxxxxxx
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
Exploration du domaine
| rowspan="1" colspan="2" |
xxxxxxxxxx
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |


|-
|-
| rowspan="1" colspan="1" |Case study 1
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
Première étude de 1-2 cas
| rowspan="1" colspan="2" |XXXxxx
| rowspan="1" colspan="1" |
 
| rowspan="1" colspan="2" |
XXXxxx
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
|-
|-
| rowspan="1" colspan="1" |Provisional research plan
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
Projet provisoire
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
 
| rowspan="1" colspan="1" |M
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
M
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
|-
|-
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
|-
|-
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
|-
|-
| rowspan="1" colspan="1" |Writing it up
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
Rédaction du rapport
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
x
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
xxx
| rowspan="1" colspan="1" |x
| rowspan="1" colspan="1" |xxx
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
| rowspan="1" colspan="1" |
 
| rowspan="1" colspan="3" |XXXXXXXXXX
| rowspan="1" colspan="3" |
XXXXXXXXXX
|}
|}



Revision as of 16:09, 10 October 2008

This article or section is currently under construction

In principle, someone is working on it and there should be a better version in a not so distant future.
If you want to modify this page, please discuss it with the person working on it (see the "history")

(translation needed)

Introduction

Learning goals
  • Learn how to make simple GANTT charts
  • Learn about PERTT charts
  • Get some other advice
Prerequisites
  • None
Moving on
Level and target population
Quality
  • low (translation needed)

It is not necessary to use some real project management technique, but doing so could help getting your thesis done in time. The main advantages good planning are:

  • Better estimation of resources (time), i.e. a good planning effort will likely tell you to reduce the scope of your research.
  • A tool for elf-control. If at some point you really are way behind schedule you have an opportunity to act.

The minimum

Create

  1. A list of things to do (workpackages)
  2. Deadlines for each
  3. Time needed for each

Then create a todo / start / deadline list, e.g. something like:

  • Literature review: start = oct 2020, end = feb 2021, volume = 1 man/month
  • Case study 1 field work: start = ....

Scheduling

Scheduling means to do the following.

  • You will have to divide a project into task, called "work packages" (WPs)
  • For each WP, you should provide an estimation in man/days or man/weeks it takes to finish
  • A work package usually relates to a stage of the research plan, e.g. "the research plan", "field work", "development work".
  • If possible, a work package should depend little on parrallel work packages
  • Each work package can lead to a "milestone" (an important stage in your research plan") and/or to deliverables, e.g. tangible products such as "research plan".

To manage this scheduling process you then work with two (related kinds of graphics):

  • An activity diagram that shows dependencies of work packages and a critical path.
  • A bar diagram that illustrates activities over time

Planning also can include taking into account possible disasters.

Activity diagrams

Activity diagrmas allow to better estimate the time it takes to reach an important stage and the global time needed.

The most well know methods are:

  • PERT (Program Evaluation and Review Technique)
  • CPM (Critical Path Method)
A simple example
  • Each project is represented as a directed graph of tasks (the rectangles)
  • Some tasks depend on other tasks
  • For each task you must estimate its duration. Often you do this with three figures: expected minimum, most expected time and expected worst case.
  • Then you also add mile stones, i.e. the completion of a group of tasks and that represent the end of an important stage.

Here is a simple PERT-like graphic. It's in French, but should be easy to understant "jour" means "day". "Milestone 1 - Exploration" is done after you completed becoming familiar with the domain of study (5 days), after you studied an example (3 days), you found some references (3 days) and you though hard about finding an appropriate approach (3 days). "Milestone 2 - a project draft" needs and extra 5 days.

File:Book-research-design-257.png

Bar Charts

Bar charts, also called GANTT Charts are easier to produce

You can create a simple version simply with a word processor or a spreadsheet software:

The horizontal axis is organized either by days, weeks or month (depending on the size of the project). For a master thesis we suggest to use weeks or month.

The vertical axis includes a list of work packages (WPs) and milestones.

You then can fill in the table like this:

  • use "XXX"” during the weeks you plan to work hard
  • use "xxx" during the weeks you plan to work a bit on it


Simple diagramme de barres avec un tableau

WP’s et milestones oct 6 08 oct 13 08 oct 20 08 oct 27 08 ... ... ... jun 1 09
Exploration of the subject area xxxxxxxxxx
Case study 1 XXXxxx
Provisional research plan M
Writing it up x xxx XXXXXXXXXX


Contrôle (Controlling)

Par qui ?

  • Dans l’industrie c’est le chef (ou encore le groupe) qui le fait,
  • ici vous êtes responsable principal !
  • Si vous faites un plan, donnez-le au rapporteur (ou intégrez-le dans la proposition)


Monitoring du progrès:

  • comparaison entre plan et réalité tous les mois
  • identification des raisons de déviation et actions correctrices
    • vos problèmes ne vont pas s’arranger seuls (!!)


Gestion des crises:

  • demandez de l’aide au directeur
  • négociez une redimension de votre projet si nécessaire
  • adaptez l’approche si (vraiment) nécessaire
  • Note: Des crises sont presques inévitables, mais un bon plan de recherche diminue les

risques et limite les dégats ....


Estimation de la durée d’un projet typique

Eléments de calcul:

tâches

par élément

total

  • Chercher un sujet et faire le plan de recherche

1 mois

  • littérature et début de rédaction

1 mois

  • contacter les sites (cas par cas)

1/2 journée

1 mois

  • visite d’un site

1 journée

  • codage et exploitation primaire d’une visite

2-3 jours

1 mois

  • analyses synthétiques / visualisations globales
  • rédaction du rapport (1ère version)

1 mois

  • révisions

1 mois

  • Total

6 mois

File:Book-research-design-258.png vous êtes trop optimistes !!

File:Book-research-design-259.png N’analysez pas trop de cas / sous-cas pour un travail de licence ou de diplôme !

... ou alors utilisez une démarche quantitative