[pypy-svn] rev 1597 - pypy/trunk/doc/funding
lac at codespeak.net
lac at codespeak.net
Mon Oct 6 16:58:44 CEST 2003
Author: lac
Date: Mon Oct 6 16:58:43 2003
New Revision: 1597
Added:
pypy/trunk/doc/funding/B5.1_project_manager.txt
pypy/trunk/doc/funding/B5.2_management_structure.txt
pypy/trunk/doc/funding/B5.3_coordinator.txt
pypy/trunk/doc/funding/B5.4_meetings.txt
pypy/trunk/doc/funding/B5.5_quality.txt
pypy/trunk/doc/funding/B5.6_communication.txt
pypy/trunk/doc/funding/B5.7_consortium.txt
pypy/trunk/doc/funding/B5.8_ip.txt
Modified:
pypy/trunk/doc/funding/B5.0_management.txt
Log:
Break out B5 into chunks. Now Holger has all the work he asked for and
then some. Sprints get mentioned in B5.0, and talked a lot in B5.4
Modified: pypy/trunk/doc/funding/B5.0_management.txt
==============================================================================
--- pypy/trunk/doc/funding/B5.0_management.txt (original)
+++ pypy/trunk/doc/funding/B5.0_management.txt Mon Oct 6 16:58:43 2003
@@ -16,7 +16,29 @@
add text!
-FIXME_LAURA FIXME_JACOB
+FIXME_LAURA FIXME_JACOB FIXME_HOLGER This is the section that needs the
+longest about Sprints... Also need to say that we have made a working
+prototype, have worked together before,
+
+B.5 Project management
+
+Describe the organisation, management and decision making structures
+of the project. Describe the plan for the management of knowledge, of
+intellectual property and of other innovation-related activities
+arising in the project. (Recommended length three pages)
+
+This section should describe how the proposed project will be managed,
+the decision making structures to be applied, the communication flow
+within the consortium and the quality assurance measures which will be
+implemented, and how legal and ethical obligations will be met.
+
+Quality of the management
+
+Make it clear how progress will be monitored and how an effective
+management structure will be put in place, with agreed lines of
+communication and responsibility. Describe how corrective actions
+will be initiated and how conflicts will be resolved.
+
here we need to say
Added: pypy/trunk/doc/funding/B5.1_project_manager.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/funding/B5.1_project_manager.txt Mon Oct 6 16:58:43 2003
@@ -0,0 +1,78 @@
+FIXME JACOB
+B.5.1 Project Manager
+
+Every project must have a Project Manager. He will be responsible for
+the Management of the Project and execution of the contract. He
+is appointed by the Co-ordinator and chairs the Management
+Meetings. He approves all outputs and reports, is the prime
+external interface and also may be the Technical Director (if one
+is deemed necessary).
+
+
+There is some confusion as to the role of the Project Manager. This is
+not an administrative chore. A Project Manager will require some
+administrative support, but that is far from the essence of the job.
+The administrative functions such as status tracking, financial
+reporting, change control and project library maintenance are really a
+minor part of the overall job.
+
+Project management activities
+
+Specific targeted research projects will also include an overall
+management structure. Over and above the technical management of
+individual work packages, an appropriate management framework linking
+together all the project components and maintaining communications
+with the Commission will be needed.
+
+Project management will include:
+
+· co-ordination of the technical activities of the project;
+
+· the overall legal, contractual, ethical, financial and administrative
+ management of the project;
+
+· preparing, updating and managing the consortium agreement between
+ the participants;
+
+· co-ordination of knowledge management and other innovation-related
+ activities;
+
+· overseeing the promotion of gender equality in the project;
+
+· overseeing science and society issues, related to the research
+ activities conducted within the project;
+
+· obtaining audit certificates (as and when required) by each of the
+ participants;
+
+· bank guarantees for SMEs (if applicable).
+
+Successful Project Management of a FrameWorkprogram Project
+requires various skills and knowledge. In my view it requires a
+person with the following attributes
+
+ · Good appreciation of the relevant business area
+
+ · Participation in a previous Framework project
+
+ · Knowledge of Framework procedures
+
+ · Good interpersonal skills
+
+ · Well organised and systematic in own work
+
+ · Good knowledge of ISO 9001
+
+ · Good knowledge of English
+
+ · Some knowledge of project technical area
+
+ · Some knowledge of financial management
+
+Project Management is a combination of all of the above skills. Extra
+strength in some areas could compensate for weakness in others.
+Remember this function includes legal responsibility aspects and thus
+keeping of good records is essential. Any telephone calls and
+agreements, especially with the Project Officer should be minuted
+and/or confirmed in writing, at least by email.
+
Added: pypy/trunk/doc/funding/B5.2_management_structure.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/funding/B5.2_management_structure.txt Mon Oct 6 16:58:43 2003
@@ -0,0 +1,23 @@
+FIXME_HOLGER
+
+We want the 2 boards. Stick youself for PBF, Nicolas for
+Logilab, Jacob for Strakt Alastair for DKFI into the Management box.
+
+Then make a technical board. Every package responsible person must
+be in here. Tim Peters needs to be given responsibility for one thing,
+also the coordinate with Cpython Workpackage.
+
+FIXME_NICO you do the WP changing.
+
+ B.5.2 Management Structure
+
+As this type of project is essentially the same as the previous RTD
+project, I would maintain the traditional structure as follows -
+
+(see the PDF STREP-template.pdf)
+
+For smaller projects and depending on the technical abilities of the
+company representatives, it is sometimes possible and more effective
+to combine the Management and Technical Boards although they must
+continue to deal with both aspects.
+
Added: pypy/trunk/doc/funding/B5.3_coordinator.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/funding/B5.3_coordinator.txt Mon Oct 6 16:58:43 2003
@@ -0,0 +1,63 @@
+FIXME Alastair
+write this.
+FIXME EVERYBODY
+proof this
+
+
+ B.5.3 Co-ordinator
+
+This is the principal interface to the Commission - both during
+proposal and project stages and is responsible for submitting the
+proposal; also conducts the contract negotiation. During project
+appoints the Project Manager, submits all reports, normally handles
+the financial statements and payments, chairs the Project Management
+Board and has overall control of the project.
+
+Note that the Coordinator normally appoints the project manager. If,
+under rare circumstances it is decided to split the management into
+Managerial and Technical parts, then a Technical Director is also
+appointed, although he is not necessarily from the Coordinating
+Organisation.
+
+
+A distinction between Financial Coordinator and Scientific
+Coordinator is no longer recognised in the contract. Any
+distinctions of role between the partners must be embodied in
+the Consortium Agreement.
+
+It is also normal for the Technical Director to chair a Technical
+Board that would consist of the Key Technical staff - one per partner
+normally or Work package leaders. Such meetings are normally held
+adjacent to Management Board meetings.
+
+
+The Technical Director would also sit on the Management Board ex
+officio and the Project Manager on the Technical Board.
+
+It is normal to have a structure as shown above under B.5.2 (note the
+Technical Board could be combined into the Management board).
+
+I am trying here to give a flavour of the type of words and content to
+use. It is not exhaustive. Do not copy them verbatim.
+
+
+A Management Board will be created that will be responsible for the
+successful completion of the project and the exploition of its
+result. It will be chaired by the appointed Project Manager and will
+consist of a senior representative of each partner.
+
+Decisions regarding the project will be made by vote with each partner
+having a single vote. In cases of a tie, the project manager will
+have a casting vote.
+
+ The role of the Management Board will include the following -
+
+ · Management of resources in order to meet schedules and goals
+ · To ensure the quality management of the project
+ · Tracking of costs related to budget
+ · Resolution of conflicts
+ · Creation of technology implementation plan and its updating
+ · Ensuring compliance with legal and ethical obligations
+
+Explain the role/responsibilities of Technical Board if constituted
+and state that it reports to the Management Board
Added: pypy/trunk/doc/funding/B5.4_meetings.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/funding/B5.4_meetings.txt Mon Oct 6 16:58:43 2003
@@ -0,0 +1,11 @@
+B.5.4 Project Meetings
+
+The Management Board will meet at the start of the project and (2/3/4)
+times per year or on an ad hoc basis as requested. The meetings will
+normally be scheduled to rotate between the principal contractors
+home base.
+
+Add info on Technical meetings as required.
+
+FIXME HOLGER THIS IS WHERE YOU DISCUSS THE SPRINTS IN MOST DETAIL.
+FIXME LAURA I HAVE A THING OR SO TO SAY IF HOLGER DOESN'T
\ No newline at end of file
Added: pypy/trunk/doc/funding/B5.5_quality.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/funding/B5.5_quality.txt Mon Oct 6 16:58:43 2003
@@ -0,0 +1,22 @@
+FIXME HOLGER FIXME JACOB
+write what we have. We don't apparantly have to have any of the rest.
+We just have to say that we will have a plan that will address blah blah
+B.5.5 Quality procedures
+
+The project manager will circulate a draft Quality Management plan
+forthe project prior to first Project Meeting and and then present it
+for approval at the first Meeting.
+
+ It will contain as a minimum, procedures for -
+
+ · Document procedures, standards and control
+ · Issue control for documents
+ · Reporting procedures, frequency and format
+ · Communication procedures
+ · Corrective actions
+ · Exception control
+ · Conflict resolution
+ · Meeting draft agenda
+ · Format of meeting minutes
+ · Tracking system for actions
+ · Specific responsibilities within the project
Added: pypy/trunk/doc/funding/B5.6_communication.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/funding/B5.6_communication.txt Mon Oct 6 16:58:43 2003
@@ -0,0 +1,8 @@
+B.5.6 Communication and Reporting.
+
+Amplify here specific policies on this subject ie use of email or
+communication via web site management page, telephones, video
+conferencing, frequency etc
+
+FIXME HOLGER -- here we do the Open Source is all about Communication
+song
\ No newline at end of file
Added: pypy/trunk/doc/funding/B5.7_consortium.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/funding/B5.7_consortium.txt Mon Oct 6 16:58:43 2003
@@ -0,0 +1,8 @@
+B.5.7 Consortium Agreement
+
+A Consortium Agreement between the partners is now mandatory and must
+be signed before any participant start work on the project. The
+Project Manager must be responsible for this activity.
+
+FIXME LAURA -- we just have to say we will have one. Don't work on this
+until after the 15th.
\ No newline at end of file
Added: pypy/trunk/doc/funding/B5.8_ip.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/funding/B5.8_ip.txt Mon Oct 6 16:58:43 2003
@@ -0,0 +1,18 @@
+B.5.8 Management of Knowledge and Intellectual Property
+
+The rules regarding the protection dissemination and use of knowledge
+have been simplified and a larger flexibility is granted to the
+participants:
+
+- rules are identical for all participants;
+
+- rules concentrate on the principles and provisions considered
+ necessary for an efficient cooperation and the appropriate use and
+ dissemination of the results;
+- participants may define among themselves the arrangements that
+ fit them the best within the framework provided in the model
+ contract.
+
+See also comments under B.3.3.1 and B.3.3.2 and address here.
+
+FIXME_LAURA write up what IPR helpdesk told you.
\ No newline at end of file
More information about the Pypy-commit
mailing list