[almighty] Reminder: Planning on Tue/Wed

[Michael Kleinhenz]

Yes, but after SP2. The intention of the suggested task list is to
speed up SP2. The whole team has to work on the task breakdown in SP2
to come to a final task breakdown that can be then put into issues on
GitHub. :-)

On Mon, Nov 28, 2016 at 3:27 PM, Joshua Wilson <jowilson at redhat.com> wrote:
> Michael,
>
> I thought the intention of creating the tasks was to have the story owners
> create them in github so that when we were ready to work the story they
> would be there. This is done to speed up the planning cycle.
>
> On Mon, Nov 28, 2016 at 8:59 AM, Michael Kleinhenz <kleinhenz at redhat.com>
> wrote:
>>
>> And here's the task planning document. Reminder: please start the task
>> planning as soon as after SP1. Not earlier :-)
>>
>>
>> https://docs.google.com/document/d/1-n63MfvNfQA09tVoqIIJ7Q8CyWeXOlFjxTWGbmFdk9c/edit
>>
>> Thanks,
>> Michael
>>
>> On Mon, Nov 28, 2016 at 11:09 AM, Michael Kleinhenz
>> <kleinhenz at redhat.com> wrote:
>> > Quick clarification: please do not add stories or tasks to the Sprint
>> > 124 milestone yet. We will do that on or after SP1.
>> >
>> > On the suggested tasks that are provided by story owners for Sprint
>> > 124: please do not create GitHub tasks for your suggestions. We will
>> > provide a goc for working on the tasks in the SP2 later. And please
>> > wait until after SP1 tomorrow to work on the list as we don't know yet
>> > which stories get accepted into the sprint.
>> >
>> > -- Michael
>> >
>> > On Fri, Nov 25, 2016 at 12:01 PM, Michael Kleinhenz
>> > <kleinhenz at redhat.com> wrote:
>> >> Hi Story Owners,
>> >>
>> >> just a quick reminder that the next plannings are due next week.
>> >> Please review your owned stories and start a discussion on possibly
>> >> open topics. The goal is that discussions on the content of the
>> >> stories are done before SP1, so that we can focus on estimation and
>> >> acceptance in SP1.
>> >>
>> >> Thanks,
>> >> 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
>> >
>> >
>> >
>> > --
>> > 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
>>
>>
>>
>> --
>> 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
>>
>> _______________________________________________
>> almighty-public mailing list
>> almighty-public at redhat.com
>> https://www.redhat.com/mailman/listinfo/almighty-public
>
>



-- 
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