itengtools wrote:

I created a project based on Scrum. It created a Release and two
Sprints. There is a period where you are gathering the info for
Product Backlog, stories, etc (Sprint Planning). You may have
"tasks" that need to be assinged to the different groups
due by the end of Planning.

How are you all recording this?

Do you mean by recording the time it took to break up stories into tasks
or how to do it, e.g how to to create new child tasks etc?


--
Cheers, Johannes
Agile Planning Team

itengtools wrote:

zrlrkewrote:

Do you mean by recording the time it took to break up stories into
tasks
or how to do it, e.g how to to create new child tasks etc?


--
Cheers, Johannes
Agile Planning Team

Thanks for your response. Again, I'm new to this. My question is about
the "Planning" stage for a project that is the built from
scratch. When you create a Scrum project, it creates a Release 1.0
with the current date, and a Sprint 1.0 with the current date.
(Sprint 2.0 etc...).

So my question is, the time spent with the customer, team, etc coming
up with the design of the system. We are asking questions and
assigning action items to the business and we are creating action
items to set up a test environment. Where in Scrum is this delegated?


Or should it be tracked at all?

Scrum does give strict advise on how to track the time spent, but there
are certain meeting types and outcomes. At the beginning of a sprint a
sprint planning meeting is held. This is to break up stories from you
product backlog into implementation tasks. The result is a sprint
backlog (a plan containing all items for the current sprint). However,
this requires a product backlog which is a prioritized list stories that
should be implemented in the release/product. A product backlog is
usually created in the beginning of the project but may change over time.

Coming back to your question. IMO track as much as possible in work
items, esp. design decisions (that is development work too) and
infrastructure work (test environment) but also meetings.


--
Cheers, Johannes
Agile Planning Team