Difference between revisions of "Team thoughts on continuous improvement 31"

From Eclipsepedia

Jump to: navigation, search
(New page: = WTP 3.1 Debriefing 07/09/2009 = == Purpose == Following our WTP 3.1 release, we'd like to have a short meeting with committers and contributors to discuss possible ways our project mig...)
 
(Things we've done well)
Line 8: Line 8:
  
 
== Things we've done well ==
 
== Things we've done well ==
 +
 +
Policy and practice of firm deadline for weekly I-build with same-day declare.
 +
 +
Regular, consistent weekly build good, even if actual delivery following Tuesday.
 +
 +
Some long standing performance bugs finally addressed (in XML Editing and related).
 +
 +
Plans (XML format and bugzilla entries) with dynamic, iterative updates.
 +
 +
Team discussion "broken out" so doesn't overwhelm WTP status call with detail.
 +
 +
Dates on Google calendar.
 +
 +
Frequent (weekly) but short status calls.
  
 
== Things we'd like to improve on ==  
 
== Things we'd like to improve on ==  

Revision as of 20:59, 9 July 2009

Contents

WTP 3.1 Debriefing 07/09/2009

Purpose

Following our WTP 3.1 release, we'd like to have a short meeting with committers and contributors to discuss possible ways our project might improve.. These include things that you think we did well in this release and things that you think should be changed or improvements that can be made, process changes, etc. This feedback will become critical to our success for our next major release

Please use this page to express priorities, make notes, and brainstorm as many ideas as possible. You can add things before the meeting (or after) just make clear when added.


Things we've done well

Policy and practice of firm deadline for weekly I-build with same-day declare.

Regular, consistent weekly build good, even if actual delivery following Tuesday.

Some long standing performance bugs finally addressed (in XML Editing and related).

Plans (XML format and bugzilla entries) with dynamic, iterative updates.

Team discussion "broken out" so doesn't overwhelm WTP status call with detail.

Dates on Google calendar.

Frequent (weekly) but short status calls.

Things we'd like to improve on