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

Re: [scrumdevelopment] question about SCRUM activity sequencing

Expand Messages
  • Doug McQuilken
    Henry,   I am also relatively new to scrum & this is the best process description I have seen in all my readings as it is truly elegant in its simplicity :-)
    Message 1 of 2 , Sep 10, 2008
    • 0 Attachment
      Henry,
       
      I am also relatively new to scrum & this is the best process description I have seen in all my readings as it is truly elegant in its simplicity :-)
       
      Regards,
      Doug
       
       
      Ps - usually the review/demo is distinct from a (team) restrospective


      --- On Wed, 9/10/08, Henry Herz <HLH88@...> wrote:
      From: Henry Herz <HLH88@...>
      Subject: [scrumdevelopment] question about SCRUM activity sequencing
      To: scrumdevelopment@yahoogroups.com
      Date: Wednesday, September 10, 2008, 1:01 PM

      Hi all
      I am relatively new to SCRUM, and want to make sure that I understand
      the correct order of SCRUM project activities & artifacts. I have
      given it my best shot below. I am particularly interested in
      understanding the process for the INITIAL creation of product
      backlog. I would appreciate any feedback to ensure I have things
      sequenced correctly chronologically. Thank you.

      Project Initiation
      - Define team, schedule, sprint length, # of sprints, etc.
      - Create Project Overview document, including:
      -- Product vision
      -- Product high-level features (but not a true backlog yet, no
      user stories)
      -- Release roadmap (release dates for high-level features)
      - Define high-level architecture

      Release Planning Meetings (multiple per project)
      - Create User Stories, from which are created…
      - Feature Estimates (in story points), from which are created…
      - Prioritized Product Backlog (since priority could be affected by
      effort required), from which is created…
      - Release Plan (list of user stories to be in release)

      Sprint Planning Meetings (multiple per release)
      - Task Estimates (in hours)
      - Create Sprint Backlog (list of user stories to be in sprint)

      Sprints
      - Conduct daily standup meetings
      -- Team members assign tasks to themselves
      -- Track tasks in the categories: to do, in progress, done,
      accepted (for those in progress, note hours remaining)
      -- Update Sprint burndown chart
      - Do the work

      Sprint Review Meetings
      - Obtain user acceptance
      - Update velocity log
      - Update Product burndown chart
      - Document lessons learned

    Your message has been successfully submitted and would be delivered to recipients shortly.