[pypy-svn] r21597 - pypy/extradoc/talk/22c3

hpk at codespeak.net hpk at codespeak.net
Thu Dec 29 00:14:52 CET 2005


Author: hpk
Date: Thu Dec 29 00:14:36 2005
New Revision: 21597

Added:
   pypy/extradoc/talk/22c3/armin_rigo.jpg   (contents, props changed)
   pypy/extradoc/talk/22c3/closure.jpg   (contents, props changed)
   pypy/extradoc/talk/22c3/location.jpg   (contents, props changed)
   pypy/extradoc/talk/22c3/manmoon.jpg   (contents, props changed)
   pypy/extradoc/talk/22c3/pair.jpg   (contents, props changed)
Modified:
   pypy/extradoc/talk/22c3/slides-agility.txt
Log:
(bea,hpk) added some pictures, refined the slides


Added: pypy/extradoc/talk/22c3/armin_rigo.jpg
==============================================================================
Binary file. No diff available.

Added: pypy/extradoc/talk/22c3/closure.jpg
==============================================================================
Binary file. No diff available.

Added: pypy/extradoc/talk/22c3/location.jpg
==============================================================================
Binary file. No diff available.

Added: pypy/extradoc/talk/22c3/manmoon.jpg
==============================================================================
Binary file. No diff available.

Added: pypy/extradoc/talk/22c3/pair.jpg
==============================================================================
Binary file. No diff available.

Modified: pypy/extradoc/talk/22c3/slides-agility.txt
==============================================================================
--- pypy/extradoc/talk/22c3/slides-agility.txt	(original)
+++ pypy/extradoc/talk/22c3/slides-agility.txt	Thu Dec 29 00:14:36 2005
@@ -61,30 +61,20 @@
 EU funding
 ==================================================
 
-- proposal got good reviews from EU contracted experts 
+- Proposal written during sprints as well as distributed
+  (submitted Oct 2003)
+- got good reviews from EU contracted experts 
 - negotiation and finalisation: 1 year! 
-- Dec. 2004 EU contract starts
 - 2 year project, 1.3 Million Euro funding 
 - contractual framework + reporting obligations 
 
-XXX SKIPXXXXBidding for the EU-funding
+Work organisation (in the EU proposal)
 ============================================================
 
-- Project needed to reach critical mass, EU needed novel
-  compiler design techniques in OSS contexts
-- Proposal was written during sprints as well as distributed
-  (submitted Oct 2003)
-- Negotiations in Brussels (March 2004): key issues being 30% cuts in budget and  denied procedures for funding contribution
-- Project "started" Dec 2004: troubles with creating
-  consortium agreement fitting the OSS structure needed
-
-Individuals ... need to organise 
-==================================================
-
-- PyPy was first and still is a network of people
-- but EU only funds organisations 
-- two companies were founded
-- 7 partners form the EU consortium: 6 companies, 1 university
+- 14 workpackages and 58 deliverables, 3 phases 
+- Need for consortium meetings every month (IRC)
+- Sprints every 6th week (coordinating development and management work)
+- EU project aspects helped to gain mid-term/long-term focus
 
 Balance of interests 
 ==================================================
@@ -97,14 +87,14 @@
 - **at all levels it is about finding 
   models for co-operation that fit**
 
-Free co-operation basics 
+Sidenote: Free co-operation basics 
 ==================================================
 
 - Christoph Spehr's "foundation of free co-operation": 
 - negotiate any model you want (including dictatorship) 
 - question and change rules and roles at any time
 - everyone can "leave" the co-operation without penalty
-- leaving party taking a share with him/her
+- leaving party can even take a share with him/her
 
 Developers collaboration  
 ==================================================
@@ -123,22 +113,23 @@
 - evolving commercial opportunities 
   US companies asking for consulting (test tool)
   or wanting to hire/pay developers on pypy related tools
-  
+
 Organising the consortium
 ============================================================
 
