Re: Sprint mechanics
- btw: at least we got our design notes down to digital photos of
whiteboards, scanned handwriting, and graphic scribble capture (new
high-tech term) in Word, using a cool mouse-pen from Finger systems.
--- In email@example.com, "Deb" <deborah@h...> wrote:
> --- In firstname.lastname@example.org, Ron Jeffries
> <ronjeffries@X...> wrote:
> > On Wednesday, January 26, 2005, at 9:21:27 AM, Deb wrote:
> > > (Yes, we have filed notes. It's not an XP shop).
> > Why are these two independent ideas on one line
> When I worked on a Java team with XP practices, some of our doc
> from the code, as Together/J diagrams, Javadoc, etc. If one needed
> particular sequence diagram, we could generate it quickly. We
> knew that such doc was up-to-date. We also used "metaphor" type
> that aged more gracefully than design notes. Non-XP shops also use
> these practices, of course, perhaps this is what you are referring
> to. My bad.
> Our shop wasn't using all the Agile best practices, inside our
> Sprints. But you've got to start somewhere! So we had a certain
> amount of (quickly obsolete) papertrail documentation, which had to
> suffice. My preference would have been to throw many of them away
> the end of a Sprint, but we weren't there yet.
> > and in parens? :)
> An aside, off the main topic of my post: because on this scrum
> sometimes, people assume that Scrum = XP, whereas Scrum+XP is only
> one (good) option. Just thought I'd nip that one in the bud to keep
> traffic down. I see it didn't work, anyway :-)
> > Ron Jeffries
> > www.XProgramming.com
> > Hope is not a strategy. -- Michael Henos