When the client has bought into Agile – is billing more likely to happen on hourly rates rather than predicted fixed costs? I know it depends but, from what I can see, agile allows you to discover as part of development and, if some cool opportunity comes up, then how is that tranlsated to the client and costed?

Thanks for your thoughts – as you see I’m interested in agile (none of my clients would have heard of it though!) – especiallly for the bigger, bespoke development projects. I like avoiding the the all in specification stage but only if hours don’t go out of control and world delivered greatly out weighs monies billed.

@joel_hughes

Thanks for the questions!

When we’re working with a client who’s used Agile before, or committed to trying it for the first time, it works well.

For clients who are new to Agile, we talk them through the process, provide introductory material that explains Agile terms, tools and processes, and lend them books.

We find that once you’ve built a good long-term relationship with a client you can start introducing the idea of working in an Agile way. And even on projects that are being run using traditional project management methodologies, internally we continue to use Agile tools and processes to manage our own work.

I guess that, like I said above, it’s all in the communication!

– Courtney

Thanks

@joel_hughes