Open ddotrollins opened 8 years ago
Suggestion: Change landmines
to pitfalls
or traps
to avoid conflating procurement problems with actual deadly landmines.
One thing I seldom hear addressed is procuring a totally new thing vs. procuring for services to maintain something you already have. For example, sites.usa.gov does daily stand ups, we have a Kanban board and a release schedule. But there are certain requirements, like working with GSA IT/OCIO to address security concerns. How do you include things like that, without turning your RFP into a combination of agile and waterfall? Or maybe hybrid contracts are ok? Maybe "agile or bust" isn't always realistic.
Typo in this bulleted list:
Background
Here’s a collection of resources that will help you understand digital acquisitions:
- TechFar
- TechFar Hub
- Agile Acquisitons 101
Leave feedback here for the Overview section of the playbook