Help Needed Regarding Time &/ Cost Saving Statistics

[Hawkraj]

Dear All,
Can any one of you who has implemented this wonderful framework in
their projects, tell me or give me a rough figure (estimates in
generall) of how much time is saved when compared with using no
framework (in terms of easy maintenance and development time) and also
how much swiz makes TESTING easy there by saving time n cost.
THANKS A LOT GUYS, i need to submit a small report in terms rough
estimate figures showing how much time & money is saved having used
this framework in the longer run than using none.
Once again THANKS a lot :-)

[Hawkraj]

And i know for sure that usage of this framework saves time & cost
during code maintenance (since it organizes the project well and mock
values for test can b given easily) but the thing is i need rough
estimates... Thanks

[Dan Bucholtz]

It will save some time during development, but the real time saver
will come in the inevitable refactoring, extending, etc. Code is some
of the cleanest code I've ever seen.

[John Griffin]

Hawkraj,

During a 2-week Scrum sprint with two developers working on the initial iteration of a project I would estimate a total savings of about 3 to 6 hours of development time. I know that doesn't sound like much but we've accurately determined that our productive sprint time per person is 3 hours/day (we are part of a 'Tools and Automation' team that supports ~15 other development teams and we get interrupted a lot).

Taking that into account it works out to 1 man-day per 2 week sprint. Also, remember that this is only the initial iteration. I can easily see in future sprints that refactoring/reworking times, etc. will be reduced by at least that much and probably more and as the code base increases complexity will be reduced (hard to estimate that right now).

Testing is slated for a future sprint so I can't help there.

Hope this helps.

John G.

--

You received this message because you are subscribed to the Google Groups "Swiz Framework" group.
To post to this group, send email to swiz-fr...@googlegroups.com.

To unsubscribe from this group, send email to swiz-framewor...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/swiz-framework?hl=.

--
John Griffin
Senior Software Engineer
Overstock.com

http://thediningphilosopher.blogspot.com/
Hibernate Search in Action (http://www.manning.com/bernard/)
__________________________________
Refactoring is NOT a substitute for design.

[John Griffin]

I should have said "one man-day PER DEVELOPER per 2 week sprint'. Sorry.

John G.

[maxim.porges]

I'd say you'll save 25% of the time you would have spent dealing with
boilerplate and singletons in the other frameworks. Swiz just gets out
of the way and lets you code.

In terms of testing, I'll assume you mean unit and integration testing
since Swiz doesn't look any different from any other framework to
functional testing tools like RIATest. Swiz will give you similar
gains here since a DI-based system makes it easy to wire up your test
fixtures with mocks or stubs. Mocks will also let you get better test
coverage than you would have gotten otherwise so that's another
bonus.

- max

[Hawkraj]

@John Griffin
THANKS a lot for ur efforts in replying me :-), it is very helpful &
update me if you could later after those testing sprints too...

@Max
THANKS a for ur explanation n support :-)

[Hawkraj]

@Dan
Thanks