On 13 March 2014 06:56, Dan Andreescu wrote:
> On Wed, Mar 12, 2014 at 4:42 PM, Oliver Keyes wrote:
The objection is pretty self-explanatory; agile is a philosophy that
dictates putting things we strongly suspect, or even know, to be actively
buggy, in front of users. When do
Arthur Richards, 13/03/2014 00:40:
While I've heard rumors and grumblings about users not being so excited
by some teams' embrace of agile practices, I haven't been a part of nor
seen any of those specific conversations. Can you (or anyone else) point
me to some of those conversations so I have m
>
> On Wed, Mar 12, 2014 at 4:42 PM, Oliver Keyes wrote:
>>>
>>> The objection is pretty self-explanatory; agile is a philosophy that
>>> dictates putting things we strongly suspect, or even know, to be actively
>>> buggy, in front of users. When doing so includes replacing or superseding
>>> core
On 12 March 2014 16:54, Arthur Richards wrote:
>
>
> On Wed, Mar 12, 2014 at 4:42 PM, Oliver Keyes wrote:
>>
>> The objection is pretty self-explanatory; agile is a philosophy that
>> dictates putting things we strongly suspect, or even know, to be actively
>> buggy, in front of users. When doing
On Wed, Mar 12, 2014 at 4:42 PM, Oliver Keyes wrote:
>
> The objection is pretty self-explanatory; agile is a philosophy that
> dictates putting things we strongly suspect, or even know, to be actively
> buggy, in front of users. When doing so includes replacing or superseding
> core functionality
On 12 March 2014 16:40, Arthur Richards wrote:
>
>
>
> On Tue, Mar 4, 2014 at 7:19 PM, Whatamidoing (WMF)/Sherry Snyder <
> ssny...@wikimedia.org> wrote:
>
>> Matt, I basically agree with you. The problem is that hundreds of our
>> "customers" do not. Erik said the other day, "2) We do have a h
On Tue, Mar 4, 2014 at 7:19 PM, Whatamidoing (WMF)/Sherry Snyder <
ssny...@wikimedia.org> wrote:
> Matt, I basically agree with you. The problem is that hundreds of our
> "customers" do not. Erik said the other day, "2) We do have a higher
> tolerance for breaking things". Do you know who "we"
Triggered by the comparison with banks, FWIW here some nostalgia (or rather
lack of): I worked at a large airline for several decades, their procedures are
very similar to large banks. Some pro's and con's of the old ways of doing
things:
I don't think we stabbed the user twice a year with a l
On Tue, Mar 4, 2014 at 7:52 PM, Whatamidoing (WMF)/Sherry Snyder
wrote:
> "Don't poke me at all", for most of them, means "do not ever release
> software that contains bugs that they will personally experience". For
> another subset, it means never making any UI changes. It's a thoroughtly
> unr
"Don't poke me at all", for most of them, means "do not ever release
software that contains bugs that they will personally experience". For
another subset, it means never making any UI changes. It's a thoroughtly
unrealistic position, but those are their real opinions.
If you want to reduce "mis
On 03/04/2014 09:19 PM, Whatamidoing (WMF)/Sherry Snyder wrote:
They're saying, "Stop poking me with a stick twice a
week". Agile proponents are saying, "Well, the only alternative is that
we stab you with a big knife twice a year". They are very loudly in
favor of "don't poke me at all".
If
On 03/03/2014 08:51 PM, Oliver Keyes wrote:
> So is the answer advisors, or just hiring
engineers for the teams that need them with a focus in the JDs and
interview processes on people with scrum experience willing to take up
being a scrum master as a primary duty?
The latter (hiring a combinat
Matt, I basically agree with you. The problem is that hundreds of our
"customers" do not. Erik said the other day, "2) We do have a higher
tolerance for breaking things". Do you know who "we" is in that sentence?
Hint: It's not our "customers".
A noisy segment of our customers either don't be
Forgot to reply all.
Matt Flaschen
On 03/03/2014 11:00 PM, Whatamidoing (WMF)/Sherry Snyder wrote:
(2) Did you all know that a significant proportion of our user
community is unhappy with the way that Agile affects them? "Release
early, release often" from the user's perspective means "have h
On 03/03/2014 11:00 PM, Whatamidoing (WMF)/Sherry Snyder wrote:
(2) Did you all know that a significant proportion of our user
community is unhappy with the way that Agile affects them? "Release
early, release often" from the user's perspective means "have horribly
and/or newly busted stuff scr
On Tue, Mar 4, 2014 at 2:45 PM, Arthur Richards wrote:
> Personally, I believe deeply, with great conviction, that we are in a
> *much* better place as a result of all of this than when I started at the
> WMF nearly 4 years ago. I think we have a long way to go, and indeed will
> have eternal room
PS Whoever comes up with a cogent tl;dr version of my most recent email
before I get around to it, I'll buy you dinner next time I see you.
On Tue, Mar 4, 2014 at 3:45 PM, Arthur Richards wrote:
> Thank you everyone for your feedback - on the list, on the talk page, and
> personally. There is *a
Thank you everyone for your feedback - on the list, on the talk page, and
personally. There is *a lot* here, so I am going to try and respond to as
much of it as I can in one fell swoop. If you read all the way to the end,
I'll owe you a beer (or equivalent).
Note that I am going to use the word '
On Tue, Mar 4, 2014 at 12:46 AM, Erik Moeller wrote:
>
> In any case, the WMF engineering@ list covers the entire
> engineering/product department and has generally been an inclusive
> place where non-technical participation is welcome. We also created
> the teampractices@ list (public & open) as
On Mon, Mar 3, 2014 at 9:24 PM, Ryan Lane wrote:
> This is an engineering topic on an engineering list. That seemed like a good
> place to stop that message.
Hey Ryan,
as Roan noted, it's odd to characterize this as an "engineering
topic". Perhaps that makes sense from the ops/infrastructure
eng
On Mon, Mar 3, 2014 at 9:53 PM, Matthew Walker wrote:
> I'm a bit confused on the role of the 'product manager' and 'scrummaster'...
> to me they're mostly the same thing. It seems like you're implying that only
> engineers can be scrummasters? (Basically, what does a scrummaster in your
> world d
On Mon, Mar 3, 2014 at 8:00 PM, Whatamidoing (WMF)/Sherry Snyder
wrote:
> (2) Did you all know that a significant proportion of our user community is
> unhappy with the way that Agile affects them? "Release early, release
> often" from the user's perspective means "have horribly and/or newly bu
I'm a bit confused on the role of the 'product manager' and
'scrummaster'... to me they're mostly the same thing. It seems like you're
implying that only engineers can be scrummasters? (Basically, what does a
scrummaster in your world do?)
The PM we just hired in fundraising is starting to massagi
On Mar 3, 2014 9:24 PM, "Ryan Lane" wrote:
>
> On Mon, Mar 3, 2014 at 3:59 PM, Oliver Keyes wrote:
>>
>> So, I'm not an Engineer, I just work here
>
>
> [snip]
>
> This is an engineering topic on an engineering list. That seemed like a
good place to stop that message.
>
Right, input from non-engi
On Mon, Mar 3, 2014 at 3:59 PM, Oliver Keyes wrote:
> So, I'm not an Engineer, I just work here
>
[snip]
This is an engineering topic on an engineering list. That seemed like a
good place to stop that message.
- Ryan
___
teampractices mailing list
te
(1) Is this actually a request for five full-time-equivalent employees,
people who will do nothing else except this? "Staffed by three people"
does not necessarily mean "staffed by three full-time employees".
(2) Did you all know that a significant proportion of our user community
is unhappy wi
On 3 March 2014 17:12, Arthur Richards wrote:
>
> On Mon, Mar 3, 2014 at 4:59 PM, Oliver Keyes wrote:
>
>> So, I'm not an Engineer, I just work here, but my first thought is: you
>> want to *start* with 3 staff, and scale it up to 5 within the same
>> budget year, for this?
>>
>> The justificati
On Mon, Mar 3, 2014 at 4:59 PM, Oliver Keyes wrote:
> So, I'm not an Engineer, I just work here, but my first thought is: you
> want to *start* with 3 staff, and scale it up to 5 within the same budget
> year, for this?
>
> The justification is a pretty good justification for having *some*resourc
I'd certainly make use of an available scrummaster. Right now we are just
getting started with Agile, and because of the small size of our team, I'm
taking on both the product owner and scrummaster role. I know this isn't
ideal due to the nature of those two roles, so I'd really like to be able
t
So, I'm not an Engineer, I just work here, but my first thought is: you
want to *start* with 3 staff, and scale it up to 5 within the same budget
year, for this?
The justification is a pretty good justification for having
*some*resources; teams are finding your knowledge and mentorship
useful, you
30 matches
Mail list logo
