Scrum - Responding to traditional RFPs
- by Todd Charron
Hi all,
I've seen many articles about how to put together Agile RFP's and
negotiating agile contracts, but how about if you're responding to a
more traditional RFP? Any advice on how to meet the requirements of the
RFP while still presenting an agile approach?
A lot of these traditional RFP's request specific technical
implementations, timelines, and costs, while also requesting exact
details about milestones and how the technical solutions will be
implemented.
While I'm sure in traditional waterfall it's normal to pretend that
these things are facts, it seems wrong to commit to something like this
if you're an agile organization just to get through the initial
screening process.
What methods have you used to respond to more traditional RFP's?
Here's a sample one grabbed from google,
http://www.investtoronto.ca/documents/rfp-web-development.pdf
Particularly,
"3. A detailed work plan outlining how they expect to achieve the four
deliverables
within the timeframe outlined. Plan for additional phases of
development."
and
"8. The detailed cost structure, including per diem rates for team
members, allocation
of hours between team members, expenses and other out of pocket
disbursements,
and a total upset price."
