Code book derived from first data collection - 1st set of interviews,,
Code,CodeName,Description
Code1,NFR: Performance,"Participants describe performance as it relates to responsiveness and load time. Includes load time, responsiveness, response time, quick or fast response."
Code2,NFR: Maintainability,"Participants describe maintainability as it relates to developers or other stakeholders being able to understand or maintain aspects of a product. Includes writing understandable code, includes processes that improve developer experience."
Code3,NFR: Usability,"Participants describe usability as it relates to the visual aspects of a product. Includes aesthetics, look and feel, the visual aspects of a product, user experience, arrangement of visual components."
Code4,Validating NFRs through feedback,"Participants elicit/validate non-functional requirements through a variety of feedback cycles. During the feedback cycle, the development team can validate if an NFR is being met or elicit new NFRs that haven’t been implemented/considered yet. Feedback cycles include code reviews, meetings, demos and informal conversations geared at giving or receiving feedback."
Code5,Unspecified NFRs,"Participants report that the non-functional requirements are mostly unwritten or unspecified. Includes keywords: undocumented, unspoken or unwritten, unorganized, unclear or misunderstood, etc. "
Code6,Discussing problems and solutions,"Participants resolve issues, misunderstandings or changes in the scope of projects through discussing problems and solutions. Includes different types of meetings for discussing/implementing NFRs, informal conversations about problems or solutions. (must be specific to NFRs)"
Code7,Asking questions,"Participants use question asking to reach a mutual understanding of a goal. Includes asking questions during formal and informal meetings, includes any other reference to asking questions to reach a mutual understanding of NFRs."
Code8,Wireframing interface designs,Participants use wireframes  to describe NFRs and make decisions about NFRs within the team. Includes sketching or creating mockups for possible solutions using a variety of visual or creative tools.
Code9,Individual Differences,"Participants report differences in individuals as a challenge for reaching mutual understanding. Includes differences in points of view, ideas, skills, experience, background and level of knowledge within the organization."
Code10,Deepening the understanding of NFRs through experience,"Participants describe depeening their understanding of non-functional requirements through experience within the organization. Includes limitations due to lack of experience, learning how the organization values NFRs, learning about NFRs over time. "
Code11,Limited understanding of customer context,"Participants describe the limited understanding of  clients/customers products or process, as one of the reasons for unclear or undocumented NFRs. Includes insufficient elicitation of NFRs from customers, limited understanding of customers, limited understanding of customer’s need, limited understanding of the origin of customer projects, learning about customers."
Code12,Gaps in communication,"Participants describe gaps in communication between stakeholders and within the development team, that could lead to a change in the scope of projects or other problems. Includes when there is a lot of feedback during meetings, when people make assumptions about a product or process, when people make assumptions about a person’s level of knowledge/experience, when there is unclear expectations, it could lead to misunderstanding within the team."
Code13,Common grasp of problems/solutions,"Participants describe their perspective of ‘shared understanding’. Includes agreement, being on the same page, understanding within the team and any other references to mutual agreement or understanding.  "
Code14,Limitations on team’s abilities. ,"Participants describe limitations on the abilities of developers or other stakeholders. Includes limitations on skills, experience or workload ."
Code15,Increased awareness,"Participants describe increased awareness on shared understanding and NFRs. Includes better understanding reached as a result of the interview sessions, increased understanding about NFRs, thinking about shared understanding or NFRs."
,,
Codebook derived from further data collection - 2nd set of interviews,,
Code ,CodeName,Description
Code1,Asking questions,Participants use question asking to reach a mutual understanding of a goal. Includes asking questions during formal and informal meetings including any other reference to asking questions to reach a mutual understanding.
Code2,Eliciting NFRs through mockups,"Participants use mockups to elicit some NFRs from customers such as user experience requirements. Mockups include: diagrams, sketches, wireframes, MVPs, demos, etc. Excludes scenarios unrelated to NFRs."
Code3,Gaps in knowledge,"Participants describe gaps in knowledge that may exist when they do not have enough background or context about a product or customers or their organization. Includes lack of background knowledge, lack of knowledge, knowledge gaps, etc"
Code4,Documenting solutions with diagrams.,"Participants use diagrams, sketches or wireframes to document solutions during formal or informal meetings through virtual drawing or design tools."
Code5,Validating NFRs through feedback.,"Participants discover, capture and sometimes validate NFRs through feedback mechanisms. Feedback include user testing, code reviews, deep-dive meetings and other meetings that help the developers validate or capture NFRs."
Code6,Deepening the understanding of NFRs,"Participants describe ways they deepen/improve their understanding of non-functional requirements/learning about how to handle NFRs such as through specialized training, wireframing, code reviews, guilds (learning from guild members, learning through guild meetings), learning from previous projects/specifications, learning about the organization, etc"
Code7,Defining development standards through guilds.,"Participants define or set development standards through guilds. Development standards refer to coding, design, documentation, testing standards, etc. Excludes any development standards that are not related to NFRs."
Code8,Easy conversations on Gather,"Participants describe Gather as a medium for having easy, informal conversations with each other. Includes mentions of informal conversations, easy conversations, talking, etc through Gather."
Code9,Connectedness through Gather,"Participants describe Gather as a medium that creates some connectedness with the team. Includes mentions of connectedness, not feeling alone, etc through Gather."
Code10,Expanding conversations on Gather,"Participants describe Gather as a way to easily expand conversations to include more people. Includes expanding conversations, jumping into conversations, etc."
Code11,Change in scope due to rework of designs.,"Participants describe situations where designs are re-iterated or changed during the development phases. Includes changes in view, changes in design, etc."
Code12,Measuring emotion response as feedback,"Participants describe a form of feedback measured as emotional responses. Participants may validate or evaluate NFRs such as user experience using this feedback. Includes visceral reactions, emotional responses, physical reactions, etc."
Code13,Cross-functional roles and communication through guilds,"Participants describe guilds are enabling cross-functional roles and communication for decision making. Includes cross-functional teams, communication through guilds across several teams, etc."
Code14,Evaluating development standards through feedback,"Participants describe scenarios that allow them evaluate some development standards through feedback from customers/ code reviews, or other feedback mechanisms"
Code15,Learning release management (NFR) through specialized training,"Participants describe special training sessions organized by the organization that focuses on release management (configuration, deployment, documentation, etc). These trainings help developers and non-developers learn about several aspects of release management."
Code16,Need to understand Customer context,"Participants describe the importance of understanding customer’s background, product, or ideas in order to elicit more requirements from them."
Code17,Defining standards for eliciting requirements,Participants describe how the team is defining standard architectures that help with eliciting requirements.
Code18,Communicating development standards with client,Participant describe communicating development standards with clients as a way to elicit requirements.
Code19,Setting programme configurations with/for clients.,Participants describe the deployment and configuration process with clients
Code20,Insufficient elicitations of NFRs,Participants describe a scenario where requirements were loosely acquired and this led to a lot of UX/design rework and a change in scope.
Code21,Sharing contents easily through Gather,Participant describe how Gather makes it easy to share content with other team members.