[mashup-dev] A few observations and things to be careful in future
releases
Tyrell Perera
tyrell at wso2.com
Tue Jul 3 12:34:29 PDT 2007
Devs,
I would like to highlight some observations I made during the past 8
weeks, while creating the UI and hope it will benefit our future
releases. So here goes...
We need to have a more clear idea of features we plan to include in a
given release. It is true that we have a wiki page on requirements, but
if you look at the current UI you'll see how large the delta is,
although it's on the positive side.
I do agree that the UI looks cooler, but IMHO we paid the price in too
much complexity with not much help to the user. So many features were
added on a regular basis, most after-thoughts than carefully
architected.
Yes, most of these features are useful (obviously) but carefully
integrated features tend to be pain-free in both short and long run, for
us devs :)
The risk here is not merely in ad-hoc development but also putting QA
way off. I'm sure most of you will agree that there is a bunch of
features in 0.1, which the QA didn't really get to test. On the other
hand, there are some areas I wanted to concentrate on such as IE
compatibility + performance issues for 0.1, which had to be postponed.
Obvious suggestions;
1. Brainstorm and come to a consensus on features per release
2. Device a plan to prioritize and integrate additional features
without disrupting delivery time-lines.
Thoughts and comments please ...
regards,
Tyrell
--
Tyrell Perera
Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/
email: tyrell at wso2.com; cell: +94 77 302 2505
"Oxygenating the Web Service Platform."
More information about the Mashup-dev
mailing list