headers
Dale Emery | 1 Jun 2009 19:11
Favicon
Gravatar

Re: ANN: Certified Scrum for the unemployed

Hi Tobias,

If you still have open slots for the San Francisco class on June 16-17, I
would like to be considered.

I'm an independent consultant, and have been for years. Some years are good;
some years suck. My last 18 months have been dreadful, and I've used up most
of my financial reserve.

Am I an appropriate candidate for the class? If so, please count me in.

Dale

On Sat, May 30, 2009 at 8:08 AM, Tobias Mayer <tobias.mayer <at> yahoo.com>wrote:

>
> Certified Scrum Master training for those undergoing financial hardship
>
> WelfareCSM <http://welfareCSM.com>  uses an open pricing model where
> participants pay only what they can afford.  The courses are targeted
> towards two specific groups:
>
> 1. Software people currently unemployed, in low-paid jobs or threatened
> with lay-off. *
> 2. Non-software people.
>
> * Additionally, the course is offered on a non-priority basis to those
> whose employers refuse to pay for training.
>
> Currently three courses are planned.
(Continue reading)

Permalink | Reply | 0 comments |
headers
geoffrey_slinker | 2 Jun 2009 19:29
Picon
Favicon

Semler MIT Video

http://mitworld.mit.edu/video/308/

About the 28 minute mark is a very "agile" statement.

Geoff

http://home.comcast.net/~gslinker/maverick/Maverick.html
http://home.comcast.net/~gslinker/agile.html
Permalink | Reply | 3 comments |
headers
Ron Jeffries | 3 Jun 2009 01:32
Favicon

Re: Semler MIT Video

Hello, geoffrey_slinker.  On Tuesday, June 2, 2009, at 1:29:07 PM,
you wrote:

> http://mitworld.mit.edu/video/308/

> About the 28 minute mark is a very "agile" statement.

Save us all a half hour?

Ron Jeffries
www.XProgramming.com
www.xprogramming.com/blog
Curiosity is more powerful than skepticism.
Permalink | Reply | 2 comments |
headers
Michael Dubakov | 3 Jun 2009 19:34
Picon
Favicon

Pair Programming problem: 3 pros 2 cons. What to do?

We have 5-person development team and tried pair programming 3 months ago. 3 developers like it, while 2
other don't (and quite aggressively vote against PP). These 2 people who do not like PP are very
experienced developers. Obviously we don't want to fire them.

What will you do in this case?
Permalink | Reply | 51 comments |
headers
geoffrey_slinker | 3 Jun 2009 18:13
Picon
Favicon

Re: Semler MIT Video

I will include the text here and you could also just drag the position indicator of the video control.

At about 28:25:

--------------
(Ricard Semler speaking about Semco)

We don't know where we are going and we would rather not pretend that we do know...

We put together a one year budget and we found that all the good things were going to happen in the second half
so we said take out the second half and tell me what you would do if you only have six months. And that changes
dramatically how people see things. And now they have to have a rolling rationale of the numbers that
people can really talk to... talking on specific numbers for more than six months is improbable. I want you
to think about the future a heck of a lot but don't right it down please because if you write it down we have to
follow it (he spoke earlier about how people like to follow things)... all of our meetings are on a
voluntary basis...

--------------

The entire video is worth the watch. I have searched the web for a transcript and can not find one but surely
one exists.

Geoff
Permalink | Reply | 1 comment |
headers
Phlip | 3 Jun 2009 21:11
Picon
Gravatar

Re: Pair Programming problem: 3 pros 2 cons. What to do?

Michael Dubakov wrote:

> We have 5-person development team and tried pair programming 3 months ago. 3 developers like it, while 2
other don't (and quite aggressively vote against PP). These 2 people who do not like PP are very
experienced developers. Obviously we don't want to fire them.
> 
> What will you do in this case? 

Let the 3 take turns pairing promiscuously with each other, and track who wrote 
what bug for a while.

--

-- 
   Phlip
Permalink | Reply | 0 comments |
headers
S M Kripanidhi | 3 Jun 2009 15:03

Need Help and Support in my R&D Efforts

