Jump to: navigation, search

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

(New page: = WTP 3.3 Retrospective 08/4/2011 = == Purpose == Following every release, we have short retrospective to discuss possible ways our project might improve. This starts with a list of th...)
 
(Things we'd like to improve on)
Line 19: Line 19:
 
== Things we'd like to improve on  ==
 
== 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: 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
+
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.  
 
JUnits: we need more passing (green) builds, less intermittent failures, so its easier to focus when there is a problem.  
Line 27: Line 27:
 
We really should do some performance testing and have focused performance milestone where we focus on improving performance
 
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
+
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).  
+
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
+
Keep up better with base prereqs (more timely)
  
 
We should focus more (and measure) not using non-API, discouraged access
 
We should focus more (and measure) not using non-API, discouraged access
  
build improvements (still needed)  
+
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.  
 
while some backlogs were reduced/categorized, old, unimportant bugs closed, we need a system to not let backlog build up or grow.  
Line 51: Line 51:
 
Do we need more/better SDK Documents?  
 
Do we need more/better SDK Documents?  
  
Could we engage our "silent" adopters in other ways?  what problems adopters have or "had" with WTP?
+
Could we engage our "silent" adopters in other ways?  What problems adopters have or "had" with WTP?
  
 +
Better/more frequent engagement with our users in the newsgroups/forums.
  
 
= Links from Other Projects =
 
= Links from Other Projects =

Revision as of 12:29, 4 August 2011

WTP 3.3 Retrospective 08/4/2011

Purpose

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 some initial topics(some from last year) to help start the discussion in our status meeting. Notes will be collected, and 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).

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

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

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?

Could we engage our "silent" adopters in other ways? What problems adopters have or "had" with WTP?

Better/more frequent engagement with our users in the newsgroups/forums.

Links from Other Projects

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