[pypy-svn] rev 1667 - pypy/trunk/doc/funding
jacob at codespeak.net
jacob at codespeak.net
Fri Oct 10 16:35:38 CEST 2003
Author: jacob
Date: Fri Oct 10 16:35:37 2003
New Revision: 1667
Modified:
pypy/trunk/doc/funding/B5.0_manage_bea.txt
Log:
Added formatting.
Modified: pypy/trunk/doc/funding/B5.0_manage_bea.txt
==============================================================================
--- pypy/trunk/doc/funding/B5.0_manage_bea.txt (original)
+++ pypy/trunk/doc/funding/B5.0_manage_bea.txt Fri Oct 10 16:35:37 2003
@@ -1,22 +1,19 @@
- B 5.0 Project Management
+B 5.0 Project Management
+========================
+PyPy as a project will be implementing an agile development
+lifecycle.This choice of development method will have effects on the
+way the project will be structured and managed.
+
+The project will have a structured project plan as is showed in this
+proposal (workpackages, Gantt-chart, deliverables, quality control
+etc). It also means that the project process, once the project get
+started, will work from a evaluate-feedback-change perspective, or so
+called "learning loops" in which project management will continuosly
+follow up on the intital project plan but also evaluate process,
+teameffectiveness, communication climate. From these learning loops
+change, when necessary, will be applied throughout the process.
- PyPy as a project will be implementing an agile
- development lifecycle.This choice of development method
- will have effects on the way the project will be
- structured and managed.
-
- The project will have a structured project plan as is
- showed in this proposal (workpackages, Gantt-chart,
- deliverables, quality control etc). It also means that the
- project process, once the project get started, will work
- from a evaluate-feedback-change perspective, or so called
- "learning loops" in which project management will
- continuosly follow up on the intital project plan but also
- evaluate process, teameffectiveness, communication
- climate. From these learning loops change, when necessary,
- will be applied throughout the process.
-
- To illustrate the focus on development process as well as project focus:
+To illustrate the focus on development process as well as project focus:
Stakeholders;
- EU
@@ -91,7 +88,7 @@
B 5.1 Project manager
-
+=====================
The PyPy project will have a project management structure that is
based upon two resources, Jacob Hallén as project manager and Beatrice
Düring as assisting project manager.
@@ -130,8 +127,8 @@
as followed:
Large scale projects:
-
-Jacob Hallén has been working since 1994 with large scale development
+---------------------
+*Jacob Hallén* has been working since 1994 with large scale development
projects. He was a consultant for, and later employee of, the LIBRIS
Department of the Royal Library of Sweden (http://www.libris.kb.se) in
the role of Technical Project Manager, with main focus on being
@@ -158,7 +155,7 @@
also the project leader for the Europython 2004 conference, to be held
in Göteborg, Sweden 9-11 June 2004.
-Beatrice Düring has experience in large scale education projects
+*Beatrice Düring* has experience in large scale education projects
involving working with consortiums of three companies servicing a
stakeholdergroup of about 30 recruiting companies. These large
education projects was part of a national program to solve shortages
@@ -185,8 +182,8 @@
of working with similar EU-funded projects since 1997.
Financial tracking in projects:
-
-Jacob Hallén has a widespread experience of founding and managing
+-------------------------------
+*Jacob Hallén* has a widespread experience of founding and managing
companies as well as being project manager for large scale
projects. He has also developed several accounting programs. When
being the CEO of NetGuide Scandinavia AB, the company was under
@@ -194,7 +191,7 @@
tight cost control and progress tracking. The management was
successful and the company grew to 35 employees under his leadership.
-The large scale education projects that Beatrice managed had a
+The large scale education projects that *Beatrice* managed had a
profitmargin of 20% which was met. The total budget for these projects
was SEK 20 million. She has also recently been involved in the
prestudy, budgeting and start of a 6 year long education project in
@@ -205,7 +202,7 @@
result responsibility.
Leadership skills:
-
+------------------
Jacob Hallén has experienced leadership challenges in different
situations. In his role as an officer in the reserve of the Swedish
army he has been deputy rifle platoon leader in the Swedsh UN forces
@@ -243,13 +240,13 @@
B 5.2 Management structure
-
+==========================
B 5.3 Coordinator dont write
-
+==============================
B 5.4 Project meetings
-
+======================
Project Meetings
-
+----------------
Management Board will meet at the start of the project and two times
per year or on an ad hoc basis as requested. The meetings will
normally be scheduled to rotate between countries of the EU and mainly
@@ -262,7 +259,7 @@
in the internal project web.
Team Meetings
-
+-------------
The project team will meet at the "sprints" which take place on a six
week cycle ( se below). During the sprints, there will be time
allotted to discuss and evaluate the project process, track progress,
@@ -272,7 +269,7 @@
documented and put up in the internal project web.
Project review workshops ("learning loops")
-
+-------------------------------------------
Every six months, as preparation for the Management Board meetings and
project reviews from the EU project office, the project management
team invites the team to an evaluation workshop, lasting for a day, in
@@ -286,7 +283,7 @@
"Sprint" Meetings are the key to PyPy's technical development
-
+-------------------------------------------------------------
Key to PyPy's technical development and research are so called
"sprints". These publically announced one-week meetings serve as an
intense working forum to rapidly discuss and implement key PyPy ideas
@@ -329,9 +326,9 @@
developers.
Technical decisions
-
+-------------------
Major design or technical decisions are usually reached through
-consensus during the sprints. If a conflict cannot be resolved there
+consensus during the sprints. If a conflict cannot be resolved there
then the technical board gets the final say. The members of the
technical board are appointed by a vote of everyone who has commit
rights to the source repository. However, it is expected that design
@@ -345,7 +342,7 @@
good design decisions.
B 5.5 Quality control of technical development
-
+==============================================
The PyPy project will ensure quality by a variety of means. On the
grand scale, the involvement of excellent researchers ensures that the
general direction takes care of latest insights in language
@@ -380,7 +377,7 @@
standards.
Additional Quality procedures
-
+-----------------------------
The project manager will circulate a draft Quality Management plan for
the project prior to first Project Meeting and and then present it for
approval at the first Meeting. It should complement the prescribed
@@ -402,7 +399,7 @@
B 5.6 Communication and reporting
-
+=================================
The project process will be reported as follows:
Monthly written status reports to the Management Board/Technical
@@ -453,5 +450,6 @@
B 5.7 Consortium dont write
-
+=============================
B 5.8 Ip dont write
+=====================
\ No newline at end of file
More information about the Pypy-commit
mailing list