search

18F / guides

18F’s guides equip 18F teams, our partners, other practitioners, lawmakers, and the public with tools and practices to improve public services. They affirm experiences, build confidence, and empower exceptional digital experiences.
https://guides.18f.gov
Other
31 stars 13 forks source link

🟢 Review agile position descriptions for content updates #313

Open jstrothman opened 2 years ago

jstrothman commented 2 years ago

The Derisking Guide links to brief agile position descriptions which last had substantive updates in Jan 2020 (aside from the addition of the Product Manager role in Feb 2021).

These could use SME review for currency (e.g. programming languages) and equity lens. Also per Shea B (Cloud) noted that we should add roles for Cloud Solutions Architect or Cloud Engineer.

bpdesigns commented 3 months ago

@cantsin should the derisking guide include cloud roles? @elisaachen should there be a service design role as part of an agile team?

cantsin commented 3 months ago

I agree that these roles need SME review. As for adding, we (18F) seldom do cloud solutions or devsecops work so we are not best suited to write position descriptions for these roles.

elisaachen commented 3 months ago

@bpdesigns - can you point me to where on our derisking guide this is? Was trying to understand the context where this content lies. Also, I know @ameliaswong has got content in the works for updating our de-risking guides with the FFS project and wondering if there some be coordination between TLC and FFS for future updates to the de-risking guide?

bpdesigns commented 3 months ago

Ah! @ameliaswong are we including these on the future of the de-risking guide? I'm also not seeing these position descriptions on the actual site.

ameliaswong commented 3 months ago

No @bpdesigns , the updates to the DRG don't include agile position descriptions. Gave you and @elisaachen viewer access to the document so you can review content if helpful (it's going through TTS approvals which is why I'm being stingy with permissions).

Also FYI, I'm writing up a deployment strategy after talking with @adunkman and @peterrowland. I'll share that with you both when we've gotten a full draft.