RE: Re: Sticking point

Dale,

> > In a shrinkwrap environment, there's generally a requirement that
> > the software run when installed on a newly set-up system with only
> > certain things on it. There's generally also a requirement for an
> > install program to do that setup.
> 
> Yes, eventually.  This iteration?

Maybe. If it's on the plan.
 
> > So at least in that environment, I'm for creating the CD and running
> > the install as soon as it's available... and I think it's better to
> > have it available pretty early in the process.
> 
> There's generally also a requirement for installation guides and user
> guides.  Are you for creating those at the earliest possible moment? 
> If not, what leads you to treat them differently from the install
> program and CD?

I'm doing extreme programming. The install is programming. If I were
charged with getting the manuals written, I might schedule them 
earlier than is traditional as well. That's how I am. :-)
 
> > This is similar in concept to quickly developing a version of the
> > entire system that runs from beginning to end, but without some of
> > the detailed featurs. The installation process is also part of the
> > user experience and it really s*cks to get to the "end"  and find
> > out you don't have a way to install.
> 
> Right.  So you offer that possibility to the Customer as soon as you
> think of it, and let the customer write a story and prioritize it. 
> What makes install different from any other story?

It's not... it's just something that customers typically forget to
write a story for. So they need prompting. Generally, they realize
that a set of features that are only available on my machine don't
make for a release.

Bear in mind that I'm thinking of an environment where we need to
be ready to release on short notice - for sales conferences, etc.
I don't deny that this is a customer decision, but it's often one
that has been made in the environment before we even start the
project - it's assumed. My job is to make it explicit, confirm 
it and carry it out.

> > In an IT environment, I'd expect some similar criterion to be
> > applied. If you plan to distribute by handing out CDs, then exercise
> > that. If it's web-based distribution, then get it set up early and
> > test it.
> 
> Why early?  Why not wait until the Customer prioritizes it into the
> next iteration?

As in the shrinkwrap case, it depends on Customer priorities. But left
to their own devices, Customers often assume that distribution is "free"

Charlie Poole
[email protected]
www.pooleconsulting.com
www.charliepoole.org




------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/CBxunD/vN2EAA/xGHJAA/NhFolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
extremecustomering-unsubscribe-hHKSG33TihhbjbujkaE4pw@public.gmane.org

 

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