Re: [scrumdevelopment] Re: Company Standards
- Hello, woynam. On Tuesday, July 1, 2008, at 11:03:51 AM, you
> You're putting the cart before the horse. You have to firstLots of things work but are not ideal. We can't prove that they
> demonstrate that the existing stuff won't work. You simply can't guess
> that it won't work. You have to prove that it won't work. You know,
> the empirical thing? Do. Measure. Adjust.
don't work. It is sufficient to suspect that one has a better idea
and to explore it.
It is not because things are difficult that we do not dare,
it is because we do not dare that they are difficult. --Seneca
- On Fri, Jun 27, 2008 at 11:36 PM, Emiliano Heyns <Emiliano.Heyns@...> wrote:On Fri, Jun 27, 2008 at 4:42 PM, Ilja Preuss <it@...> wrote:Emiliano Heyns wrote:How visible is that progress? How visible is how much needs still to be
> Do I want them to behave differently... that is a very good question. I
> think (easy to say) I would be OK with a wide variety of behaviors as
> long as we're showing noticeable progress towards our projects' goal.
done to reach that goal? Is this reflected in some kind of burn chart
that the team members believe in?
I'm beginning to doubt this. We have something like this, but I wonder whether the value of the milestones is adequately explained, which could certainly be an issue for the new member. If not, it could explain a thing or two.
I've been reading Jean Tabaka's book; I forgot who recommended it to me, but here's a heart-felt thank you to whoever did. I've found "a thing or two" that I should have handled very, very differently. So my apologies to this group, after the apologies already rendered to my team. We're not at the performing stage yet, but in a lot better shape than we were.