If I may add a few personal observations to the stack...
* The first few retrospectives you have, are going to be fascinatingly
awkward. Particularly so for established teams.
I've seen this happen several times, and heard tales of many more
situations that fit the same pattern: If any of the part
On Mon, Dec 9, 2013 at 5:49 PM, Tomasz Finc wrote:
> And if we haven't given you enough info. You can find all the notes
> from the Mobile Apps team retrospectives on our team page
>
> https://www.mediawiki.org/wiki/Wikimedia_Apps/Team
>
>
Oo oo! And the mobile web team:
https://www.mediawiki.org
And if we haven't given you enough info. You can find all the notes
from the Mobile Apps team retrospectives on our team page
https://www.mediawiki.org/wiki/Wikimedia_Apps/Team
On Mon, Dec 9, 2013 at 4:43 PM, Arthur Richards wrote:
>
>
>
> On Mon, Dec 9, 2013 at 5:24 PM, Chris McMahon
> wrote:
On Mon, Dec 9, 2013 at 5:24 PM, Chris McMahon wrote:
>
> I'll suggest you do a retrospective for every sprint. These
> retrospectives should have three aspects:
>
> What went well: celebrate your successes, you deserve it.
> What did not go well: make a list of issues encountered during the last
I started a while back a wiki (
https://www.mediawiki.org/wiki/Analytics/ScrumRetrospective) explaining the
5 why's method if you want to dig deeper into a problem. The wiki contains
some useful references and examples.
D
On Mon, Dec 9, 2013 at 7:36 PM, Arthur Richards wrote:
>
> On Mon, Dec 9,
On Mon, Dec 9, 2013 at 4:47 PM, Steven Walling wrote:
> Hey all,
>
> So one of the pieces of feedback out of our Quarterly Review last week for
> the Growth team is that we should probably start doing retrospectives to
> improve our process.
>
> I understand the theory behind retrospectives as a p
On Mon, Dec 9, 2013 at 4:24 PM, Chris McMahon wrote:
> What went well: celebrate your successes, you deserve it.
> What did not go well: make a list of issues encountered during the last
> sprint
> What to improve: this is where it gets interesting...
At the beginning of the retrospective befor
I'll suggest you do a retrospective for every sprint. These retrospectives
should have three aspects:
What went well: celebrate your successes, you deserve it.
What did not go well: make a list of issues encountered during the last
sprint
What to improve: this is where it gets interesting...
T
On Mon, Dec 9, 2013 at 3:47 PM, Steven Walling wrote:
> My first question is when should I schedule our retrospectives? For context,
> Growth is in the tail end of our fifth sprint, and sprint planning/kickoff
> meetings happen on Wednesdays for us.
Apps do them every two iterations.
Whenever we
Hey all,
So one of the pieces of feedback out of our Quarterly Review last week for
the Growth team is that we should probably start doing retrospectives to
improve our process.
I understand the theory behind retrospectives as a product owner, but since
we don't have a scrum master, I wanted to a
> On Tue, 2013-12-03 at 22:24 -0500, Matthew Flaschen wrote:
> > On 11/26/2013 11:25 AM, Andre Klapper wrote:
> > > https://www.mediawiki.org/wiki/Bug_management/Bugzilla_Etiquette
> > Can you send this to Wikitech?
http://lists.wikimedia.org/pipermail/wikitech-l/2013-December/073462.html
andre
-
11 matches
Mail list logo
