|
12.1 Plan Procurements The process of documenting project purchasing decisions, specifying the approach, and identifying potential sellers. Simple Version: Writing up, or referencing how the purchasing process will be undertaken. |
|
|
PMI |
Agile PMBOK, Agile Difference, Comment |
|
Inputs Scope baseline Requirements documentation Teaming agreements Risk register Risk-related contract decisions Activity resource requirements Project schedule Activity cost estimates Cost performance baseline Organizational process assets Tools and Techniques Make-or-buy analysis Expert judgement Contract types Outputs Procurement management plan Procurement statements of work Make-buy-decisions Procurement documents Source selection criteria Change requests |
Inputs Scope baseline Requirements documentation Teaming agreements Risk register Risk-related contract decisions Activity resource requirements Project schedule Activity cost estimates Cost performance baseline Organizational process assets Tools and Techniques Make-or-buy analysis Expert judgement Contract types Outputs Procurement management plan Procurement statements of work Make-buy-decisions Procurement documents Source selection criteria Change requests Since the Plan-Procurements step includes considering the risks involved with each make or buy decision, it is important to consider any of this risks an agile approach may bring. For instance an organization following an agile approach engaging with a waterfall based vendor. The stakeholder education process for ensuring all parties understand the approach and closure (“Done”) criteria is important. Often group claim to be doing agile (or waterfall) but in fact are not following all the steps and quality assurance processes than generally define these approaches. Don’t take things on face value, plan to investigate and assess the risks. |
