[Request]: Consider adding a sample project schedule to the Working with a vendor development team section of the De-risking Guide

[ameliaswong]

A description of the work

This was an idea from content testing the De-risking Guide with state employees.

“The challenge in the past has been around the schedule, sprint, timeline, and user testing. Having a schedule that can change can help people understand the goal.”

Source: https://docs.google.com/document/d/1HIMK3ocWeS6prAVHtVjXKnOl66Tb90l377I22AAMd-Q/edit

FFS team’s thoughts in 2024:

• An idea is to share a sample schedule of how a project schedule ended up after the fact to show how much user research happened, for example.

• Could mention that you can’t rely on a rigid schedule (we make this observation earlier when talking about PO role)

Context: When the FFS Team revised the De-risking Guide, it kept a list of backlog items for possibly addressing in future iterations. As the project lead during close-out, I transferred that list to the Guides repo.

Point of contact on this issue

Amelia Wong

Reproduction steps (if necessary)

No response

Skills Needed

• Any Human
• Design
• Content
• Engineering
• Acquisition
• Product
• Other

Does this need to happen in the next 2 weeks?

• Yes
• No

How much time do you anticipate this work taking?

A month

Acceptance Criteria

This ticket would involve:

• assessing the utility of the requested content by having conversations with relevant 18F staff (starting with Product) to decide if content on this subject should be developed/added (or if an existing resource could be linked to from the DRG)
• if no, you're done.
• if yes, the next step is figuring out what should be said or linked to with relevant 18F staff input
• if new content is needed, writing/editing content
• notifying TTS Outreach of changes to see if new content requires going through GSA concurrence
• going through GSA concurrence, if needed
• publishing