[almighty] Planning preparation and task breakdown template for next sprint

[Michael Kleinhenz]

Hi all,

we're having the next planning next week. In the last Grooming, we
have assigned owners to the stories most likely being in the next
sprint. Owners (and everyone else), please remember doing the
preparation work for the planning meetings. In detail, this means:

Prior to SP1:
 - make sure you (story owner) have a full understanding of the story
and the context.
 - make sure the story represents a consensus in the team and the team
has an understanding of
   the story content.
 - the owner and a team should already have thought about the effort
estimation for the story.

-> the goal here is to minimize the discussions and time needed in the
SP1. We should focus on
    estimation and acceptance there! So we need to make sure everyone
is on the same page
    on the content of the stories before the meeting.

Prior to SP2:
 - prepare a suggested task list for your owned story. Please use this document:

  https://docs.google.com/document/d/1-n63MfvNfQA09tVoqIIJ7Q8CyWeXOlFjxTWGbmFdk9c/edit#

-> Goal here is to have something as a baseline that we can work on in th SP2

After SP2:
 - commit the results of the SP2 into GitHub by adding the new tasks
as issues and linking
   them into the connected stories.
 - be prepared for questions regarding the content of the story from the team.
 - work with the team to track the progress on the story to make sure
we get it completed
   at the end of the sprint.

As always, comments welcome :-)

-- Michael

-- 
Michael Kleinhenz
Principal Software Engineer

Red Hat Deutschland GmbH
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany

RED HAT | TRIED. TESTED. TRUSTED.
Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht München,
HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham,
Michael O'Neill