RE: Do C-Level managers, and business drivers really need to know about XP?

I wouldn't have thought XP was meant to have a lot of visibility to upper 
management. "Agility" focuses on developers and their immediate customers 
and it enables a lot of good things at those levels. Upper management 
dealing with annual budgets is likely to approve a proposal from a business 
manager to reduce costs by implementing a new system to do some process 
with healthy ROI and not worry much about how it's done.

They might be interested in process when we have more satisfied customers. 
Or we deliver better, faster, cheaper. Or they change high-level priorities 
and truncate the project and discover we delivered value equal to the 
spend-to-date. It will be a good day when they stop by to ask "Hey, how did 
you do that? Can you do it again?"

At 10:52 PM 1/26/03 -0500, you wrote:

>Scott,
>
>What happens, though, when those upper managers are asking for budget
>figures based on what's going to be delivered over the period of a year?  I
>suppose many organizations couldn't provide an accurate figure regardless of
>methodology, but a group using XP at least would answer, "Well that
>depends."  That isn't something that would have "the suits" opening their
>pockets, so I feel that at least a little education is required.
>
>Dave Rooney
>Mayford Technologies
>http://www.mayford.ca
>
>
> > -----Original Message-----
> > From: Scott Worley <[email protected]>
> > [mailto:[email protected]]
> > Sent: Sunday, January 26, 2003 10:44 PM
> > To: [email protected]
> > Subject: [xpAdoption] Do C-Level managers, and business drivers really
> > need to know about XP?
> >
> >
> > Hi all, a slightly diffrent tack of approach on the issue of XP
> > Adoption.
> >
> > Do the high level managers in a company need to know about Agile this
> > or XP that?
> >
> > In my opinion (I am a C-Level Manager) NO, what they/we want is
> > results if its due to a new process that the dev team or indeed any
> > other team is using, thier team lead/PM should know about it, but
> > above that it is not necessary.  A PM can request resource from
> > higher management and in most cases the justification is of the
> > standard Time/Cost/Resource type. A PM should act as a consultant to
> > the teams they ENABLE and the management they provide a service for.
> >
> > I have worked at various levels in development over the past 10+
> > years, and in most cases the dev team I have been in, HAVE NOT TOLD
> > the PM what exact process they follow :) including myself.
> >
> > Normally the time spent trying to educate people on process, is time
> > we should have been coding, politics are fine when there is time.
> >
> > As a final note, I am not saying Senior management should not know
> > what is being done process wise, just not in a low level and somewhat
> > evangelistic way (btw: I am very evangelistic about agile process not
> > just in development)
> >
> > Scott Worley
> >  CTO, Speaker, Consultant, Trainer, ENABLER of Process.
> >
> >
> >
> > To unsubscribe from this group, send an email to:
> > [email protected]
> >
> >
> >
> > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
> >
> >
> >
>
>
>To unsubscribe from this group, send an email to:
>[email protected]
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/



To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/