MDSA Retro Follow-on: Develop new applicant briefing doc
jkarpen opened this issue · comments
Create a document for tracking important details about new MDSA applicants. Josh will create a template with headers and run by Jason and Ian for review.
Notes from Retro sticky notes:
Develop process for identifying baseline client technologies
could be something project champion helps us with
github desktop works (so far)
powershell is sometimes locked down
git bash is sometimes not locked down but sometimes people cannot connect to GitHub
Make sure this includes some section on tools to identify what (if any) tools the applicant already has in place? Any they do not have will need to be procured so we want to loop them in early on it
This could be a simple table of tools and whether they have it or not
Be much more explicit about data access needs and in-scope datasets during project selection and development.
Staff requirements
Require staff to have prior knowledge of working with the project data
or
Advanced SQL/Data modeling knowledge
these can be yellow flags for project selection
Blank template briefing doc is here: https://docs.google.com/document/d/1dEzUOS4IYBLqRDRAQ583hUd8igkHEvFU4yoxomMuDhw/edit?pli=1#heading=h.yf06od49es9a
Ian reviewed and made changes. The next step I was going to take would be to populate this for DWR, specifically the group led by Aaron Cuthberson. We had calls with them on 3/8 and 4/19. Those notes are in the running Office Hours doc here: https://docs.google.com/document/d/1PkDk1qCoeRB8VGJR6ZTbEZTd9_yNmHvE0zXlAbz-zWo/edit?pli=1#heading=h.bagzwv7dwuvz
After that the plan was to let Jason review the template for DWR. If it looks good then start populating it for whichever groups Jason thinks are needed.
@ian-r-rose Would you consider this issue completed by the doc you created here? https://docs.google.com/document/d/1_pVzaPbSb28doC7L8zeRZfuFFFuut6APSRe5Swv1oB0/edit?pli=1#heading=h.rtlst0j4o648
Yes, I think so, thanks for the flag!