Back to Forum

REGARDING MILESTONE PAYMENTS FOR AGILE FP PROJECT

Last post 06:23 pm August 29, 2016 by Timothy Baffa
1 reply
Suresh Vipperla
08:22 pm August 28, 2016

I have handled few projects using Waterfall and V models. As per initial agreement, the payment to be done by customer at the end of every phase i.e after completion of Requirements analysis (SRS), Design, Development, SIT, UAT (Acceptance test) and Deployment.

My question is ... how to define these payment milestones for Agile FP projects. Is it based on the total number of sprints... ie... if I have total 10 sprints, can I ask customer to pay 4 equal installments (each payment after completion 2-3 sprints).

What is the industry best practice. I have to decide asap.. can anyone please quickly answer...

Timothy Baffa
06:23 pm August 29, 2016

Suresh,

It seems your customer was originally paying installments that were tied to waterfall phases but not tied to delivery of value.

It seems this is a good opportunity to educate the customer around the benefits of an Agile approach, and paying for actual value delivered.

That being said, I can make an assumption that there is a list of functionality tied to the fixed-price bid. If so, then perhaps associate customer payment with delivered functionality? I would not necessarily tie customer payments to the # of sprints completed, since there is no guarantee that we know the # of sprints required, or that the completed sprints delivered the functionality identified.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.