Guide to agile software development: part 2 — what should a customer do?
In this article, Shoosmiths looks at what any customer entering an agile software development project should do to ensure that it is geared up to implement such a project and that the documents governing the project adequately protect its position.
A customer of an agile development solution should evaluate the following before entering into such a project to ensure it is geared to receiving such a product:
- Internal due diligence - is there internal buy-in for the project for example, is the customer able to delegate authority for decision making?
- External due diligence - has the customer looked into the financial standing, technical and financial capabilities of the potential supplier? Can the supplier meet the objectives required?
- Cultural fit - is the culture of the customer (and the supplier) suited to agile development together?
- Objective - does the customer have a set objective that it plans/needs to reach? How easy is it for the customer to articulate that objective, given there will be no technical specification?
If you are registered and logged in to the site, click on the link below to read the rest of the Shoosmiths briefing. If not, please register or sign in with your details below.
News from Shoosmiths
News from The Lawyer
Briefings from Shoosmiths
A developer can commit the offence of ‘knowingly permitting’ the deposit of waste by its contractor, despite having no knowledge that the deposit was in breach of an environmental permit.
The case of Hershaw and ors v Sheffield City Council is a reminder to employers to be careful about how and what they communicate to their employees.
Analysis from The Lawyer
Compliance and corporate governance codes for large financial institutions will undoubtedly include provisions to regulate high pay in the future
There’s more to the ABS model than attracting the man in the street and procuring external investment. Partners at the big corporate firms, take note…