Recommended
Recommended
More Related Content
Similar to The Good, The Bad, & The Ugly: Best Practices and Pitfalls as a Government Contractor
Similar to The Good, The Bad, & The Ugly: Best Practices and Pitfalls as a Government Contractor (20)
Recently uploaded
Recently uploaded (20)
The Good, The Bad, & The Ugly: Best Practices and Pitfalls as a Government Contractor
- 1. The Good, the Bad, & the Ugly Best practices as a government contractor Laura Lanford & Kaitlin Devine
- 2. The Good, the Bad, & the Ugly Best practices as a government contractor Laura Lanford & Kaitlin Devine The Promise The Challenges The Approach
- 3. 1/ Who We Are
- 4. Laura Lanford Senior Manager, Data Engineering laura@nuna.com
- 5. January 18, 2018 SUBTITLE Main Title Caitlin Weber caitlin@adhocteam.us Danny Chapman danny@adhocteam.us Kaitlin Devine Director of Innovation kaitlin@adhocteam.us @kaitlinbdevine
- 6. 2/ The Promise of Government IT
- 7. Government experiences that are Fast Efficient Usable by everyone
- 8. Good example #2 (Kaitlin)
- 10. Good example #2 (Kaitlin)
- 11. Good example #2 (Kaitlin)
- 12. 3/ Working with Government as a vendor
- 13. Government can be … S L O W
- 14. Defensible to • GAO • Inspectors General • Congress • OMB • Media • Public
- 15. Speed vs defensability - Kaitlin (talk about all auditors) Government Market Startup Market
- 16. Government requires certainty* * even when there’s no certainty to be had
- 20. Agile is an ongoing & substantial shift for government
- 21. Live Footage of Our Legacy System Diagram
- 22. 4/ Tactics for bridging the gap
- 24. Responding to Change parts of Agile (needs picture -- Kaitlin will procure picture) Laura added a candidate picture below, if you want to use it. Responding to Change
- 25. COMFORT ZONE DANGER ZONE
- 26. via Visibility
- 27. Granularity - knowing status and visibility as you go along - We rely on client to take initiative to look at JIRA instead of going out of our way to give them artifacts and things for visibility - (laura) Information ≠ Clarity
- 28. “There are 22 days left in the project. There are 2 epics closed, 4 epics in progress, and 8 epics open. Several people were on PTO last week, and we couldn’t get a timely response from another vendor. We’re going to try and have our engineers work over the weekend. Their velocity has been 30 points per sprint but with the weekend work we should be able to get the extra points made up in the next sprint.” Data “We’re halfway through the project timeline but only 40% complete. Our current velocity is a risk to the project completion, which we are addressing in the next sprint and plan to have back on track by the end of next sprint Insight
- 31. I don’t know what you’re talking about
- 32. Facilitate Product Ownership, Don’t control it
- 33. ALIGNMENT only matters when you know where you want to go via makemesocialblog.wordpress.com
- 35. “The two biggest levers for improving people’s lives at scale are technology and government. We put them together.”