I have been a core XPiete for over a decade now and have been a purist at that.  I have been trying my best to
propogate the Values and Principles of Agile in India  since 2001 to the best of my ability.

Over the last couple of years, I have been very frustrated in the way organizations are understanding and
implementing the Values and Principles of Agile in their organizations upside down and discrediting
Agile for it.  

After a detailed introspection with many of my such customers,  I found that we may have to first
empethatically understand the constraints and limitations in large traditional organizations, 
within which they are trying to embrace Agile.  Most of the times these  organizations are unable to create
and sustain an Agile Culture that is so desparately needed for Agile to survive.

Many Agile Evangelists have identified these problems and have called it "ScrumBut" (Ken Schwaber), 
"Flaccid Scrum" (Martin Fowler), "Waterscrum" and sometimes "ScrummerFall"
(http://blogs.msdn.com/nickmalik/archive/2007/06/04/waterscrum-vs-scrummerfall.aspx ). 
People in these organizations heart of heart feel hypocritical and ashamed too,  seeing Agile Practices
being implemented upside down in their organizations.   But none of the Agile Evangelists have come
forward to solve this problem in a more practical and feasible manner for these organizations and have
left them alone writhing in pain.

I am trying to research and explore if we could find a better way to address these pain areas in such large
software product development organizations, who in their true earnest, wish to improve but do not find
Agile working for them, within their own cultural limitations and constraints.   What they need to do to
improve,  may not be core Agile,  but something similar that works for them,  in their contexts.

I am aspiring to build a new set of Practices or a "Practice Framework"  for such large traditional software
product organizations which they can reference and use easily and conveniently accross their entities,
within their own traditional organizational environment and hierachial culture and still realize
value in terms of being able to improve their business efficiency and effectiveness.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ola Ellnestam | 3 Jun 2009 21:29
Picon

Re: Pair Programming problem: 3 pros 2 cons. What to do?

Hi Michael,

As a developer I would continue pairing with the ones that likes it. As
questions, bugs or other chances pops up, I would pair for a while with
the ones that doesn't like it. Maybe they can cope with that and maybe
that will get them to get used to pairing. Even like it after a while.

As a boss I would make sure that there are no difficulties to pair. Buy
large(er) screens, remove cords from floor, buy larger desks, tear down
walls. Do basically anything that eases pairing. Just to make sure
everybody knows that I want them to pair.

Also, I'd be explicit about /why/ I want pairing to happen. To spread
knowledge, risks etc etc.

Good luck.

Cheers,
Ola

Michael Dubakov wrote:
> We have 5-person development team and tried pair programming 3 months ago. 3 developers like it, while 2
other don't (and quite aggressively vote against PP). These 2 people who do not like PP are very
experienced developers. Obviously we don't want to fire them.
> 
> What will you do in this case? 
> 
> 
> 
> ------------------------------------
(Continue reading)

Permalink | Reply | 2 comments |
headers
Phlip | 3 Jun 2009 23:57
Picon
Gravatar

Re: Pair Programming problem: 3 pros 2 cons. What to do?

Ola Ellnestam wrote:

> As a developer I would continue pairing with the ones that likes it. As
> questions, bugs or other chances pops up, I would pair for a while with
> the ones that doesn't like it. Maybe they can cope with that and maybe
> that will get them to get used to pairing. Even like it after a while.

Has the OP's crew been following any of these wise suggestions?

   http://c2.com/cgi/wiki?HowToPissOffYourPair

They tend to make the value of pairing more obvious...

--

-- 
   Phlip
Permalink | Reply | 1 comment |
headers
banshee858 | 4 Jun 2009 00:00
Picon
Favicon

Re: Pair Programming problem: 3 pros 2 cons. What to do?

>
> We have 5-person development team and tried pair programming 3 months ago. 3 
> developers like it, while 2 other don't (and quite aggressively vote against PP). These 2 
> people who do not like PP are very experienced developers. Obviously we don't want to fire
> them.
> 
> What will you do in this case?
>
How did you frame your decision making process?  Was it majority vote?  Consensus?  Leader decides with
input?  Or something else?  I ask because depending on what were the ground rules for making decisions
influences how you can take your next step.

Carlton
Permalink | Reply | 16 comments |

Gmane