esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hirsch, Richard" <>
Subject RE: Sprint 1 Results
Date Sat, 07 Feb 2009 06:05:45 GMT
Probably best to discuss it without recriminations via the mailing list. 
The main question is did we bite off more than we chew? 
Maybe we should focus on smaller sprints with fewer items and have a status check half way
through the sprint. Or we could use scrum "mails" via the mailing list once a week. This is
probably the best idea and would also closely mimic the culture of our scrum calls.
>It would be best to have some sort of sprint retrospective and planning ASAP so we increase
the momentum.
I agree. Siemens installation is now up and running with the very old Google-based war file
and the press release is also in its final stages which should mean more attention as well.


From: David Pollak []
Sent: Fri 2/6/2009 15:18
Subject: Re: Sprint 1 Results

On Fri, Feb 6, 2009 at 1:23 AM, Hirsch, Richard

> Hi,
> Our first sprint ends today and I'd like to know the status of the
> tasks:
> Here are the items that we planned and their status to the best of my
> knowledge.
> User Interface:
> *       General User Interface (UI) roadmap with order of goals and what
> needs to be accomplished
> *       Adequate description of User Interface architecture
> *       Creation of first sprint specification
> *       Partial implementation  (Web Interface)
> Server:
> *       Generic code clean-up   // Finished
> *       Unifying server calls (JSON-related) // Partially finished
> *       Support for Twitter API // Partially finished
> *       Document how compass can use other persistency types
> *       Merge Action branch into official trunk  // Finished
> *       Further work on java API (GetMessages) // Partially finished
> I'll be on vacation next week, but I suggest that meeting next week or
> the week after would be ideal.

It would be best to have some sort of sprint retrospective and planning ASAP
so we increase the momentum.

This sprint was not ideal from a commitments to deliverables perspective (I
am as guilty of this as anyone, so please to hear me casting blame far
beyond myself.)  I think it's important that we discuss the reasons for not
estimating correctly so we can get better at estimating in the future.

If we can't do a call on Monday or Tuesday, then I propose that we spent a
lot of time over the weekend discussing why we didn't make our milestones
and plan for the next iteration.

Sound reasonable?



> We should also start planning for the next sprint. Anyone have any
> suggestions on the things we should work on?
> If possible, I'd like to see groups on the server side.
> D.

Lift, the simply functional web framework <> 
Beginning Scala
Follow me:
Git some:

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message