+- PyPy was first and still is a network of people
+- but EU only funds organisations 
 - 7 partners, 3 previously not involved in the PyPy community
 - 6 partners only partially funded (50% cost models)
 - 2 new companies: "forced" entrepreneurship
-- not all involved developers get funded!
 
-Organising the work
+Consortium Meetings ... 
 ============================================================
 
-- 14 workpackages and 58 deliverables, 3 phases 
-- Need for consortium meetings every month (IRC)
-- Sprints every 6th week (coordinating development and management work)
-- EU project aspects helped to gain mid-term/long-term focus
+.. image:: saarbruecken_consortium.jpg 
+
+.. Bea
+
 
 Core of Agile practises: the people factor
 ============================================================
@@ -182,10 +173,25 @@
 ============================================================
 
 - Planning: location, venue, rough goals and activities, preparation with local hosts
+
+.. image:: location.jpg
+
+
+Sprinting the PyPy way 2
+============================================================
 - Doing: start up meeting, daily status meetings, pairprogramming
+
+.. image:: pair.jpg
+
+Sprinting the PyPy way 3
+============================================================
+
 - Closing: closure meeting (planning work between sprints), sprint reports, evaluations
 
-Sprinting the PyPy way 2
+.. image:: closure.jpg
+
+
+Sprinting the PyPy way 4
 ============================================================
 
 - 7 days with 1 break day
@@ -199,35 +205,39 @@
 - EU project culture
 - Traditional project management culture
 - Chaospilot (actionlearning and process design) culture
-- 5 different national cultures
+- 5+X different national cultures
 
 The challenge: managing diversities part 1.
 ============================================================
 
-- Developer driven process and Formal project organization 
-		- management team, technical board and partners
-		- sprint organising
-- increased risk of added workload of management
+- Developer driven process and formal project organization
+      - management team, technical board and partners
+      - sprint organising
+      - planning and focusing on technical tasks 
+- constant risk of added workload of management
   work on core developers 
 
 The challenge: managing diversities part 2.
 ============================================================
 
 - Agile strategies and Formal EU requirements 
-		- written high level requirements
-		- change control structures complicated
-- increased risk of missing opportunities and not
+      - written high level requirements
+      - change control structures complicated
+- constant risk of missing opportunities and not
   creating/reacting to change fast enough
 
 The challenge: managing diversities part 3.
 ============================================================
 
 - OSS community and hierarchies for "conceptual integrity"
-  - pypy-dev/core developers in technical board
-  - industrial usage vs research oriented work
-- increased risk for unbalancing the community
+      - pypy-dev/core developers in technical board
+      - industrial usage vs research oriented work
+- risk for unbalancing the community
 
-Picture: man on the moon 
+hitchikers guide ... 
+============================================================
+
+.. image:: manmoon.png 
 
 Problems and perspectives 
 ==================================================
@@ -241,8 +251,8 @@
 Working with people from the same planet 
 ==================================================
 
-- generally shared perspectives (synchronised 
-  rotation around a common center) on project success 
+- generally shared perspectives, synchronised 
+  rotation around a common center ... on project success 
 - different continents can be hard enough
 - potential for misunderstanding/friction 
 
@@ -273,23 +283,19 @@
 Cross-project pollination 
 ==================================================
 
-- zope-europe, canonical 
+- zope-europe, canonical, Calibre
 - dissemination: universities, IONA, Intel, HP ... 
-- Alan Kay / Squeak ... 
+- Alan Kay 
+- Squeak (21c3)
+- ... 
 
-Conclusion
+Conclusion / Food for thought
 ============================================================
+
 - A shared and challenging vision
 - Respecting and "exploiting" strengths of the different cultures involved
 - Designing minimalistic project structures channeling work, not hindering work
 - Room for group learning and creating change - not just reacting to change
-XXX ??
-- sprints 
-- how does that EU thing work 
-- EU review 
-- agile experiences from other projects 
-XXX
-
 
 .. |bullet| unicode:: U+02022
 .. footer:: Bea During, Holger Krekel |bullet| 22C3 |bullet| 29th December 2005 



More information about the Pypy-commit mailing list