All,
as we approaching the delivery of the first milestones for Openbravo 3.0, it
was time to re-establish our good practice of providing a public release
status tracking page.
If you recall, in 2.40 and 2.50, we had a nice status
tracking<http://wiki.openbravo.com/wiki/Release_Status>that was very
popular with our community. Since then we adopted Scrum, which
has been a very positive project methodology for us, but the status
reporting has moved to the individual team backlogs and the scrum of scrums
global backlog; while that information remained public, it has been very
difficult for our community to interpret it and make sense out of it.
To re-established the good practice of public status tracking, I have
created this read only Google spreadsheet:
http://spreadsheets.google.com/pub?key=0AjMsaCphoKkzdFpIUkgwNWtmTHJZVWJycXNlTHJjd3c&hl=en&gid=1
This link is also available out of the main page of the wiki.
*How to read this status report
*This status report is made of four tabs plus these instructions:
1. Project list
2. Overall status
3. Release calendar
4. Status export
*Project List*
This tab contains the list of projects that constitute the Openbravo 3.0
release.
Since Openbravo 3.0 is designed as a template or "distribution", made of
several modules, one of which is Core, there are different types of
deliverables involved in the 3.0 release:
* C: Core enhancements
* MCD: Modules that are part of the core distribution
* M: Modules
* D: Documentation
* I: Infrastructure enhancements
* O: Other
C and MCD deliverables constitute what goes in the base Openbravo 3.0
release; the other deliverables are either optional or indepedent.
Each project is labeled with a color coded status:
* W (gray): waiting for clarification (the scope of the project is not yet
clear)
* R (red): ready (the scope is clear but the work has not started)
* S (orange): started (work in progress)
* D (green): done
* N (cyan): not in scope (the project either didn't exist at that time or it
is no longer currently in scope)
The current status of the project is reported in the homonymous column.
Historical status is reported in the columns on the right hand side of the
report; for example, in column "24", you can find what the status was on
week 24 of 2010.
*Overall Status*
This tab tracks projects by week with a break down by milestone (RC1, RC2,
etc.). It also includes two burn down chart: one for the overall release and
one for the next milestone.
In terms of computation, projects are either done or not done (a started
project does not count towards progress on the release). For simplicity, all
projects are assumed of equal size.
*Release Calendar*
This tab lists the targeted release dates of each individual release
candidates.
*Status Export*
This tab contains the overall status in a format that can be easily used to
export and import in other applications for further analysis.
In the next few days, I will be blogging about this but I wanted to start
sharing this report from now.
Thanks,
Paolo
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Openbravo-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openbravo-development
