Hi,
Copy-pasting the latest discussion with Ajay on vWorker:
== From Ajay ==
Alright for the new deadline - I've just extended it. Since this is the
second deadline extension, can you explain a bit more about what made
this necessary?
Ajay>> Xavier I have reviewed the intial timeline I had requested while
bidding on the project which was for 30 working days. I think I failed
to clarify that
working days did not include Saturdays and Sunday. So our expectation
was that we should be able to finish the project by about 10th of
December.
I undertand how it can be necessary to extend the deadline when we
actually start actually working on the project, but what went wrong with
the first deadline extension? How can we make sure we won't need to
extend it again?
Ajay>> I have reviewed with Pramendra all the pending tasks for this
application. Following are the tasks that are pending right now:
1. HTML integration - Some of it is done but as the design is a bit
compliated it is taking more time
2. Test cases - Pramendra is in the process of completing the test
cases.
3. Functional test cases with Windmill - These are dependent on HTML
integration as the tests need to be recorded and played.
About releasing a part of the founds - I'm open to it, it's a good
policy to split payments in different chunks, it makes things more
manageable, both from a financial and project management perspective.
The only thing I will need for this is to make sure that all
requirements (unit tests, code comments, etc. - cf requirements section
of the specifications) are met for the current codebase. But I don't
think it is the case currently, no?
Ajay>> As per my discussion with Pramendra, except for the above three
items all the changes including
1. Localization related with .po files
2. Documentation with PHP documenter
3. Integration with OWA
Are already done.
As per our latest and final estimates:
1. Unit Test case creation and testing will take about 3 days
2. HTML integration will take another 3 days
3. Functional test recording and play back with Windmill should not take
more than 2-3 days. Though this one is tentative as we have not tried
windmill on this application yet.
4. Code review - I think before the application is accepted there would
be a code review, comments and may be some changes / testing etc. This
should take about 4 days. Though this step depends on your availability
also. Please do let me know if you have had a chance to look at the code
yet.
We should be able to complete the above 3 steps by 25 December. So I
would request you to modify the deadline to 25 December so that we do
not have to ask for any extensions any more. What we are doing to ensure
that we don't miss this deadline:
1. We have setup daily deadlines internally and are meeting the same.
2. We are closely monitoring the progress each day and have kept a
experianced developer on a stand by if there is any slippage
3. Only new part that we can give some surprises is windmill testes.
Do let me know if I missed any point that needs further clarification,
or anything you see that can cause any slippage?
Also, please let me know if it's possible for you to release 50% funds.
Best Regards,
Ajay
== From me ==
By flouzo with 21 ratings
>From Paris, Ile de France in France (see local date/time)
Posting # 32,950,824 on Thursday Dec 16, 2010 10:03:35 AM EDT
Hi Ajay,
Thanks for the details! Yes, I have just seen both of your messages - I
usually check my email once a day, and I had done it already yesterday
when you sent your message.
Ajay>> Xavier I have reviewed the intial timeline I had requested
>>while bidding on the project which was for 30 working days. I think I
failed to clarify that
>>working days did not include Saturdays and Sunday. So our
>>expectation was that we should be able to finish the project by
>>about 10th of December.
Ah, sorry about that - my mistake then. : )
>>1. Unit Test case creation and testing will take about 3 days
>>2. HTML integration will take another 3 days
>>3. Functional test recording and play back with Windmill should not
take more than 2-3 days. Though this one is tentative as we have not
tried windmill on this application yet.
For releasing a part of the funds, as said in my last message it's
possible, but I will need to have all the technical requirements (cf
specs, this includes unit tests, but a finished HTML integration is not
necessary). So if you focus first on meeting these requirements for the
current codebase, I can release 50% as soon as they are met, and then
you would finish the remaining for the other 50%.
This is needed because code that hasn't been properly tested,
documented, etc. is basically very hard to get to take over by another
developer. If there was an issue with the final deliverables, I need to
ensure that I can pass over what I have paid for to someone else.
>>4. Code review - I think before the application is accepted there
would be a code review, comments and may be some changes / testing etc.
This should take about 4 days. Though this step depends on your
availability also. Please do let me know if you have had a chance to
look at the code yet.
Yes - I have started reviewing the code, and entered a few issues in the
bugtracker already: https://bugs.launchpad.net/cardstories/+bugs . There
are also a few issues about the design that have been entered too.
Pramendra told me he would have a look at those after completing his
current tasks, so I've hold the review for now. But I'll be available
during the Christmas period, so we shoul be able to do this together as
needed.
We should be able to complete the above 3 steps by 25 December. So I
would request you to modify the deadline to 25 December so that we do
not have to ask for any extensions any more. What we are doing to ensure
that we don't miss this deadline:
>> 1. We have setup daily deadlines internally and are meeting the same.
>> 2. We are closely monitoring the progress each day and have kept a
experianced developer on a stand by if there is any slippage
>> 3. Only new part that we can give some surprises is windmill testes.
Good to know! Thanks for those details.
Btw, to keep the rest of the people involved in the project in the loop,
do you mind if I copy& paste your messages on the project public
mailing-list? Would make it easier for me : )
Thanks!
Xavier.
To: flouzo and CodeFire Technologies Pvt Ltd
Alert # 3,930,258 on Thursday Dec 16, 2010 10:05:16 AM EDT
Alert: Deadline change (note: this is a current deadline)
flouzo changed the deadline to Sunday Dec 26, 2010 12:01:05 AM (60.88
days from Tuesday Oct 26, 2010 2:53:53 AM). flouzo, if this is not what
you intended, please update the deadline on the site from your project
control panel.CodeFire Technologies Pvt Ltd, if this is not what you
believe was agreed upon, please immediately inform the employer onsite
and work out the misunderstanding. If either of you has a problem you
cannot resolve concerning the deadline, please notify vWorker.com for
assistance.
== From Ajay ==
Hi Xavier,
Thanks for the response. Feel free to paste the message on the mailing
list.
Best!
_______________________________________________
Farsides mailing list - [email protected]
Wiki: http://farsides.com/
List: http://farsides.com/ml/
Forum: http://farsides.com/forum/
Ideas: http://farsides.com/ideas/
Chat: http://farsides.com/chat/
