| Actionable Insight |
Evidence-driven findings that inform actions that should be taken by decision makers.
See also Insight (and within that definition Design Insights). |
An insight which is actionable are...
1) Aligned: it should be closely tied to key goals or KPIs.
2) put in Context: it should explain why an insight is important or unique (benchmarks + comparisons can be helpful).
3) Relevant: delivered to the right people at the right time, using the right channel(s).
4) Specific: it must clearly explain why something has happened.
5) Novel: it should challenge or evolve current beliefs and reveal new patterns. |
"An insight that drives action is typically more valuable than one that simply answers a question - especially an insight that makes you rethink something and pushes you in a new direction. They are the highly treasured output of all the work that goes into collecting, preparing and analyzing your data. Maximizing the actionable insights you formulate from any investment in research is important." |
https://www.forbes.com/sites/brentdykes/2016/04/26/actionable-insights-the-missing-link-between-data-and-business-value
https://www.techopedia.com/definition/31721/actionable-insight
https://en.wikipedia.org/wiki/Insight
https://hbr.org/2012/09/metrics-are-easy-insights-are-hard
http://www.copyright.com/blog/turn-analytics-actionable-insights/ |
| Agent (Software Agent) |
Software that acts on behalf of a user or other party/agent, and decides which (if any) action is appropriate to take.
Agents are also known as bots (from robot).
See also Autonomous Agent, Calculator, Engine, Artificial Intelligence (AI). |
Agents may be "embodied" (e.g. a robot), or embedded (such as in a chatbot executing on a phone (e.g. Siri)). Software agents may be autonomous or work together with other agents or people.
Agents interacting with people may possess human-like qualities such as natural language understanding and speech, personality.
- Intelligent agents exhibit some aspect of artificial intelligence, such as learning and reasoning.
- Autonomous agents are capable of modifying the way in which they achieve their objectives.
- Distributed agents are executed on physically distinct computers
- Multi-agent systems are a collection of distributed agents that work together to achieve an objective that could not be accomplished by a single agent acting alone
- Mobile agents are agents that can relocate their execution onto different processors
|
|
Wikipedia |
| Agile
(Kakama) |
Agile is a method of project management, used especially for software development (but is now being used more widely than just development), that is characterised by the division of tasks into short phases of work and frequent reassessment and adaptation of plans. |
Agile was originally an approach for software development (but is now being adopted more widely in different industries). The agile method gives teams the ability to take requirements and allows for their solutions evolve through the collaborative effort of self-organising and cross-functional teams and their customer(s)/end user(s). It advocates adaptive planning, evolutionary development, early delivery, and continual improvement, and it encourages rapid and flexible response to change. It focuses the team on 'just enough' (or minimal viable product) and those pieces of work should be able to be completed within a one to two week planning cycle.
With the focus not being purely on software development the original Manifesto for Agile Software Development has evolved to Modern Agile (see links following), which makes agile as a method accessible to other industries.The values and principles have been derived from and underpin a broad range of frameworks, including Scrum and Kanban. |
|
https://en.wikipedia.org/wiki/Agile_software_development
https://en.wikipedia.org/wiki/Google_Dictionary
http://modernagile.org
http://agilemanifesto.org |
| AISA (Approved Information Sharing Agreement) |
An enabling tool that allows government agencies to provide efficient and effective public services by allowing agencies to collaborate and share information without intruding on individuals' rights or exposing agencies to legal risk. |
As of 2018 around 7 AISAs exist between government agencies. |
An AISA exists between Inland Revenue and New Zealand Police "to assist Police to deliver the public service of reducing the rate of serious criminal offending in New Zealand. This agreement authorises the disclosure of information to New Zealand Police to assist Police to deliver the public service of reducing the rate of serious criminal offending in New Zealand." |
https://www.privacy.org.nz/privacy-for-agencies/information-sharing/approved-information-sharing-agreements/ |
| Alpha (phase of Lab workflow model) |
The third phase in the Service Innovation Operational Workflow Model where a very basic working service is developed to gather user feedback, test that it works as intended, and inform whether it is technically feasible to build.
See also Minimum Viable Product (MVP) |
As the service is built the team seeks to:
1) Test the hypotheses created in the Design Discovery phase.
2) Test that the service you want to build is technically possible
3) Test that the service facilitates intended outcomes
4) Observe if the service causes any unintended outcomes
Research is completed with a small group of users, and early feedback is gathered about the design of the service.
Note: Software in Alpha state can start to be tested with users beyond limited levels enabled by rough prototypes. Alpha software must be considered unstable - with implications including data loss. |
"If you pass an alpha assessment, you can start writing your code in production and recruiting users to use your private beta." (GOV.UK Service Standard) |
Service Innovation Lab - Welcome Pack
https://docs.google.com/document/d/1DQOS4bhd8VcZY2ftpGGN-lco-5jdiI9_z66Yg4Jpu-Y/edit?usp=sharing
UK Government Service Assessments
https://www.gov.uk/service-manual/service-assessments/how-service-assessments-work
|
| API |
Application Programming Interface |
A set of clearly defined methods of communication between various software components. Computer programs are typically organised and assembled into some type of software components that are combined to form larger IT systems. To prevent a massive tangle of complex software in which every piece of software is able to talk to every other piece of software, interfaces (or APIs) are used to partition the IT system.
An API hides a lot of detail of the internal workings of a software component that the outside world does not need to know. In this way, APIs provide a description of how to use the functionality of a software component and to exchange data with it. At run-time, software components interact with one another through the application programming interface.
Governments are currently thinking about APIs for service delivery, including how open government APIs can be used to deliver innovative services by third parties, and by businesses to directly transact with government. |
"There are over a thousand applications which use the Trade Me API, built by individuals or organisations outside Trade Me. These applications provide services which meet needs of users not catered for by the Trade Me website or API - in some cases by providing a different interface to the same underlying functions - and in other cases by mashing up a combination of APIs."
NZ Companies Office: "We offer a range of APIs that help our customers to build software that connects directly to our systems."
"NZQA has created an API to allow access to a student’s Record of Achievement”. |
Federated Services Delivery Glossary
https://docs.google.com/document/d/1RynDtghq41mxRCL86vRgn_M4KjyDigJtamjEd9IJnKw/edit?usp=sharing
https://webtoolkit.govt.nz/blog/emerging-tech-apis-for-service-delivery/ |
| Artificial Intelligence (AI) |
Intelligence demonstrated by machines, in contrast to the natural intelligence displayed by humans and other animals.
An intelligent agent is any device that perceives its environment and takes actions that maximize its chance of successfully achieving its goals.
In everyday usage, "artificial intelligence" refers to any time when a machine mimics "cognitive" functions that humans associate with other human minds, such as "learning" and "problem solving". |
Modern machine capabilities generally classified as AI include successfully understanding human speech, competing at the highest level in strategic game systems (such as Chess and Go), autonomously operating cars, and intelligent routing in content delivery networks and military simulations.
Machine learning algorithms (software) are a subset of AI algorithms - these are computer algorithms that improve automatically through experience (they are trained to recognise patterns).
For any system that learns, the output is determined by the input it receives. There are therefore many sources of bias. These sources include (but are not limited to!) the data we use to train systems, and our interactions with them in the “wild". |
"we often see the machine learning and AI buzzwords being thrown around to indicate that an algorithm was used to analyze data and make a prediction. Using an algorithm to predict an outcome of an event is not machine learning. Using the outcome of your prediction to improve future predictions is." |
Wikipedia
https://www.datasciencecentral.com/profiles/blogs/artificial-intelligence-vs-machine-learning-vs-deep-learning
AI Forum NZ - Shaping a Future New Zealand
https://aiforum.org.nz/wp-content/uploads/2018/07/AI-Report-2018_web-version.pdf |
| Autonomous Agents |
An intelligent Agent operating on an owner's behalf but without any interference of that ownership entity. |
Entities operating on an owner's behalf but without any interference of that ownership entity. Agents may be embodied (e.g. a robot), or embedded (e.g. Siri). Automous agents are capable of modifying the way in which they achieve their objectives. |
|
Emerging Tech Landscape |
| AI applications |
Programs that have been developed to perform specific tasks, and could be used for a wide range of activities.
|
Applications include:
- Identification (Facial recognition, fingerprints, voice, gait)
- Natural language generation/processing (NLG/NLP)
- Deep fakes
- Process analysis/optimisation
- Conversational interfaces
|
|
Emerging Tech Landscape |
| AI tools |
AI Tools help to solve learning, reasoning, knowledge, planning (etc!) problems, and are typically based on search and mathematical optimisation, including statistics + probability.
|
|
|
Emerging Tech Landscape |
| Augmented reality (AR) |
An experience which overlays virtual objects on the real-world environment.
See also Mixed Reality (MR) and Virtual Reality (VR) |
Augmented reality is primary current used via a mobile handheld device and not a headset (vs Mixed Reality (MR or MX) which is primarily headset based. |
"Pokémon Go is an augmented reality (AR) mobile game developed and published by Niantic for iOS and Android devices..... It uses the mobile device GPS to locate, capture, battle, and train virtual creatures, called Pokémon, which appear as if they are in the player's real-world location" |
Wikipedia
https://en.wikipedia.org/wiki/Pok%C3%A9mon_Go |
| Behavioural Archetypes |
A UX tool which helps a designer (and their team) understand and empathise with the people they are designing for. The aim is to broadens their perspective and force them to challenge their own biases and conventions in favor of approaches that align to the people’s goals, needs and pain-points.
See also Personas |
Archetypes are based on research data, and focus on user behavior and motivation, and many believe they are more useful than personas for defining experiences. The aim is to empower your team to immerse themselves in what the customer is doing and what they desire to achieve, resulting in a more accurate UX strategy, and creating a stronger foundation for the project overall.
Archetypes are steeped in user behavior. They contain details from user interviews around a group’s needs, motivations and pain-points. Archetypes focus on the “who does what, when they do it, and why” of your audience research. They provide insight into behavior patterns – how a customer is using a product or service currently. |
|
|
| Backlog |
The backlog, also known as product backlog is a prioritised list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product and is referenced daily by the scrum team to determine what they need to work on next. |
The product owner is responsbile in ensuring the backlog/product backlog is kept up to date and has all the right information in there for the scrum team use to complete a task. The content is broken up into a story and are prioritised for the scrum team. The product backlog is living and will be constantly changing and evolving on a daily basis and is never complete. |
|
https://www.scrum.org/resources/what-is-a-product-backlog
https://www.agilealliance.org/glossary/backlog/ |
| Backlog Grooming |
See backlog refinement for further information |
See backlog refinement for further information |
|
|
| Backlog Refinement |
Also known as backlog grooming. Backlog refinement is when the product owner and some or all of the team review what's coming in the next sprint |
Backlog refinement is when the product owner, with some or all of the scrum team review the backlog. This gives the scrum team the opportunity to look at what features are likely to come up in the next sprint. It's also an opportunity to make sure they are prioritised correctly, that they have everything required to deliver that feature prior to sprint planning. It also means that if there are still questions, then the product owner can resolve these ahead of sprint planning. |
|
https://www.mountaingoatsoftware.com/blog/product-backlog-refinement-grooming
https://www.agilealliance.org/glossary/backlog-grooming/ |
| Beta (phase of Lab workflow model) |
Developing a service to meet demands of a live environment, including understanding how to build and scale the service while continuously make improvements to meet user needs. |
Building a fully working service based on the Alpha - this may involve adding/modifying features based on evaluation and design roadmap. This is done in close partnership with government agencies and their technology partners, and includes iterative releases of working versions of the service to the public. At this stage the product will need to meet standards and policies for things like privacy, security and accessibility. |
|
https://www.digital.govt.nz/standards-and-guidance/strategy-and-planning/digital-lifecycle/ |
| Bias (in computer/AI systems) |
Computer systems that systematically and unfairly discriminate against certain individuals or groups of individuals in favour of others. |
There are many sources of bias including (but definitely not limited to):
- Preexisting Bias (bias that gets built into a software system because the organization determining the requirements for the software is biased. The software reflects their own bias)
- Technical Bias (Technical bias emerges as a consequence of technical constraints or decisions. Limited space on a display, input devices, and specific algorithms can bias a system in one way or another)
- Emergent Bias (Use of a software system changes over time. Through the addition of new users or new types or sources of data, bias can emerge in ways that are difficult - if not impossible - to predict when the system was built) |
|
Bias in Computer Systems
https://vsdesign.org/publications/pdf/64_friedman.pdf |
| Big data |
Extremely large data sets that can be analysed computationally to reveal patterns, trends, and associations (often relating to human behaviour and interactions). |
|
|
Emerging Technology Landscape
|
| Biotechnology |
Technology based on biology. It harnesses cellular and biomolecular processes to develop technologies and products that help improve our lives and the health of our planet. |
Examples include:
- Genetics
- Proteomics (large scale study of proteins) |
|
Emerging Technology Landscape
|
| Bot |
See Agent.
An intelligent Agent is any device that perceives its environment and takes actions that maximize its chance of successfully achieving its goals. |
|
|
|
| Calculator (Software) |
Simple software with a simple interaction model.
See also Engine and AI |
Software calculators generally
- provide options for the user to select one at a time.
- perform a process that consists of a sequence of steps, each of which applies one operation
- have no purpose other than these processes
- do not accept large amounts of input data or produce many results
- Do not make inferences on results / outcomes |
"Non-numerical calculators include life-style and scientific calculators" |
|
| Citizen |
A legally recognised subject of a state, either native or naturalised. |
Person who is entitled to enjoy all the legal rights and privileges granted by a state to the people comprising its constituency, and is obligated to obey its laws and to fulfil his or her duties as called upon. |
“Jane was well-respected and viewed as an upstanding citizen”. |
Business Dictionary |
| Cloud computing |
Using a network of remote servers to store and access data and software, rather than a local server or device. |
The on-demand availability of computer system resources, especially data storage and computing power, without direct active management by the user. The term is generally used to describe data centers available to many users over the Internet.
Clouds may be limited to a single organization (enterprise/private clouds), be available to many organizations (public cloud), or a combination of both (hybrid cloud).
Cloud computing relies on sharing of resources to achieve coherence and economies of scale. |
|
Emerging Technology Landscape
https://drive.google.com/file/d/1E9g9uJU6w260bIV33cK0vprhfvBowCLY/view?usp=sharing
https://en.wikipedia.org/wiki/Cloud_computing |
| Common capabilities
|
The collection of standards, processes, resources, tools, skills and behaviours needed to ensure a consistent, integrated and seamless service experience across all the various integrated services operating within the FSD ecosystem.
|
|
|
Federated Services Delivery Glossary |
| Complex Problems |
Problems with no obvoius solution |
|
|
|
| Concept |
a provocative glimpse at whats possible |
A concept is of something that does not exist but can be made of or be based on things that do exist |
Examples of concept design:
speculative client work
exploratory projects
concept products
pre-production designs |
|
| Continuous Improvement |
A foundational principle of Agile: "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly."
Can also be applied to products/services - where it means reacting to user needs, stakeholder demands, and evolving targets. |
An Agile team will typically hold a reflection session or Retrospective after each iteration or Sprint. This is a chance for the entire team to surface what's been going well, what could be improved, and the improvements or changes the team will focus on in the next Sprint. |
speculative client work |
Service Innovation Work Programme 2018 2019 with detail
https://drive.google.com/open?id=1fLO2VbHkHccF4A1ixoTsRkNBgF8hzSFU |
| Daily huddle |
See daily stand-up |
See daily stand-up |
exploratory projects |
|
| Daily stand-up
(Tū mai) |
The stand-up is a daily meeting, is one of the Scrum practices. It's a meeting which lasts between 5 - 15 minutes and the scrum team discuss three questions:
- what did you do yesterday
- what are you doing today
- are there any blocks from stopping you completing this task? |
The stand-up is a daily meeting, is one of the Scrum practices and gives the team the opportunity to self organise for the day. It's also know as the daily huddle. It's a good opportunity to draw awareness to any 'hidden' work and create transparency within the team on other tasks that they might need to make time for during the day.
It's held at the same time and the same location daily and the team must stand-up (this helps keep the focus tight).
It's a meeting which lasts between 5 - 15 minutes, but should never exceed 15 minutes and the scrum team discuss three questions:
- what did you do yesterday
- what are you doing today
- are there any blocks from stopping you completing this task? |
concept products |
https://www.mountaingoatsoftware.com/agile/scrum/meetings/daily-scrum
https://en.wikipedia.org/wiki/Stand-up_meeting |
| Data |
Raw and unprocessed facts, usually in the form of numbers and text. Data can be quantitative (measured) or qualitative (observed).
See also Information and Insight |
|
prototypes |
https://www.forbes.com/sites/brentdykes/2016/04/26/actionable-insights-the-missing-link-between-data-and-business-value |
| Design Sprint
(Ohia mano) |
A (typically) five-day intense workshop-style process for answering questions through design, prototyping, and testing ideas with customers. |
The (Google) Design Sprint was developed by Google Ventures based on a bunch of good practice from dSchool, IDEO etc.
Design Sprints can vary in length - but care must be taken not to lose the benefits of their highly structured process. The Lab has run a number of three day design intensive sprints recently (16/10/2018). |
pre-production designs |
The Design Sprint
http://www.gv.com/sprint/
https://designsprintkit.withgoogle.com/introduction/overview |
| Design Thinking |
A set of mindsets and skillsets that can be used by anyone to examine and understand a problem and to drive better ideas and launch more experiments into the world. |
Design Thinking is based on the idea that the best way to learn is by doing, working on real problems in real time.
The (Google) Design Sprint is a well known example of a multi-stage Design Thinking workshop. |
|
The Design Gym |
| Digital Service Council (DSC) |
Established in 2013 (and replaced by SIWG in 2015) to provide governance to the Result 10 programme of work. |
The council was made up of 8 agencies: Department of Conservation, DIA, IR, MBIE, MSD, NZ Customs, Police, NZTA.
The council club-funded the programme until July 2015 when it became funded by other means. Club-funding meant that each agency contributed an amount into a pool that the overall programme was then funded from.
|
|
Service Innovation Lab - Welcome Pack
https://docs.google.com/document/d/1DQOS4bhd8VcZY2ftpGGN-lco-5jdiI9_z66Yg4Jpu-Y/edit?usp=sharing
|
| Discovery |
The second phase in the Service Innovation Operational Workflow Model where an evidence led process is followed to identify potential changes that will benefit customers. |
This phase involves a deep dive on a specific opportunity by looking at the problems customers are facing, analysis of the causes behind these problems, hypothesis led validation to test assumptions and ideation and potentially prototyping to develop a range of change concepts that could help users. There are two types of Discovery - Discovery - Research Discovery and Discovery - Design Discovery. A decision about which type of Discovery is required is made in the Scoping phase. |
|
"Service Innovation Work Programme 2018 2019 with detail
https://drive.google.com/open?id=1fLO2VbHkHccF4A1ixoTsRkNBgF8hzSFU"
Service Innovation Lab - Operational Workflow Model
https://docs.google.com/document/d/1vxH0hOLGa9SQGH7xIQnODQXUIqKl7TDa0svCCBAEDAM/edit?usp=sharing |
| Discovery - Design Discovery |
A standard rapid Lean product/service validation process starting with a design brief or Lean Canvas, problem definition, problem validation, and finishing with solution validation. |
If the needs of users are well understood, and clear problems have been identified then it may be possible to begin this Discovery stage without a Research Discovery. Deliverables from this stage include a description of future state, defined measures of success, a bunch of prototyped solutions which didn't solve the problem, and a validated prototype that is worth (re)developing into an Alpha (or not!). |
|
Service Innovation Lab - Operational Workflow Model https://docs.google.com/document/d/1vxH0hOLGa9SQGH7xIQnODQXUIqKl7TDa0svCCBAEDAM/edit?usp=sharing |
| Discovery - Research Discovery |
Focused research into the needs of users in a defined opportunity area with the aim of identifying problems which are worth defining in more detail (and solving for) in a Discovery - Design Discovery phase. |
A substantial piece of research investigation and evidencing. It is applicable to complex issues that fall within but are not limited to, a ‘Life Event’.
Consists of two sub-phases
1) Understand: broad and shallow research
2) Refine: narrow and deep research into particular issues (what's the problem, who is experiencing it, when it is happening) |
|
Service Innovation Lab - Operational Workflow Model https://docs.google.com/document/d/1vxH0hOLGa9SQGH7xIQnODQXUIqKl7TDa0svCCBAEDAM/edit?usp=sharing |
| Encryption |
Converting data from a readable form to an encoded version that can only be decoded by another party if they have access to a decryption key. Encryption is used to help keep data private, both when it is transmitted across networks, and when it is stored. |
There are two common categories of encryption:
1) Aymmetric-key ciphers, also referred to as "secret key," use a single key, sometimes referred to as a shared secret because the system doing the encryption must share it with any entity it intends to be able to decrypt the encrypted data. The most widely used symmetric-key cipher is the Advanced Encryption Standard (AES), which was designed to protect government classified information. The challenge with this form of encryption is that the sender must exchange the key used to encrypt the data with the recipient before the recipient can perform decryption on the ciphertext. The need to securely distribute and manage large numbers of keys means most cryptographic processes use a symmetric algorithm to efficiently encrypt data, but they use an asymmetric algorithm to securely exchange the secret key.
2) Asymmetric cryptography, also known as public key cryptography, uses two different but mathematically linked keys, one public and one private. The public key can be shared with everyone (and is used to encrypt data), whereas the private key must be kept secret (as it is used to decrypt data which has been encrypted with the private key). The RSA encryption algorithm is the most widely used public key algorithm (the Secure Socket Layer (SSL) used by web browsers using the HTTPS protocol).
This form of cryptography can also be used to ensure the integrity (was the data altered since being encrypted), authenticity (are you sure it came from the source you think it did) of data through the use of digital signatures. |
Emerging Tech Landscape:
"Encryption assists in protecting privacy. It
turns sensitive information into “for your eyes only” that’s intended only for the parties that need to access it" |
https://en.wikipedia.org/wiki/RSA_(cryptosystem)
https://en.wiktionary.org/wiki/nonreputable#English
https://searchsecurity.techtarget.com/definition/encryption |
| End User |
Person who ultimately uses or is ultimately intended to use a deliverable (product, service, process etc). |
An end user is the person that a deliverable (service, software program, hardware device, product, process etc) is designed for - and who uses the deliverable after it has been fully developed (and potentially marketed, and installed). |
“Organisations should always keep the end user in mind when designing a new service”.
"Identify your users and understand their ongoing needs.
- Conduct holistic research on the real needs of your users from their point of view and what that means for the design of the service..." |
The Tech Terms Computer Dictionary
https://www.digital.govt.nz/standards-and-guidance/digital-service-design-standard/principles/#Principles-1 |
| Engine (Software Engine) |
Software components an order of magnitude more complex than ordinary modules of software.
Typically software modules pass data to a software engine and the engine transforms data into a different state.
See also Calculator and Agent |
Examples of software engines include workflow engines, inference engines, search engines, and relational database engines.
Normally software engines can be tuned - like a car engine (unlike less sophisticated software which requires refactoring to improve it).
|
"A game engine is a software development environment designed for people to build video games. Developers use them to create games for consoles, mobile devices, and personal computers.'
"Other examples of engines are Audio, Video, Image heavy processing engines and specialized proprietary rendering engines in Hollywood films which require lot of visual optimizations." |
|
| Entity |
A thing with distinct and independent existence |
An entity is something that exists separately from other things and has a clear identity of its own. An entity can include an individual, business, device or system. |
Example: “Although Government buildings are in separate locations, Government is considered to be a single entity” |
Collins English Dictionary |
| Epic |
A large feature written as a user story that needs to be broken down into more bite sized pieces of work and prioritised in the product backlog, that the scrum team use to deliver a product. |
An epic is a large user story or feature that cannot be delivered as defined within a single sprint or is large enough that it can be split into smaller user stories. It can also be represented by a short phrase instead of a user story depending on what it is.
Epics give you the ability to track large, loosely defined ideas in the backlog without the need to overpopulate your backlog with multiple items, if the idea isn't fully formed yet. At the point that it's more formed you are able to break the epic down into smaller user stories and track against the delivery of the epic. |
Epic:
As a user, I can backup my entire hard drive.
User stories:
As a power user, I can specify files or folders to backup based on file size, date created and date modified.
As a user, I can indicate folders not to backup so that my backup drive isn't filled up with things I don't need saved. |
https://www.agilealliance.org/glossary/epic/
https://www.mountaingoatsoftware.com/agile/user-stories |
| Estimation |
Estimation is what effort the scrum team think it's going to take to deliver a feature or user story from the product backlog. |
Estimation is what effort the scrum team think it's going to take to deliver a feature or user story from the product backlog.
An estimation also informs how much work the scrum team think they can bring into a sprint and deliver within that timeframe. Estimation can be done a couple of ways, the most basic being tee shirt sizing (small, medium or large) or using Fibonacci. Estimation isn't a measure of time involved to deliver something, but the effort. Estimation is also known as story points, sizing. |
|
https://www.agilealliance.org/glossary/estimation/ |
| Federated Architecture (FA) |
A pattern in enterprise architecture that allows interoperability and information sharing between semi-autonomous de-centrally organized service providers. |
|
|
Modified from Wikipedia |
| Federated Service Delivery (FSD) |
The working name of Result 10, Action 5. It is focused on taking a truly customer-centric view of delivering government services. |
Result 10 completed extensive customer research during which customers told us they experienced a lot of pain points when dealing with government services - including having to approach several different government agencies to get things done. Federated Service Delivery seeks to address these issues by putting customers at the centre of all government service delivery - removing artificial demarcations, particularly around significant life events such as having a baby or embarking on tertiary study.
Federated Service Delivery is closely related to Result 10, Action 4 - "Consolidate and rationalise the government web domain and rewrite service information to make transactions easier to find and use."
See also Federated Architecture (FA) |
"Agencies are being asked to apply a “federated services” model to integrate their services for customers but because there is no reference implementation for this, they are having to undertake the financial and technical risk in interpreting what it means."
"Federated services model: seamless digital services for users, consumable authoritative components (data, content, transaction services, business rules), personalisation?"
"The DSC chose the ‘federated’ term deliberately to reflect the fact they were seeking to build a collaborative, distributed model of integrated services rather than a highly centralised model." |
Introducing Federated Service Delivery
https://www.digital.govt.nz/blog/introducing-federated-service-delivery/
Draft Lab+ work plan (April - June 2017)
https://docs.google.com/presentation/d/16EY6o7udZFjp2DsFEPSZyvWKpS5AlCTv8wflRgPCj8s/edit?usp=sharing |
| Hypothesis |
A provisional idea which is proven to be "true" or "false" through an experiment. |
If you believe something might be true but don’t yet have definitive proof, it is considered a theory (or hypothesis) until that proof is provided
For a hypothesis to be a scientific hypothesis, the scientific method requires that one can verify or test it. Scientists generally base scientific hypotheses on previous observations that cannot satisfactorily be explained with the available scientific theories.
In "entrepreneurial science", a hypothesis is used to formulate provisional ideas within a business setting. The formulated hypothesis is then evaluated where either the hypothesis is proven to be "true" or "false" through an experiment which is either verifiability or falsifiability oriented . |
|
https://en.wikipedia.org/wiki/Hypothesis
For a very formal definition of hypothesis testing:
http://mathworld.wolfram.com/HypothesisTesting.html |
| Hypothesis - Null Hypothesis |
A null hypothesis is the proposition that there is no cause and effect relationship between phenomena or populations. |
Using a null hypothesis is useful because it can be tested and found to be false, which then implies that there is a relationship between the observed data.
It is much easier to disprove a hypothesis than to positively prove one.
A common approach is to reject a null hypothesis if the observed data are significantly unlikely (stats definition) to have occurred if the null hypothesis were true. |
"Hyperactivity is unrelated to eating sugar" is an example of a null hypothesis. If the hypothesis is tested and found to be false, using statistics, then a connection between hyperactivity and sugar ingestion may be indicated. A significance test is the most common statistical test used to establish confidence in a null hypothesis."
"You may be wondering why you would want to test a hypothesis just to find it false. Why not just test an alternate hypothesis and find it true? The short answer is that it is part of the scientific method. In science, propositions are not explicitly "proven." Rather, science uses math to determine the probability that a statement is true or false. It turns out it's much easier to disprove a hypothesis than to positively prove one. Also, while the null hypothesis may be simply stated, there's a good chance the alternate hypothesis is incorrect." |
Wikipedia
https://www.thoughtco.com/definition-of-null-hypothesis-and-examples-605436 |
| Information |
Data that has been processed, aggregated and organized into a more human-friendly format that provides more context. Information is often delivered in the form of data visualisations, reports and dashboards.
See also Data and Insight |
|
|
|
| Innovating at scale |
The collobative practices which create an empowered networked community resulting in value for government and the broader economy. |
Working with the community in an open, cooperative, participative manner - government to working as a keystone member of the community (working with the community to meet the needs of the community). |
|
Service Innovation Toolkit |
| Insight |
Conclusions generated by analyzing information that can influence decisions and drive change.
Design Insights are breakthroughs that reveal behavior patterns and drive bold decisions. By shedding light on behavior patterns, they can point design teams in new directions that would otherwise go unexplored. They are NOT observations, data or user wish or need.
See also Data, Information, and Actionable Insight |
Data, information and insights are not synonyms. Data is raw and unprocessed facts, usually in the form of numbers and text. Information is data that has been processed, aggregated and organized into a more human-friendly format that provides more context. Insights are generated by analyzing information and drawing conclusions.
Design Insights can shape a project during any point in the product development process by revealing behavior patterns that are normally lost, hidden or obscured. By bringing these patterns in view, we can make observations and form connections between them, as well as predict future behaviors. This deep understanding of the true nature and motivations behind user behaviors prevents teams from going too far down wrong paths, and leads us to better ideas, better solutions, and ultimately better products/services. |
"my Fitbit watch gives me all kinds of activity data: steps, BPM (heart beats per minute), and so on. If my watch says I’ve taken 7,442 steps today, this single fact is fairly useless, especially without more context - but my Fitbit app includes a number of data tables and visualizations (information) such as a weekly steps report where I can see how many steps I completed each day. When I analyze this trended information I can see my current trajectory is ahead of what I accomplished the past few days and with a little extra effort in the evening I can reach my daily target (insight: I only need 2,558 more steps in the next 5 hours to reach my daily target). |
https://www.forbes.com/sites/brentdykes/2016/04/26/actionable-insights-the-missing-link-between-data-and-business-value
https://www.techopedia.com/definition/31721/actionable-insight
https://en.wikipedia.org/wiki/Insight
https://hbr.org/2012/09/metrics-are-easy-insights-are-hard
https://zurb.com/design_insights https://thrivethinking.com/2016/03/28/what-is-insight-definition/ |
| Internet of Things (IoT) |
Devices with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction. This includes (but isn't limited to!) cellphones, coffee makers, washing machines, headphones, lights, wearable devices, and components of machines (for example a car engine, or wheel bearing). |
IoT is a big topic at the moment because it can be applied both at a small scale (e.g. automating data collection from components in manufacturing to predict when they will fail), and to things like transportation networks and "smart cities" which can help us reduce waste and improve efficiency for things such as energy use. It has enormous potential to help us measure, understand, and improve how we work and live.
Note:
1) A number of factors mean that the number of connected things is skyrocketing (Gartner estimatres by 2020 there will be over 26 billion connected devices, some say 100 billion). Big contibutors include the cost of connecting to the internet decreasing rapidly, and more and more devices being created with Wi-Fi capabilities (and sensors built in) - again due to costs coming down.
2) The "internet" in the name is misleading because devices may be connected in a home or factory via non-IP (internet) networks (such as "ZigBee") to a router. The impact of these connected devices is typically included when talking about IoT.
3) Many IoT devices use web protocols to communicate (these are a subset of the ways to communicate using the internet), but not all do. |
Emerging Tech Landscape:
"Network-enabled smart devices that use embedded processors, sensors and communication hardware to collect, send and act on data they acquire from their environments" |
https://www.forbes.com/sites/jacobmorgan/2014/05/13/simple-explanation-internet-things-that-anyone-can-understand/#b07ea0d1d091 |
| Lean Canvas |
A strategic tool to synthesise business, project or
product ideas on to one (typically A3) page.
|
A tool used as part of lean startup methodology for developing products, which aims to shorten product development cycles (and achieves this by adopting a combination of hypothesis-driven experimentation, iterative product releases, and validated learning).
|
"A key focus of the Lean Canvas is on understanding the problem to be solved. Most products (product companies) fail, not because they fail to build what they set out to build, but because they waste time, money, and effort building the wrong product. A huge conttibutor to this is a failure to understand the problem at the start." |
Wikipedia
https://blog.leanstack.com/why-lean-canvas-vs-business-model-canvas-af62c0f250f0 |
| Life Event |
A life event is a major event or related series of events that change a person's status or circumstances. |
Examples of life events include giving birth, marriage, divorce, death of spouse, or loss of a job.
When customers contact government in the course of a life event (eg enrolling for tertiary education) they do so in order to achieve a task or goal greater than the scope of individual agency services. |
|
Federated Services Delivery Glossary |
| Logic Mapping (Game Design) |
Logic mapping is a game design tool applicable in a design situation dealing with complex issues that require systemic design or redesign. |
Logic mapping reveals the common threads running through audience experiences. It helps to identify commonalities around issues and motivations, shared between different groups. It aids decision making by revealing the most impactful area where action can be focused.
The Logic Mapping process evolved out of research into the application of positive psychology for the design of serious games. |
|
Logic Mapping — Game Design for Complex Problems
https://medium.com/@driedfrog/logic-mapping-is-a-game-design-tool-dbc4f10a0a1e
Making it easier to buy and sell...
https://www.digital.govt.nz/blog/making-it-easier-to-sell-and-buy-a-property-exploring-the-notice-of-sale-process/ |
| Kanban |
Kanban is a basic workflow that allows people to pull work into their work in progress, when they are ready to take it on. |
Kanban was originally developed for Toyota's manufacturing arm and would resupply products based on customer demands. Over the years this has been repurposed to use with a variety of different teams who want to be able to manage their work in progress with the ability to pull work into their workflow when they need it.
Kanban allows organisations and teams to start with their existing workflows and drive a change on how they deliver work. It creates transparency of the work in progress and allows teams to be able to stop starting and start finishing work.
Kanban is another framework utilitised by Agile. |
|
https://en.wikipedia.org/wiki/Kanban
https://www.agilealliance.org/glossary/kanban/ |
| Minimum Viable Product (MVP) |
A product with just enough features for you to test it with users and check whether those features work (and gather meaningful feedback). |
Multiple prototypes may be created within a Design Discovery or Alpha phase to inform and refine a product of Alpha quality (the MVP). Note that producing a product of Alpha quality differs from running an Alpha phase.
Proof of concepts and prototypes are usually developed and tested within a controlled environment – such as in a workshop or lab workplace – although some prototypes are tested out in the field. Pilots and MVPs, on the other hand, are usually tested in the real world.
Note: there are many sources which reference the (in)famous Dropbox video as an MVP. While the video was a clever way of communicating a concept and gauging interest, the video was not a working product, and therefore not an MVP.
"remember DropBox’s first MVP was a video and there are many more similar examples" |
"Are you looking for purely a build of an MVP (defined by GDS Service Manual as "just enough features for you to test it with users and check whether those features work"), or a full alpha with user testing and refinement?"
"The minimum viable product is that version of a new product a team uses to collect the maximum amount of validated learning about customers with the least effort." |
Australian Digital Transformation Office
https://ausdto.github.io/service-handbook/alpha/4-finishing-alpha/4-1-defining-mvp.html
UK Government Service Manual
https://www.gov.uk/service-manual/agile-delivery/how-the-alpha-phase-works
https://states-of-change.org/stories/proof-of-concept-prototype-pilot-mvp-whats-in-a-name
Hackney Council - Creation of an MVP of the digital service for Ways into Work (see questions)
https://www.digitalmarketplace.service.gov.uk/digital-outcomes-and-specialists/opportunities/2274
Wikipedia https://www.nesta.org.uk/blog/proof-of-concept-prototype-pilot-mvp-whats-in-a-name/ |
| Mixed Reality (MR) |
The merging of real and virtual worlds to produce new environments and visualizations where physical and digital objects co-exist and interact in real time. |
Mixed reality not only overlays, but anchors virtual objects to the real world, and allows the user to interact with the virtual objects.
Mixed reality is generally (26/10/2018) experienced via a headset such as the MS Hololens or Magic Leap.
aka hybrid reality |
|
Wikipedia |
| Pattern Language |
A pattern language is a method of describing good design practices within a field of expertise. |
The term "pattern language" was coined by architect Christopher Alexander and popularized by his book A Pattern Language. - https://en.wikipedia.org/wiki/Pattern_language
The notion of patterns has been adopted by IT to describe good design practices for providing computer systems.
|
|
Federated Services Delivery Glossary |
| Persona |
A representation of a key audience segment used as a design tool to create empathy with a group of real users mixing demographic information with archetypal behaviors in a believable format.
See also Digital Identity - Persona and Behavioural archetypes |
Good personas are a reliable and realistic representation of audience segments for reference based on qualitative + quantitative user research - often including web analytics. They help the team avoid designing a product from a client-as-customer or us-as-customer perspective.
The challenge/weakness with personas can be that they focus on characteristics, and are often created with little insight into the behavior of the people they represent – which opens the door to assumptions by your project team. Personas include demographic details such as age, gender, occupation, education, interests, etc - so they are useful to provide insight into the characteristics of a target audience - but may not include details on behavioral patterns (compare Behavioural Archetypes). |
"Personas help to focus decisions surrounding site components by adding a layer of real-world consideration to the conversation. They also offer a quick and inexpensive way to test and prioritize those features throughout the development process." |
https://www.usability.gov/how-to-and-tools/methods/personas.html
Archetypes not Personas - Pivotal Labs
https://medium.com/interactive-mind/archetypes-not-personas-2e32c8306112
https://smashingideas.com/behavioral-archetypes/
https://www.huffingtonpost.com/entry/why-you-should-find-your-archetype-not-your-persona_us_59b592bfe4b0c50640cd6879
|
| Product Backlog |
The Product Backlog, also known as Backlog is a prioritised list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product and is referenced daily by the scrum team to determine what they need to work on next. |
The product owner is responsbile in ensuring the backlog/product backlog is kept up to date and has all the right information in there for the scrum team use to complete a task. The content is broken up into a story and are prioritised for the scrum team. The product backlog is living and will be constantly changing and evolving on a daily basis and is never complete. |
|
|
| Product Owner
(Rangitira) |
The Product Owner holds the vision for what the scrum team are delivering and ensuring that the maximum of value in a sprint is being delivered. |
The Product Owner (PO) is one of three roles within a Scrum team. The PO holds the vision/value for the project/product and communicates this back to the scrum team and makes sure that they are delivering to the vision. The PO will have a deep understanding on who will be using the the product, but they don't determine how much work the scrum team will do in a sprint or change the goals - but they will determine what the team need to do and controls the backlog for the project. A PO needs to be readily available to the scrum team in order for the team to deliver to the vision. |
|
https://www.mountaingoatsoftware.com/agile/scrum/roles
https://www.scrumalliance.org/agile-resources/scrum-roles-demystified |
| Production Technologies |
Machines that create a tangible physical product that a business can use or sell. These technologies are used in a wide range of industries.
|
Examples include:
- Additive manufacturing (3d printing, cold spraying etc)
- Bio manufacturing (vaccines, detergents..)
- Self assembling components (small powerful electronics, drug delivery..) |
Wikipedia (Self-assembly of nanoparticles)
"Due to the proliferation of nanoparticle synthesis techniques, the study and design of nanoparticle self-assembly has become widespread.[3] The spatial arrangements of these self-assembled nanoparticles can be potentially used to build increasingly complex structures[4] leading to a wide variety of materials that can be used for different purposes." |
Emerging Technology Landscape
https://smallbusiness.chron.com/production-technology-manufacturing-25068.html |
| Proof of concept |
an implementation of a certain method or idea using specific technologies — in order to assess and demonstrate its feasibility and confirm its practical potential.
See also Prototype and MVP. |
The objective of a PoC is to prove the idea and/or technology by exposing a realistic, functional implementation of a subset of functionality. It is usually small, focusing on a particular aspect of the product, and is typically not complete. |
Demo of a concept and how it will work in context (users and system) |
https://medium.com/innovation-machine/is-it-a-prototype-or-an-mvp-well-its-a-proof-of-concept-f8df5bb8940a |
| Prototype |
A prototype is a way to test one part of a complicated system or product. It is an early sample/model built to test a concept or assumption or to act a a thing to be tested and learned from.
See also MVP and Proof of concept and Mock-up and Wireframe.
|
A prototype can take many forms (paper, powerpoint, cardboard and bluetack), and be very low, to very high fidelity.
A model of your idea. An early model can be very simple to test underlying principles; when it comes to the later stage of the design process, a more accurate model is required to refine details of form and function.
What is it useful for?
Physical prototypes help iron out any unanticipated problems with your creative ideas. Prototypes give you insight into how your design will be used, before you create a finished version. |
Nesta table of low-hi fidelity prototyping.
"Physical prototypes are also particularly effective in communicating design ideas to diverse groups of stakeholders." - UK Design Council |
https://www.unhcr.org/innovation/what-is-prototyping-anyway/ https://www.usability.gov/how-to-and-tools/methods/prototyping.html https://www.interaction-design.org/literature/article/design-thinking-get-started-with-prototyping https://www.invisionapp.com/design-defined/prototype/ |
| Quantum Computing |
Computers that use ‘Qubits’ as opposed to binary processing, resulting in a leap in data generation and processing power
|
Computers which work with information which is represented in more than two states. Information is encoded as quantum bits, or qubits, which can exist in superposition. Qubits represent atoms, ions, photons or electrons and their respective control devices that are working together to act as computer memory and a processor. |
|
Emerging Technology Landscape |
| Retrospective
(Titiro whakamuri) |
A session where an Agile team reflects on performance to date, and creates a plan for improvements to be made within the next iteration or Sprint. |
The scrum team meets regularly, usually after the end of each sprint. This time is used to reflect on the most what the sprint team determine were the most significant events/problems that occured during the sprint. They unpack the events/problems that occurred and work together to make and take decisions/experiments to either resolve the issue or take steps to see if they can improve on the issue.
The retrospective is facilitated generally by the scrum master. There are several different approaches for running a retrospective and these sessions can also be tailored to themes that may have come up throughout the sprint. The retrospective meeting can typically run from one to four hours. With the meeting being facilitated it gives the opportuity for everyone on the sprint team to have a voice and be able to speak up. |
|
https://www.agilealliance.org/glossary/heartbeatretro/#q=~(infinite~true~filters~(postType~(~'page~'post~'aa_book~'aa_event_session~'aa_experience_report~'aa_glossary~'aa_research_paper~'aa_video~'aa_podcast)~tags~(~'retrospective))~searchTerm~'~sort~false~sortDirection~'asc~page~1) |
| Robotics |
The design, construction, operation, and use of robots, as well as computer systems for their control, sensory feedback, and information processing.
|
The development of machines that can substitute for humans and replicate human actions. Robots can be used in many situations and for lots of purposes, but have to date most commonly been used in dangerous environments (including bomb detection and deactivation), manufacturing processes, or where humans cannot survive. More recently, machine learning and artificial intelligence are pushing the boundaries of what robots can do - self-driving cars, robot vacuum cleaners, and machines which provide care for hospital patients will all become commonplace in our lifetimes. |
VUW Engineering:
"Advances in machine learning and artificial intelligence are pushing the boundaries of what robots can do. What was once ‘the future’—self-driving cars, robots that clean your room or provide care for hospital patients—is becoming real and even commonplace in our lifetimes." |
Emerging Tech Landscape |
| Scoping |
The initial filtering phase in the Service Innovation Operational Workflow Model where a possible Lab project or interaction is assessed. |
This phase works through framing and scoping to explore and seek insights about the user experience, including the eco-system which they have to navigate. It helps us to define the problem space, our approach, resources required, customer and SME engagement etc. Depending on complexity and previous knowledge this phase could take 1 - 4 weeks. |
"The TEC led Entering Tertiary life event ran over four weeks." |
Service Innovation Lab - Operational Workflow Model
https://docs.google.com/document/d/1vxH0hOLGa9SQGH7xIQnODQXUIqKl7TDa0svCCBAEDAM/edit?usp=sharing
Service Innovation Lab – Our Services
https://docs.google.com/document/d/1z9UM52fDCtXFFVnwjgCjwxtgynrC-iFut7aBrhFSVqg/edit?usp=sharing |
| Scoping - Assessment Scoping |
The first stage of a two part Scoping phase in which an asessment is made as to whether the project should be taken on by the Lab. |
An assessment about whether the Lab should proceed with the project based on considerations such as whether the Lab is well positioned to add value, and whether the team/agency/interested party are ready to engage and commit with the Lab and its processes. The output from this stage is a (rapid) decision about whether the project will become part of the work-programme, and what the next step (after Project Scoping which always follows immediately) should be (e.g. Research Discovery or Alpha). This decision is made based by the Lab leadership team based on a one-page document. |
|
Service Innovation Lab - Operational Workflow Model
https://docs.google.com/document/d/1vxH0hOLGa9SQGH7xIQnODQXUIqKl7TDa0svCCBAEDAM/edit?usp=sharing |
| Scoping - Project Scoping |
The second stage of a two part Scoping phase which involves a deeper dive into the potential of the project. This is the first stage at which a project is considered part of the work-programme. |
This stage defines the project scope in more detail, including key areas of focus, resources and people required, and the commitment from all parties required for completion. This is captured in a project scope document. |
|
Service Innovation Lab - Operational Workflow Model
https://docs.google.com/document/d/1vxH0hOLGa9SQGH7xIQnODQXUIqKl7TDa0svCCBAEDAM/edit?usp=sharing |
| Scrum |
Scrum is a simple framework that enables teams to collaborate effectively on solutions to complex problems. |
Scrum is a framework (with principles and practices) that helps teams to work through complex adaptive problems, by breaking them down into small features that are be delivered in small managable pieces in short timeframes or sprint's. This approach allows for fast feedback, and the opportunity to review as a team how they work together and identify areas they need to improve. By the end of the sprint the team should be delivering features or products of the highest value and features or products that do 'just enough' to get the job done.
the scrum team self organises on a daily basis with a stand-up, there are regular backlog refinement sessions, sprint planning, retrospectives to allow for transparency and support to remove anything stopping them from completing a feature or story.
It's work noting that scrum is one of several agile frameworks. |
|
https://www.scrum.org/resources/what-is-scrum
https://www.scrumalliance.org
https://www.agilealliance.org/glossary/scrum/ |
| Scrumban |
Scrumban uses the prescriptive nature of Scrum allowing the team to be agile and the process of improvement from Kanban allowing the sprint team to continually improve and pull work as it's needed from a prioritised backlog, but limiting their work in progress |
Scrumban uses the best parts of Scrum and Kanban allowing a team to deliver their projects. It uses the prescriptive nature of Scrum allowing the sprint team to be agile and the process of improvement from Kanban allowing the team to continually improve and pull work as it's needed from a prioritised backlog, but limiting their work in progress. The approach allows sprint teams to look at things in a lean way, organised around teams and allows for timeboxing where required. |
|
https://www.agilealliance.org/what-is-scrumban/
https://en.wikipedia.org/wiki/Scrumban |
| Scrum Master
(Toa Kakari) |
The Scrum Master's role is to protect the team from distractions and helping them remove any 'blocks' they might have to achieving the goal of the sprint. |
The Scrum Master is not a project manager. The role of the Scrum Master is one of three within a Scrum team. The Scrum Master's role is to protect the team from distractions and helping them remove any 'blocks' they might have to achieving the goal of the sprint. The Scrum Master will also work closely with the team to ensure the Scrum is being applied correctly.
The difference between the role of project manager and scrum master is that the scrum master allows the team to self organise and come to their own decisions and supports the product owner with the handling of reports and budgets. The project manager retains command and control over the team and handles all the reporting and budgeting associated with a project. |
|
https://www.agilealliance.org/glossary/scrum-master |
| Scrum team |
The core team that will deliver the project or product that is being worked on. |
The scrum team is one of three roles within the scrum. They are a a cross functional team who are self organising and have been formed to delivier a project. There are a range of different disciplines that might be involved, such as: product owner, scrum master, designers (UX / UI), developers, testers, business analysts. Some of these team members will be part of the scrum for the duration of the project, others will come and go as they are required. |
|
|
| Serious Games |
Games that are designed for a primary purpose other than pure entertainment |
|
|
Wikipedia |
| Service Innovation Lab Work Programme |
The programme of work developed by the Service Innovation Reference Group (SIRG), and committed to by the Service Innovation Lab. |
The programme is focused on supporting the government priorities: building quality public services, improving access to core services, child poverty, homelessness, supporting families and sustainable economic development. |
|
Service Innovation Work Programme 2018 2019 with detail
https://drive.google.com/open?id=1fLO2VbHkHccF4A1ixoTsRkNBgF8hzSFU |
| Service Innovation Operational Workflow Model |
The process followed by the Service Innovation Lab to deliver the Service Innovation Lab Work Programme. |
The workflow model follows four main stages: Scoping, Discovery, Alpha, Beta. |
|
Service Innovation Lab - Operational Workflow Model
https://docs.google.com/document/d/1vxH0hOLGa9SQGH7xIQnODQXUIqKl7TDa0svCCBAEDAM/edit?usp=sharing |
| Service Innovation Reference Group (SIRG) |
Provides support to SIWG and develops + maintains the detail of the work programme and initiatives. |
Established in 2015, this group comprises some of the members of the old FSD Working Group as well as some new members. |
|
Introducing Federated Service Delivery
https://www.digital.govt.nz/blog/introducing-federated-service-delivery/ |
| Service Innovation Working Group (SIWG) |
Provide governance to the Service Innovation (previously "Result 10") programme of work.
aka (SWIG) via typos and in common verbal usage so it can be distinguished from SIRG |
Replaced the DSC in 2015. Membership was expanded to include Ministry of Education, Ministry of Health, Justice, ACC and (more recently) Statistics NZ, NZTA, Department of Conservation and New Zealand Customs Service withdrew.
|
"A proposal for seed funding for the first phase of implementation has been approved by SIWG, and is the best opportunity to demonstrate the potential of the FSD model in a life event initiative in the near term." |
|
| Sizing |
See Estimation |
See Estimation |
|
|
| Spatial Computing |
The practice of using physical space to send input to and receive output from a computer.
|
Spatial computing encompasses everything needed to let people move around in a digital 3D world — software and technology associated with artificial intelligence, including machine learning and natural language processing; computer vision; augmented reality; virtual reality; mixed reality; and all other apps that support the creation and maintenance of a digital 3D world. |
Emerging Tech Landscape:
"the practice of using physical space to send input to and receive output from a computer"
"Our thesis is that for the next 24 months the first places you’ll see successful deployments of Spatial Computing are mostly gaming or enterprise uses, like surgery, logistics, mining, architecture, and car design, training, and many more." |
https://infiniteretina.com/a-new-definition-of-spatial-computing-the-fourth-paradigm-2/
https://venturebeat.com/2019/03/04/infinite-retina-will-make-apps-and-experiences-for-spatial-computing/ |
| Sprint |
A sprint (or iteration) is the basic unit of development in Scrum (one form of Agile). Sprints are generally fixed in duration for the length of a project, and are typically 1-2 weeks, but can be longer.
|
A Sprint typically starts with sprint planning that defines a sprint backlog (identifying the work for the sprint) and a sprint goal. Each sprint ends with a sprint review/showcase to show progress to stakeholders, and a sprint Retrospective.
Scrum places a real emphasis on having a working product (or new set of features) at the end of the sprint. In the case of software, this is likely to mean that software has been fully integrated, tested and documented, and is potentially shippable. |
|
Wikipedia |
| Sprint Backlog |
The sprint backlog is the subset of product backlog that the sprint team targets to deliver during a sprint to acheive the sprint goal and the feature /product they are working towards to deliver |
The sprint backlog is the subset of product backlog that the sprint team targets to deliver during a sprint to acheive the sprint goal and the feature /product they are working towards to deliver. The sprint backlog is agreed by the sprint team at sprint planning.
The sprint backlog is then represented on a digital or physical board to create visibility and transparency of what the team are working on. The items in the backlog are what the sprint team focuses on for that sprint and all work should be represented there. If new work is identified as part of the sprint, the sprint team have a discussion on the requirements and agree whether it can be bought into the sprint and agree what can drop out of the sprint. |
|
https://www.agilealliance.org/glossary/sprint-backlog
https://www.scrum.org/resources/what-is-a-sprint-backlog
https://www.mountaingoatsoftware.com/agile/scrum/scrum-tools/sprint-backlog |
| Sprint Board
(Papa Kōrero) |
The sprint board tool that sprint teams use to make their sprint backlog items visible. This is used in conjunction with the daily stand-up that helps team remain focused on the work at hand. |
The sprint board tool that sprint teams use to make their sprint backlog items visible. This is used in conjunction with the daily stand-up that helps team remain focused on the work at hand.
In it's basic form it creates a workflow that gives the sprint team the ability to pull new work into their workflow. Generally this is made up of the following columns which the sprint team can pull a story into.
Backlog (the work that needs to be done)
Doing (the work that is currently in progress)
Blocked (work can't be completed due to something stopping this)
Review (ready for the product owner to review or other members of the team)
Done (work is approved and completed) |
|
|
| Sprint Planning |
Sprint planning is an event held on the first day of the new sprint. During this time the sprint team reviews and agrees the product backlog items they will work on during that sprint. |
Sprint planning is an event held on the first day of the new sprint. During this time the sprint team reviews and agrees the product backlog items they will work on during that sprint. The sprint team talks through the approach to delivering these backlog items and what the goal of the sprint will be. Sprint planning is attended by:
- the product owner takes the team through the items for the upcoming sprint,
- the sprint team review the items, ask questions and determine how many items they can bring into the sprint
- the scrum master facilitates the session |
|
https://www.agilealliance.org/glossary/sprint-planning
https://www.scrum.org/resources/what-is-sprint-planning |
| Story Points |
See Estimation |
See Estimation |
|
|
| Symbiotic Applications |
Applications focused on the convergence of human augmentation with the increasing intelligence and awareness of artifacts, leading towards a symbiosis of humans and machines.
|
Examples include:
- Wearable devices
- Brain-computer interfaces
- Smart prosthetics |
https://www.ieee.org
"Symbiotic Autonomous Systems are poised to have a revolutionary impact on society over the coming years"
Professor Manuela Veloso:
"a future in which humans and intelligent systems are inseparable, bound together in a continual exchange of information and goals that she calls “symbiotic autonomy.” |
https://www.crunchbase.com/organization/ieee-symbiotic-autonomous-systems#section-overview
https://www.theverge.com/a/verge-2021/humanity-and-ai-will-be-inseparable |
| Symposium |
a fancy academic conference (which sometimes includes a feast and a sacrifice to greek gods) |
Symposiums are generally smaller than conferences - and less hands-on than a workshop. |
|
|
| System |
A set of connected items or devices (i.e. computer equipment and programs) that operate together for a particular purpose |
A set of detailed methods, procedures and routines created to carry out a specific activity, perform a duty, or solve a problem. An organized, purposeful structure that consists of interrelated and interdependent elements. |
“An improved health system would benefit all New Zealanders”. |
Business Dictionary |
| User
(Kaiwhakamahi) |
A user is a person or thing that uses something such as a place, facility, product, or machine.
The Entity (Individual, Business, System or Device) participating in an online transaction. |
An entity (Individual, business, system or device) that has authority to use an application, equipment, facility, process, or system, or one who consumes or employs a good or service to obtain a benefit or to solve a problem, and who may or may not be the actual purchaser of the item.
See ‘Entity’, ‘Identity’, ‘Business’, ‘System’ and ‘Device’. |
“The user logs on to their banking website before accessing their bank account”.
"Your users have multiple online personas — can they all log in to your site?" |
Business Dictionary, Collins Dictionary |
| User Story |
User stories are short, simple descriptions of a feature told (usually) from the perspective of the person who desires the new feature/item - generally at user or customer of the the work you are delivering. |
User stories are short, simple descriptions of a feature told (usually) from the perspective of the person who desires the new feature/item - generally at user or customer of the the work you are delivering. They are generally written in the voice of the customer and will include acceptance criteria required to deliver that story. User stories usually follow a template: As a type of user , I want some goal so that some reason . A story is written for a small piece of work that can be completed independently from any of the other stories in the sprint backlog or product backlog. Each story has it's own 'card' that is represented on the sprint board.
Acceptance Criteria is additional information that provides the sprint team with more detail about how benefits will be delivered as part of this work being done and something for the product owner to check against when that story has been worked on and that work is ready to be reviewed. Stories are sometimes broken down further into tasks e.g. the steps required to complete the story.
Anyone on the sprint team can write the stories, they are generally reviewed and prioritised by the product owner. The user stories relate directly back to the epic's that the sprint team are delivering for.
|
Epic:
As a user, I can backup my entire hard drive.
User stories:
As a power user, I can specify files or folders to backup based on file size, date created and date modified.
As a user, I can indicate folders not to backup so that my backup drive isn't filled up with things I don't need saved. |
https://www.mountaingoatsoftware.com/agile/user-stories
https://en.wikipedia.org/wiki/User_story
https://www.boost.co.nz/blog/2018/06/user-stories-in-scrum |
| Virtual reality (VR) |
An experience which immerses users in a fully artificial digital environment.
Primary via a headset |
|
|
Wikipedia |
| Workshop |
Working as a collective on task development within a timebox |
Typically involves activites to help generate outputs and outcomes that will further the work. Roles required - participants, facilitator, documentor. Workshops may require independant parties to facilitate in-order to progess or not bias the work being done. Different to meetings which are centered around communication of ideas not developing them. Meetings are informative and invovle gathering evidence to inform or make decisions |
|
https://www.linkedin.com/pulse/meetings-vs-workshops-paul-nunesdea/ http://www.evenues.com/event-planning-guide/types-of-meetings-and-events |
