Jump to: navigation, search

Team thoughts on continuous improvement 31

Revision as of 10:53, 14 July 2009 by David williams.acm.org (Talk | contribs) (Things we've done well)

WTP 3.1 Debriefing 07/09/2009


Following our WTP 3.1 release, we had short post mortem to discuss possible ways our project might improve. This starts with a list of things we like and don't like about how the release went, and will evolve into action items with people assigned to be responsible, where appropriate.

Below are the raw notes from our 7/9/2009 status meeting.

Things we've done well

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

Regular, consistent weekly (Thursday) is 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 worked well.

Team discussion "broken out" to their own regular meetings, so they don't overwhelm WTP status call with detail (that only a few on call are interested in).

Dates on Google calendar helps keep all coordinated by having dates in a central spot.

Frequent (weekly) but short status calls.

Things we'd like to improve on

Too many intermittent junit failures: especially in that there are too many long periods build failures. Failures (even compile errors) begin to be ignored since failures so common.

Builds take too long: especially in that it takes a long time to get notified if problem or not after checking in code.

Lack performance suite or benchmarks.

Lack of dependent project communication, such as emf or platform, both if and when "breaking" changes coming and once we learn of it, seems there's no central place to learn of all "breaking changes".

Hard for newcomers (even adopters) to get "acquainted" or integrated with WTP policies, practice, and rhythms so testing isn't done early enough and communication is awkward, hard and takes too long to get worked out. [The break-out meetings such as for JEE have helped.]

Lots of code checked in with no junit test (both new function and bug fixes).