Sanjay wrote: >Possibly the above details are sketchy but the immediate questions for him >to firm up investment plans are: >- Will a Pharo based platform be appropriate > -- Technology ? > -- Robustness & support ?
Nothing you indicated in your estimates would be a bad fit for Pharo. Strong points for Pharo in a startup context are flexibility and very fast development. Not being 64-bit is a weak point, but you might be able to come up with a shared nothing architecture and lots of images running part of the problem. Do a spike integrating and deploying the technologies you need, and make sure you can do that again after each commit. >- what will be the team man year effort (ballpark estimate) for development, >testing, administration upto initial go-live ? 1, 10 or 10000. Portal is a semantics-free marketing term. Estimation at this level of fuzziness is a meaningless activity. What do you plan to have online at the end of the first week, the first month and the first quarter (at less and less detailed level)? Do you already have these users, or do you need to grow the number from zero? Create a story map and slice it. http://www.agileproductdesign.com/blog/the_new_backlog.html Stephan
