Note that this brings much of the original Westwood requirements to release well before Chandler actually hits its Westwood release.
Address why we're duplicating work being done out there and what third-party stuff we are using (this was Paul Hill's question -- was Paul thinking of Slide?)
Discuss how Scooby is already benefitting from much of the original and innovative design work on Chandler. We may even be able to leapfrog Chandler in some areas and lead the way. We also need to consider when to design specifically for the Web UI environment and its limitations and capabilities.
What are the extra pieces of work required to release a product: install, uninstall, help, accessibility, i18n -- note we're now starting to address these seriously and what that implies about how close we're getting to Kibble
Last fall we wanted to do 0.5, 0.6 and 0.7 and then hit Kibble -- that might have brought Kibble in early 2006 if we'd been perfect in executing and hardcore in rejecting features.
The good news is we're tracking decently towards that, with only 20% slip (1 month extra on top of five or six planned)
However we think that we'll need an extra release (0.8) to deal with problems and unforeseen requirements (accessibility, performance, wxWidgets).
Our projections are getting more accurate because the horizon is closer.