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
JUnit have done better (even if not green as much as they should).
graduation jaxws went smoothly (thanks to shane and daniel)
jsdt good to be "own project", has been getting more help
good at meeting deadlines
ian, good patch responsiveness
bug focus quality area ... less "home work" to do. Kept up.