Bryan CampbellAgile Transformation and Coaching| 7C's Consulting Inc.Tomball, Tx, United States
Curious if there are any references material beyond blog pages for Agile Contracts and Agile compliance to SOX/HIPPA/PII etc that people could recommend. The PMI-ACP identifies these in their knowledge and skills and I wanted to understand the reference content. Saving Changes...
Sort By:
Elizabeth HarrinDirector| RebelsGuideToPM.comLondon, England, United Kingdom
Sorry, I'm not aware of any. Hopefully someone else will come along with some resources to share! Have you tried the government website? They might have some information. Saving Changes...
Obviously, a fixed bid contract is not going to work well with Agile methods. So, that leaves T&E (Time & Expense), as well as a hybrid model. The hybrid model provides a recurring payment (like a retainer) to the contractor to supply certain skills to the company. The retainer often includes a certain number of pre-paid hours per month (or sprint). Company can shift the recurring requirements (developers vs database analysis, for instance) with a contract-negotiated 4-8 week lead time. The contract could also call for the contracting company to provide additional staffing on an as-needed basis, such as a "super sprint" or some multi-iteration implementation, again with some contract-negotiated lead time. These adjunct staff would be T&E. Here is a website dedicated to agile contracts which I hope will help you.
Bryan CampbellAgile Transformation and Coaching| 7C's Consulting Inc.Tomball, Tx, United States
Thanks for the links, there is some great material in them. Reading Larman's article I wonder if I might be projecting my own definition of an agile 'contract' onto the term. He mentions
"It is meant to include the broader notion of agreements or specifications between parties in product development, and whether the emphasis is on nailing down these agreements or on ongoing collaboration, learning, and evolution. For instance, a traditional approach includes an early detailed specification of requirements and then “signing off” on these, which are then passed on to development teams for realization—a ‘contract’ of requirements."
I'm beginning to think the PMI-ACP reference to agile contracts is more in the form he describes above, the types of 'contracts' we use organizationally and not necessarily the legally binding contracts that lawyers and contract offices are involved in. Saving Changes...
