1 / 13

Project work plan

Project work plan. St. Petersburg, May 18, 2011 Dr. Andrey Girenko www.giraf-pm.com. Basic definitions.

oswald
Download Presentation

Project work plan

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project work plan St. Petersburg, May 18, 2011 Dr. Andrey Girenko www.giraf-pm.com

  2. Basic definitions ...A work package is a major sub-division (sub-project, building block) of the proposed project with a verifiable end-point – normally a deliverable or a milestone in the overall project... The work plan shall be broken into work packages (WPs)…

  3. Basic definitions A deliverable represents a verifiable output of the project. Deliverables are often Reports (technical and formal) Technologies (e.g. software, prototypes, demonstrators) Principle publications (e.g. White Paper, website, database, etc.) Etc.

  4. Basic definitions A milestone is a Control point where decisions are needed with regard to the next stage of the project. Examples: End of requirements analysis End of evaluation trial Moment of obtaining one of the core technologies

  5. Features of a WP Size of a WP shall correspond to the size of the project (STREP – 7-12 WPs, IP – 10-18, etc.) Reasonable number of deliverables (2-6) Can/should be broken into TASKs Size of WPs within a project shall be balanced (no super-WP, no micro-WP) Logics underpinned by the goals of the project Do not forget standard WPs (MNG, DISS) Try to avoid mono-participant WPs Think of knowledge transfer and timing

  6. Coming back to our “dummy” project… Start thinking – what is needed to make it happen? The overall goal: To improve Math education in Europe, especially for transition from schools to Universities… The basic idea: Game-based collaborative TEL tools for learning Math in social networks. (A STREP project, with 8 partners, budget ca. 4 Meuro)

  7. Principle blocks… 9. Management and Coordination 8. Dissemination and exploitation 7. Testing and Evaluation 6. Integration 2. Pedagogical scenarios 3. Learner modeling 4.Flexible user interfaces 5. Assessment tools 1. Requirements analysis

  8. Connections… Management and Coordination Dissemination and exploitation Testing and Evaluation Integration Pedagogical scenarios Learner modeling Flexible user interfaces Assessment tools Requirements analysis

  9. Pert Chart example: IP

  10. Timing: Gantt Chart Milestone

  11. User centred design (optional) WP2 WP3 WP1 WP5 WP4 WP6 WP8 ISO standardized approach

  12. Gantt chart: IP using UCD (MS Office)

  13. Conclusions… Work plan is one of the important aspects defining the overall success Be practical, try to imagine how you will run the project While shaping WPs, try to make them easy-to-manage WP titles – try to highlight most innovative aspects of the project Highlight complementarity of activities For every WP try to keep in mind a Leader Use eye-catching graphical presentations Finally, try to get some “external” evaluation of the WP structure

More Related