Postmorten of htmled

I measured the recent work on htmled with Process Dashboard's PSP0. Since I want to continue evolving the project, I think I'll have a good opportunity to try to improve the effort estimations and the planning.

So, lets resume the results:

Time

	Plan	Actual	Actual %
Planning	24	93	9.35%
High-level Design	0	0	0%
High-level Design Review	0	0	0%
Detailed Design	120	46	4.62%
Detailed Design Review	0	0	0%
Code	240	546	54.9%
Code Review	0	0	0%
Compile	24	8	0.8%
Test	48	275	27.6%
Postmortem	24	27	2.71%
Total	660	995	-------

Defects Injected

	Plan	Actual	Actual %
Planning	0	1	5%
High-level Design	0	0	0%
High-level Design Review	0	0	0%
Detailed Design	0	5	25%
Detailed Design Review	0	0	0%
Code	0	9	45%
Code Review	0	0	0%
Compile	0	0	0%
Test	0	5	25%
Postmortem	0	0	0%
Total	0	20	-------

Defects Removed

	Plan	Actual	Actual %
Planning	0	0	0%
High-level Design	0	0	0%
High-level Design Review	0	0	0%
Detailed Design	0	1	5.26%
Detailed Design Review	0	0	0%
Code	0	7	36.8%
Code Review	0	0	0%
Compile	0	1	5.26%
Test	0	10	52.6%
Postmortem	0	0	0%
Total	0	19	-------

More time and defects than I would expect and I knew the code basis and the requirements very well. I think that it is OK if I take into account the fact that I'm not very experienced with Python and that I had plenty of interruptions.

htmled ready for production use!

After a while working on this I think I will be able to make my blog update based on the current status of htmled. It processes correctly this Handbook file, being that I even found and corrected some errors in the HTML with it. As stated previously I'm using Test Driven Development (TDD) and using the Process Dashboard to track time and defects. It was fun, mainly because I used Python, TDD and knew very well the requirements ;-).

Mainly I hope it improves dramatically the readability of my blogging. I'm not following full commercial blogging rules, but, heck, I don't intend to earn money with this, just publicize properly my playground.