Hey ya'll,
I wanted to open up an issue for any questions or comments you might have on the changes that were addressed in the email from Adam and JP a few weeks ago. I will be scheduling a follow-up Design Manual meeting so we can discuss and provide answers, so please post away!
For your reference, the email is copied here:
Hi All,
We’d like to give you an update on the Design Manual (DM) and Capital Framework (CF). We’ve come a long way from where we were a year ago with the Design Manual surge as well as Capital Framework (woot!) and here is what we have in mind for the near-term:
DM and CF will remain separate for now: Merging DM and CF may be an ideal future state, but for now we should focus on completing the current backlog of work needed to support our projects.
Going forward for the DM:
The Product Owner (Candice) for the DM manages new standard needs and attends backlog planning for CF.
New approved standards will be added to the manual as draft images that the PO will prioritize into the CF backlog, no coding necessary.
Hack days (defined at a later date) will help provide more time for teams to work, to help alleviate balancing project work / DM work.
Going forward for CF:
A few FEWDs will be named as “primary maintainers” and asked to devote a percentage of their time to CF each week. This role will be completely voluntary, but project teams will accommodate for this in their planning.
There will be alternating bi-weekly backlog refinement with Adam as Product Owner where we will organize and prioritize CF work.
Expand the “definition of done” to include new component being available in the Design Manual.
In the near term we will wrap up the Atomic work and going forward we will prioritize work based on the bi-weekly backlog refinement meeting and partnership with the DM team.
Critical Capital Framework updates/needs could go through either the CF.gov Platform team or the Design Ops intake process and made part of their officially tracked work.
Who is the audience for DM and CF?
We strive for transparency in making all our work public and available, but the primary audience is us, our designers and developers. With that in mind we hope that it will help us continue to think of the work as being iterative.
We recognize there are a lot of questions that aren’t addressed here and new ones will arise as we move forward. Our process should always facilitate the best work and we will adjust wherever necessary. Please send us any feedback, questions, comments.
Hey ya'll, I wanted to open up an issue for any questions or comments you might have on the changes that were addressed in the email from Adam and JP a few weeks ago. I will be scheduling a follow-up Design Manual meeting so we can discuss and provide answers, so please post away!
For your reference, the email is copied here:
Hi All,
We’d like to give you an update on the Design Manual (DM) and Capital Framework (CF). We’ve come a long way from where we were a year ago with the Design Manual surge as well as Capital Framework (woot!) and here is what we have in mind for the near-term:
DM and CF will remain separate for now: Merging DM and CF may be an ideal future state, but for now we should focus on completing the current backlog of work needed to support our projects.
Going forward for the DM:
Going forward for CF:
Who is the audience for DM and CF? We strive for transparency in making all our work public and available, but the primary audience is us, our designers and developers. With that in mind we hope that it will help us continue to think of the work as being iterative.
We recognize there are a lot of questions that aren’t addressed here and new ones will arise as we move forward. Our process should always facilitate the best work and we will adjust wherever necessary. Please send us any feedback, questions, comments.
Thanks, Adam & JP