(Principles)
Change From:
• We look to the future. Our systems are secure and open source, created and maintained in repositories where it may be inspected by the public who places their trust in it and copied for use by other agencies.
• To: We look to the future. Our objective is that our systems are secure and open source, created and maintained in repositories where code may be inspected by like minded developers who place their trust in it, copy it for use in other agencies, and share discovered solutions that increase the functionality or safety of the code.
Change From
• We practice human-centered design. Everything that we produce is highly accessible, per WCAG 2.0. We build APIs before we build software atop it, and we believe that APIs require a well-designed interface
• To: We practice user-centered design. Everything that we produce is highly accessible, per WCAG 2.0. We build APIs before we build software atop it, and we believe that APIs require a well-designed interface
(Meetings)
Change From
• There are two basic meeting rhythms: daily standups and semi-weekly agile sprint rituals.
• To: There are two basic meeting ryhthms: daily standups and sprint rituals. The sprint duration will be determined by the development team’s leadership in consideration of the work to be done, and the resources available. The duration of a sprint is typically two weeks, resulting in semi-weekly agile sprint rituals.
Change From
• Every day, at 9 AM AKT, we hold a tight 15-minute standup.
• To: Every morning we hold a tight 15-minute standup.
Change From
• Every two weeks we hold sprint rituals. Each two-week sprint begins with backlog grooming (prioritizing work in the backlog) and sprint planning (define the work to be done over the next two weeks). Each sprint ends with a sprint review (demonstrate work done, and accept or reject that work) and a sprint retro (review the process of how people performed in this sprint). These are all held back-to-back, on the same day
• To: As each sprint ritual begins, we conduct backlog grooming (prioritizing work in the backlog) and sprint planning (define the work to be done over the next sprint). Each sprint ends with a sprint review (demonstrate work done, and accept or reject that work) and a sprint retro (review how the sprint went as far as people, relationships, processes and tools, identifying what went well and ways that we can improve quality and effectiveness.
(Design Research)
Change From
• Interview notes will be anonymized, lead researcher will be the keeper of the key (Joan Smith = Participant 1).
• To: Interview notes will be anonymized. The keeper of the key to participants is the state project UI/UX coordinator.
(Accepting Vendor Work)
Change From
• (Person TBD) merges pull request to master
• To: DHSS product owner and network services deployment team
(Principles) Change From: • We look to the future. Our systems are secure and open source, created and maintained in repositories where it may be inspected by the public who places their trust in it and copied for use by other agencies. • To: We look to the future. Our objective is that our systems are secure and open source, created and maintained in repositories where code may be inspected by like minded developers who place their trust in it, copy it for use in other agencies, and share discovered solutions that increase the functionality or safety of the code.
Change From • We practice human-centered design. Everything that we produce is highly accessible, per WCAG 2.0. We build APIs before we build software atop it, and we believe that APIs require a well-designed interface • To: We practice user-centered design. Everything that we produce is highly accessible, per WCAG 2.0. We build APIs before we build software atop it, and we believe that APIs require a well-designed interface
(Meetings) Change From • There are two basic meeting rhythms: daily standups and semi-weekly agile sprint rituals. • To: There are two basic meeting ryhthms: daily standups and sprint rituals. The sprint duration will be determined by the development team’s leadership in consideration of the work to be done, and the resources available. The duration of a sprint is typically two weeks, resulting in semi-weekly agile sprint rituals.
Change From • Every day, at 9 AM AKT, we hold a tight 15-minute standup. • To: Every morning we hold a tight 15-minute standup.
Change From • Every two weeks we hold sprint rituals. Each two-week sprint begins with backlog grooming (prioritizing work in the backlog) and sprint planning (define the work to be done over the next two weeks). Each sprint ends with a sprint review (demonstrate work done, and accept or reject that work) and a sprint retro (review the process of how people performed in this sprint). These are all held back-to-back, on the same day • To: As each sprint ritual begins, we conduct backlog grooming (prioritizing work in the backlog) and sprint planning (define the work to be done over the next sprint). Each sprint ends with a sprint review (demonstrate work done, and accept or reject that work) and a sprint retro (review how the sprint went as far as people, relationships, processes and tools, identifying what went well and ways that we can improve quality and effectiveness.
(Design Research) Change From • Interview notes will be anonymized, lead researcher will be the keeper of the key (Joan Smith = Participant 1). • To: Interview notes will be anonymized. The keeper of the key to participants is the state project UI/UX coordinator.
(Accepting Vendor Work) Change From • (Person TBD) merges pull request to master • To: DHSS product owner and network services deployment team