SIGIA-L Mail Archives: RE: Re: SIGIA-L: Reasonable weekly co
RE: Re: SIGIA-L: Reasonable weekly commitments and conditions for consulting (long, but thought-provoking)
From: Paulssen, Natasja (fin) (natasja.paulssen_at_ordina.nl)
Date: Wed Sep 05 2001 - 03:37:18 EDT
I had approximately the same problem with a client once, where development
tried to elope with the project. I managed to be appointed 'conceptual
linking pin' responsible for translation of technical stuff into something
the stakeholders could still understand (and something the projectmanager
couldn't do!). I worked at the premises of the stakeholders and went to
meetings with development 3 times a week.
Best regard, Natasja Paulssen
> -----Oorspronkelijk bericht-----
> Van: David R. Austen [mailto:dausten_at_hoosier.net]
> Verzonden: dinsdag 4 september 2001 17:42
> Aan: christina
> CC: sigia-l_at_asis.org
> Onderwerp: Re: SIGIA-L: Reasonable weekly commitments and
> for consulting (long, but thought-provoking)
> Hello christina,
> Tuesday, September 04, 2001, 10:39:58 AM, you wrote:
> c> Your client sounds like a project manager to me--
> c> some project managers can get the big picture, sadly many
> cannot and focus on the two pieces in their
> c> power:budget and timeline. I suspect there is a power
> behind this dictator's
> c> throne.
> I am afraid you have hit the bullseye. He has instructed us not to
> have discussions with the stakeholders at the big picture
> level (progress on
> project) but only at the "component level" of the project. Familiar
> to you?
> c> You need access to it. There a number of ways to do this, including
> c> worksessions where you involve the stakeholders in the
> design process
> c> (personas and scenarios are especially good for this in my
> In this, the stakeholders will be able to see the importance of
> working with an AI who understands the integrity of the process,
> what will make it a success, or not. I think the project manager, on
> the other hand, will especially emphasize his ability to "ride herd"
> over developers (of all sorts.)
> c> Work with this person/persons to define a features list
> you can accomplish
> c> in the timeline, partially driven by your user
> requirements analysis.
> Yes, I absolutely agree.
> c> I think getting access to key stakeholders is one of the
> most common
> c> problems freelancers and agencies face. I'd love to hear
> other folk's
> c> strategies for getting these people involved or even just
> I have that access now, and am concerned that it does not slip away.
> He is moving me away from the stakeholders premises to his own
> premises, implying that the stakeholders will interfere with my work
> as an AI. But I believe it is more of a question of the control (and
> credit) that he wants to enhance.
> I feel very uneasy about the symbolism in moving me. I do understand
> the advantages of (eventually) needing to work hand-in-glove with the
> development and content preparation team. But those days are weeks, if
> not months away.
> Some feedback on this last part would be especially helpful.
> Best regards,
> David mailto:dausten_at_hoosier.net
This archive was generated by hypermail 2.1.2
: Sun Nov 23 2003 - 22:54:48 EST