There are situations where the client organization must follow a certain standard or rules, such as determining in advance the cost of the project (e.g. fixed price), the time frame, the documentation of the project, etc. How do both the client and the supplier (software houses) cope with such restrictions in agile development (e.g. SCRUM)?
In one project, measuring scope, time and cost in the initial stage is complex. A team needs to be very mature to estimate with great accuracy. Requirements change as the client validates the market with him. Agile (e.g. Scrum) contracts adopts scope and time flexible due to these changes. Only the monthly cost, with a dedicated team, is fixed. As always the team will focus on increasing client ROI, and the feedback loop is short (2-4 weeks), this relies on the team. Techniques such as integration and deploy continuous provide greater security for the client. And the client can terminate the contract so it finds the unfeasibility of the project. The organization must be projectized to support Agile.
Filipe;
In your reply to explain the advantages of agile development. These are clear, but my question is about how to cope with the problem when the client organization must sign a contract (because of its regulations and other constraints), such that includes the total cost of the project, and possible a timetable. Does agile development mean that a contract can not be on the basis of a fixed price/cost and timetable?
Thanks for your reply. It seems that in commercial project (where there is a client who pays for the development, etc), there are no short cuts, and "pure" agile development is not an option.
- Badges
- Science topic
- Similar topics
- Thesis Research