Loading ...
Sorry, an error occurred while loading the content.

Re: How much deep should the team achieve to understanding about product backlog items in the beginning ?

Expand Messages
  • M.Jalilnejad
    Nice answer Steve, You enlighted me. That s why I like this group After reading the answer, I think my question is wastful. Yes know the experience tells us
    Message 1 of 16 , Mar 26, 2011
    • 0 Attachment
      Nice answer Steve,
      You enlighted me. That's why I like this group
      After reading the answer, I think my question is wastful.
      Yes know the experience tells us how much is enough.

      Regards,
      Jalilnejad

      On 3/24/11, Stephen Palmer <stephen.palmer@...> wrote:
      > The old FDD community-site has a couple of threads on fixed price and
      > FDD/agile that might help:
      >
      > http://www.featuredrivendevelopment.com/node/612
      >
      > http://www.featuredrivendevelopment.com/node/527
      >
      > As to how much to do upfront - my glib answer is always:
      >
      > 'just enough design initially' or 'Jedi' for short. How much is 'just
      > enough', well that takes judgement based on experience. After all, one does
      > not become a Jedi Master overnight :-)
      >
      > Seriously however, I do not think there are any concrete rules here. Much of
      > the answer depends on the make-up of the team, the type of application being
      > created, familiarity with technologies and technical architecture that will
      > be used, and the complexity of the problem domain, etc.
      >
      > I guess one generally accepted rule of thumb would be to stop doing a piece
      > of upfront work as soon as you recognise it is not adding any further
      > significant value. Another overriding rule of thumb is that the team does
      > need to be confident that it knows enough to be able to complete the work
      > they commit to for the first Sprint.
      >
      > Steve
      >
      > Stephen R. Palmer
      > Certified Scrum Practitioner, FDD Associate, Coad-Certified Mentor
      > http://www.featuredrivendevelopment.com, http://www.nebulon.com,
      > http://www.step-10.com, http://www.twitter.com/stephenrpalmer
      >
      >
      > On 23 Mar 2011, at 19:01, M.Jalilnejad wrote:
      >
      >>
      >> thank you all
      >> The example about Surgeons was good. a surgeon should know what he/she
      >> would do beforehand and uses medical images an experiments to know more,
      >> but however it might be some unknown issues that may occur after starting
      >> the surgery, then his/her expertise comes to importance. I mean that some
      >> uncertainty may (or inevitably ) remain and its not bad.
      >>
      >> I agree with the "balance" André mentioned and the highlight that Steve
      >> quoted. the question is how to know the anticipation is enough ?
      >> My other question is still remained unanswered, "What about fixed-price
      >> contracts ?"
      >>
      >> Regards
      >> Jalilnejad,
      >>
      >>
      >>
      >
      >
      >
      > ------------------------------------
      >
      > To Post a message, send it to: scrumdevelopment@...
      > To Unsubscribe, send a blank message to:
      > scrumdevelopment-unsubscribe@...! Groups Links
      >
      >
      >
      >

      --
      Sent from my mobile device
    Your message has been successfully submitted and would be delivered to recipients shortly.