[Google_spring08] Need to postpone transition meeting to April 18

[Michael L. Marcus]

Michael,

We have made less progress on the second prototype than expected, and
we would like to postpone tomorrow's transition meeting until we have
something complete to show you. If you are available, we would like
to move the meeting to next Friday, April 18 at 4:30 PM.

In lieu of the meeting tomorrow, we would still like to have the
conference call as scheduled.

Please let us know either way if this is agreeable.

Thanks,
Mike
_______________________________________________
Google_spring08 mailing list
Google_...@cs.nyu.edu
http://www.cs.nyu.edu/mailman/listinfo/google_spring08

[Michael Schidlowsky]

Michael,

I'd like to learn more about what happened. What exactly are you guys
behind on? Have you evaluated what caused the problem and how you
could have prevented it in the first place?

What features do you plan to present at our next meeting?

-Michael

[Michael L. Marcus]

We are planning to present a sample Rails application (message board)
that does Create and Read operations both locally and remotely. At
this point, we have the code in pieces as completed by the individuals
in the group; we now need to pull everything together, integrate it
into the Rails plug-in architecture and do end-to-end testing.

The problem here was an underestimation of effort. We did not leave
enough time for individual group members to complete their tasks.
Going forward, we will attempt to estimate better now that we have a
better sense of what is involved at a low level. The group members
will also be managing time better to increase the hours spent coding
for the project.

On Thu, Apr 10, 2008 at 2:58 PM, Michael Schidlowsky
<mschid...@google.com> wrote:
> Michael,
>
> I'd like to learn more about what happened. What exactly are you guys
> behind on? Have you evaluated what caused the problem and how you
> could have prevented it in the first place?
>
> What features do you plan to present at our next meeting?
>
> -Michael
>
>
>
>
> On Thu, Apr 10, 2008 at 10:36 AM, Michael L. Marcus <mlm...@nyu.edu> wrote:
> > Michael,
> >
> > We have made less progress on the second prototype than expected, and
> > we would like to postpone tomorrow's transition meeting until we have
> > something complete to show you. If you are available, we would like
> > to move the meeting to next Friday, April 18 at 4:30 PM.
> >
> > In lieu of the meeting tomorrow, we would still like to have the
> > conference call as scheduled.
> >
> > Please let us know either way if this is agreeable.
> >
> > Thanks,
> > Mike
> >
>

--
Quid quid latine dictum sit, altum videtur.

[Michael Schidlowsky]

My apologies, but I just realized that starting next thursday I'm
going to be in California, then Dublin, and then California again for
various reasons. So I'm leaving on thursday the 17th and coming back
on the 28th. So not to put you guys on the spot, but we're going to
have to do this before I leave.

Since Monday and Tuesday conflict with Ruby on Rails, all I can offer
is Wednesday.

Does that work for you?

-Michael

[Michael Schidlowsky]

I lied. Wed is the day we're doing the code reviews in Evan's class.

Unfortunately, I'm stuck. If you guys can still do today, that works
for me. Otherwise all I have available is a remote meeting from
California (but not on the 18th... we'd have to work out a time). Or
an in-person meeting when I get back.

-Michael

[Michael L. Marcus]

As I mentioned, we don't have anything cohesive to show today, so I
don't think an in-person meeting makes sense. However, we have made
some good progress, so we would still like to have the conference call
this afternoon to discuss our design and next steps. The code review
might also be a good chance to discuss some of the technical points as
well.

Please send us some specific dates and times that would work for you
over the next few weeks, and I will coordinate with the team to
reschedule the meeting.

Thanks,
Mike

On Fri, Apr 11, 2008 at 10:27 AM, Michael Schidlowsky

[Evan Korth]

Is it too much for us to do the second transition meeting after the code
review session? I'd spring for pizza.

e.

[Michael L. Marcus]

We agree that a short demo/discussion following the code review is a
great idea. Especially if there's pizza.

[Ankit Kiritkumar Kamdar]

yes, I think we should be good by Wednesday.

Ankit Kamdar
Master of Science in Information Systems.
New York University/Stern School of Business.