Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

Team thoughts on continuous improvement 32

WTP 3.2 Retrospective 06/17/2010


Following every release, we have short retrospective 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 initially notes from our 6/17/2010 status meeting. Overtime the notes will be categorized, organized, collapsed, etc., to make correspondence to actions clear.

Things we've done well

Maintained last year's "good" list! (esp. such as, keeping up specialty break out meetings, e.g. for Java EE work)

JUnits have done better (even if not green often, there are fewer numbers of intermittent failures).

The graduation and integration of JAX-WS code went smoothly (thanks to Shane and Daniel)

JSDT creation went well, good to be "own project", has been getting more visibility, interest, help

WTP is good at meeting deadlines (less stress, less run over into weekends, etc.)

Good, timely patch review and application responsiveness from source editing team

weekly bug focus quality area ... less "home work" to do week to week. Teams kept up and/or had less backlog to start with.

welcomed more contribution in source editing improved diversity in source editing

Things we'd like to improve on

weekly quality focus: would be nice to raise the bar ... actually fix more old bugs (not just triage)

weekly quality focus: add metrics, such as track fix rates

JUnits: we need more passing (green) builds, less intermittent failures, so its easier to focus when there is a problem.

We really should do some performance testing and have focused performance milestone where we focus on improving performance

should do more explicit verification and closing of fixed bugs

documentation -- longer term planing from everyone would help doc. teams plan what they need (as is, sort of milestone by milestone).

keep up better with base prereqs more timely

We should focus more (and measure) not using non-API, discouraged access

build improvements (still needed)

while some backlogs were reduced/categorized, old, unimportant bugs closed, we need a system to not let backlog build up or grow.

Listing/engaging adopters (e.g. we left out Spring IDE from release materials? RIM?)

Publicly listing and acknowledging new contributors? special events? (i.e. we have "new and noteworthy" for function ... but many other "cool activities".

Should we have more tutorials? or webinars? cheat sheets? Special tips? (JSF and Dali do some of this, there is an XML Example). Need more? Encourage community to contribute?

Could we engage/encourage earlier testing from users/adopters?

Do we need more design documents?

Do we need more/better SDK Documents?

Links from Other Projects

Other projects also have their own "retrospectives". Some are linked here, to cross-reference others observations and findings.

Back to the top