[consulting] Estimation-Blowout case-studies wanted

[Gerhard Killesreiter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Susan Stewart schrieb:
> Ashraf Amayreh wrote:
>>
>> Has anyone faced this problem? How do you begin to tackle it? What do
>> you do when the client wants the design to come out from his side and
>> you know the deisnger will totally be someone unacquainted with Drupal?
>> And in some cases I faced, not acquainted with web development!
> <snip>
> 
> I wholeheartedly agree here.  It's easy enough to time project tasks
> and establish a baseline for how long common (and even uncommon)
> tasks will take.
> 
> However, when there's a module that will do X out of the box, but
> the theme suggests a major change in how that will be presented,
> there's a lot more work involved than there needs to be.
> 
> If we are developing the theme in-house, I know things will be in
> order for the easiest implementation.  When the design is coming
> from the client, or their marketing agency, that isn't a given.

IMO it is not only about themes, it is also about interaction design.
Some people have ideas about that that differ from how Drupal
implements certain things (say, user registration). If the client then
insists to implement the design given to hime by his designer (or
worse: _his_ client), then you end up with a looong hook_form_alter
function which unsets fields, adds callbacks, removes other callbacks,
etc. Sometimes I feel like writing your own registration would have
been better.

But I only know that at the end after many iterations of back and
forth...

Cheers,
	Gerhard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkmlXEcACgkQfg6TFvELooS4BgCgkwrTWzhETdEwPCCSqrb895mi
9RoAn2L3WtactFxblnbAOkZaLZvbm5hx
=Mrqm
-----END PGP SIGNATURE-----