Meeting minutes
New member introductions
Introductions
Check in with Josh about Github Issues
jspellman: most of the issues are minor and dealt on different layer. if there is something that you want me to look into, I will check it out.
Fazio: we have asked Josh to cleanup the queue in github
janina: this is useful to have fresh overview especially for the people who come with fresh perspective.
<Fazio> When would they start using this model? Where do they start/What initial steps would they take? What happens if they have one person with 8 hours per week or less available to be documenting (and doing the due diligence with others that they work with to get that data)? Is this model still a feasible option for them?
stacey: I would like to hear from you all. How do you envision to use this model?
stacey: if I am a brand new person in my org, I would not know how to use it and I would like to have this info
Fazio: we get similar questions and need to work on the case studies.
janina: we regard the click-ability of this model for all. therefore the case studies is required.
Joshue108: I did some search in github. I want to ask you about the priority. There are tons of stuff out there
janina: let me suggest if there are editorials to validate and they are substantive please focus on them
Joshue108: before the call next week I will update about the progress
sheri: some use cases - Large organization, Equity, consulting model. we can put anything which is going to be helpful to explain people about the usage
Lionel_Wolberger_: size is not everything. because in some huge compnies have only one digital asset and some that are not big they may have multiple products
sheri: informed and un-informed model
Brian: mistake that we made was that we took this template, I would stay on first step whether it is one person or group of people are spending time on the template, we found that that we all had different interpretation.
Lionel_Wolberger_: we talk about different personas, but the person who is running the model is responsible for the progress. there is a huge difference between a typical case that we see very often.
Lionel_Wolberger_: you might be a beginner and you are in this org and working on multiple products. or other way around
ack, lionel
janina: we can form a subgroup if people are interested
janina: once we have something in writing we can add it in our document
stacey: I am willing to help
CharlesL: with these personas, I am wondring about the different dimentions sheets in excel e.g knowledge, skills, support.. would we also define the role of organization departments
sheri: whoever has data has to be involved
CharlesL: I am trying to see how these dimensions are going to be assigned in organizational structure
jeff: it depends on the scale of the company
<Fazio> Is the model only for SDLC/external-facing products? Or, does it encompass internal products, experiences, processes? This isn’t clear, but at first read of the introduction it seems external facing products only.
sheri: intent was to cover if you are external facing app includes 3rd party then they become important for the assessment
stacey: just in case if we are using any internal tool for external users like customer support which is not accessible, I believe it will be included in this model to assessment
CharlesL: this is what I was wondering about whole personas and knowing what dimension each company want to consider. I wasnt considering engineering procurement.
it might be good to point out
+1
<Fazio> Integrate stage - who’s creating the roadmap? Or is this meaning it’s baked into the roadmap for various teams? Part of OKRs?
stacey: Objective and Key results for quantitate goal settings
<Fazio> OKR = Objectives, Key Results