[02/Methodology/01]

User stories focused on business value

To explain the required details of the mockup

Section after the graphical mockup section

To support sprint planning and tracking

Business value

By modifying the process template

Scrum

To shoot software features through the layers of the software system

Implement functional requirements first, then non-functional requirements

5 to 9 team members

Product owner, developers, and Scrum master

To produce new reports, dashboards, or measures

Scrum

Flexibility

To introduce Agile development methodologies

Organization and execution of Data Vault 2.0 projects using Azure DevOps

To demonstrate the feasibility of the project

Software developers with Scrum experience

Project manager

To define the activities required for information delivery

Dealing with obstacles in the project

To prevent idle time

To develop the dashboard at the end of the sprint

To improve the development process

Creating a backlog item with all the required sub-tasks from the sprint plan example

Add, remove, or change the existing sub-tasks

Improvements discussed in the retrospective meeting

Data Vault 2.0 methodology

What went well, what didn’t go well, and how the process should be improved

The activity itself

Scrum

Product owner, Scrum master, and developers

To shoot software features through the layers of the software system

7-9 team members

To facilitate the Scrum ceremonies

To track the progress of the team's tasks

Data Vault 2.0 projects

It allows for extensibility of the model

It was in line with their strategy to introduce Agile development methodologies

Ensuring the team follows Scrum practices

The inclusion of aspects from other methodologies

To start with a small-scale model before expanding

Project manager

To establish a pattern during the sprint

Use blueprints and organized production lines

To build the dashboard

To manage the project

To improve the development process

The graphical mockup section

To visualize the sprint plan

Using information requirements

To document the functionality to be implemented

To facilitate the Scrum process

Improved data integration

To track the progress of tasks in a Scrum team

To create a template with all the required sub-tasks from the sprint plan example

To discuss what went well, what didn't go well, and how the development process can be improved

To model and load a data analytical platform on the Azure cloud

To facilitate the Scrum process and ensure the team adheres to Scrum principles

To show how the data warehouse should look and function

True

True

True

True

True

True

True

True

True

True

False

False

True

False

True

True

False

True

False

False

True

True

False

True

True

True

True

True

True

False

True

True

True

True

True

False

False

False

True

True

False

True

True

True

True

True

True

True

True

True

True

False

False

True

True

True

False

False

False

True

Data Vault 2.0 = Model that allows for step-by-step extension of the model by new entities Scrum = Methodology that the Data Vault 2.0 methodology is based on Data Vault 2.0 projects = Often use Agile methodologies such as Scrum Scrum Master = Role in a Data Vault 2.0 team responsible for managing the project

Deployment of the data analytics platform = Function that will be discussed in subsequent articles of this ongoing blog series Organization and successful execution of Data Vault 2.0 projects = Focus of this article Structure of information requirements = Can be customized in Azure DevOps

Proof of concept (PoC) = Small initial model that most clients at Scalefree start with Raw Data Vault = Part of the model where additional source data sets are added in subsequent iterations Business Vault = Part of the model where transformation logic is added in subsequent iterations Data Vault 2.0 = Model that is often used with Agile methodologies such as Scrum

Scrum Master = Role that should find this article especially useful Dashboard Designer = Works on the dashboard after the sprint is over Generalized Developer = Part of the Data Vault team

Scrum = Basis of the Data Vault 2.0 methodology Agile = Often used in conjunction with Data Vault 2.0 Function Point Analysis = Method used by a specific role in a Data Vault team

Data Vault 2.0 Model = Has the advantage of extensibility User Stories = Should be focused on business value Scrum Board = Organized to show direct business value and typically has fewer cards

Automation engineer = Responsible for automating tasks and processes Dashboard designer = Responsible for designing and developing dashboards Project manager = Responsible for managing the project and effort estimation Scrum master = Responsible for dealing with obstacles in the project and organizing meetings

Sprint plan = Defines the activities required to deliver the requested information, including the sequence and dependencies Data provisioning = The addition of source systems to the data lake Raw Data Vault = One of the upstream layers that must be built before the dashboard Business Vault = One of the upstream layers that must be built before the dashboard

Production street = A metaphor for the unorganized process of building data warehouses and Big Data projects Blueprint = A metaphor for the sprint plan, which defines the activities and sequence in the information delivery process Sprint type = A specific type of sprint plan that defines the activities for a particular aspect of the project Retrospective meeting = A meeting where the goal is to improve the development process

True = The sprint plan in a Data Vault team acts as the blueprint for the information delivery process False = The dashboard designer in a Data Vault team can only work on the dashboard after the sprint is over

Effort estimation using function point analysis = A responsibility of the project manager in a Data Vault team Data Vault 2.0 model = Allows for step-by-step extension of the model by new entities Retrospective meeting = Used to improve the development process in Data Vault 2.0 projects Sprint plan = Defines the activities required to deliver the requested information in a Data Vault team

Scrum master = Not responsible for managing the project, but dealing with obstacles and organizing meetings Sprint plan = Acts as the blueprint for the information delivery process in a Data Vault team Project manager = Responsible for managing the project and effort estimation in a Data Vault team Data Vault 2.0 = Often used in conjunction with Agile methodologies such as Scrum

Tracer bullet approach = A concept used in software development to 'shoot' software features one by one through the layers of the software system Sprint = A time-boxed iteration used in Data Vault 2.0 projects to develop the data analytics platform Scrum of Scrum = A method often used in Data Vault 2.0 projects to better synchronize with other Agile teams, including software development teams of the operational source systems Data Cleaning = An example of business value that could be implemented in a Data Vault 2.0 project

Product Owner = Responsible for defining and prioritizing the backlog items Developers = Responsible for building the technical platform and implementing the functional and non-functional requirements Scrum Master = Responsible for ensuring that the Scrum framework is followed and facilitating the team's progress Dashboard Designer = Responsible for designing the dashboards for the data analytics platform

Backlog = A list of all desired features, enhancements, and bug fixes for the data analytics platform Functional Requirements = Requirements that specify what the system should do Non-Functional Requirements = Requirements that specify how the system should be Scrum Board = A visual representation of the work to be done and the work that has been completed in the sprint

Data Vault 2.0 = A methodology based on Scrum that is used for building data warehouses Sprint Plan = A blueprint for the information delivery process in a Data Vault team Retrospective = A meeting at the end of the sprint to improve the development process Product Owner = The role responsible for defining and prioritizing the backlog items

Data Lake = A secondary reason for setting up a budget for an analytical data platform Business Value = The focus of the team in a Data Vault 2.0 project, such as a new report, dashboard, or a new measure to be calculated Technical Platform = The platform that is built by the team to implement the business value Data Flows = The implementation of these for new functional requirements often influences the technical implementation

Product Owner = Responsible for defining and prioritizing the backlog items Developers = Responsible for building the technical platform and implementing the functional and non-functional requirements Scrum Master = Responsible for ensuring that the Scrum framework is followed and facilitating the team's progress Dashboard Designer = Responsible for designing the dashboards for the data analytics platform

Graphical mockup = An Excel spreadsheet with artificial information, a Visio diagram or a screenshot from a legacy report KPI descriptions = Instructions to calculate the measures, often referring to KPI tree definitions Data sources = A list often described in more detail in an external document or Wiki Test cases for user acceptance test (UAT) = A detailed list of test cases for the UAT

Sprint plan = Acts as the blueprint for the information delivery process Scrum/Kanban board = Used to show direct business value and typically has fewer cards Backlog items = Used to document the functionality to be implemented using the information requirement template Process template = Modified in the organizational settings to reflect the structure of the information requirement

CMMI = One of the methodologies supported by Azure DevOps Services for project management Scrum = Used in Data Vault 2.0 projects to establish the continuous delivery of information assets Agile = One of the other approaches supported by Azure DevOps Services for project management Data Vault 2.0 = A methodology that combines aspects of Scrum with other approaches in a data warehousing context

Project Manager = Responsible for managing the project and adjusting the structure to the organization's needs Scrum Master = Responsible for establishing the continuous delivery of information assets and supporting sprint types and plans Dashboard Designer = Works on the dashboard after the sprint is over Business User = Should be able to describe relevant details of the mockup

Information requirement = More closely related to traditional software requirements where all necessary detail is described but focused on one functional requirement User story = Defines the functionality from the business user’s perspective and should be focused on the business value Sprint = A time-boxed iteration of work Test cases = Used for the user acceptance test (UAT)

Scrum / Kanban board = Used for the user stories and the requirements management in Data Vault 2.0 projects Project management = One of the services provided by Azure DevOps Services Requirements management = One of the services provided by Azure DevOps Services Version control = One of the services provided by Azure DevOps Services

Scrum board = An organized board that shows direct business value and typically has fewer cards Sprint plan = Acts as the blueprint for the information delivery process in a Data Vault team 1-Click Child-Links = A free plug-in available on the Visual Studio Marketplace that can be used as an alternative approach for configuring sub-tasks in the copy of the work item Retrospective meeting = A meeting where the team discusses what went well, what didn’t go well, and how the process should be improved

Data Vault 2.0 = Based on the Scrum methodology and includes aspects from other methodologies Scrum = A methodology used to improve the development process by conducting retrospective meetings Scrum/Kanban board in Azure DevOps = Used to manage and track work items in a project 1-Click Child-Links = A plug-in that can be used to modify the structure of sub-tasks in a work item

Product owner = Responsible for effort estimation using function point analysis Developers = Work on some smaller tasks and non-functional requirements, which are represented by their own cards on the Scrum board Scrum master = Responsible for ensuring the template becomes stable after a number of sprints Dashboard designer = Can work on the dashboard before the sprint is over

Template = Used to create a backlog item and prepare it with all the required sub-tasks Sub-tasks = Configured in the template and can be added, removed or changed in the copy of the work item Sprint types = Require different sprint plans and work item templates Retrospective meeting = Can influence the defined sub-tasks in the template work item

Scrum board = Shows direct business value and typically has much fewer cards 1 business value = The team's focus in a Data Vault 2.0 project 1 card = Represents the one business value on the Scrum board Non-functional requirements = Represented by their own cards on the Scrum board

Sprint plan = Acts as the blueprint for the information delivery process in a Data Vault team 1-Click Child-Links = A free plug-in available on the Visual Studio Marketplace that can be used as an alternative approach for configuring sub-tasks in the copy of the work item Retrospective meeting = A meeting where the team discusses what went well, what didn’t go well, and how the process should be improved Scrum board = An organized board that shows direct business value and typically has fewer cards

Data Vault 2.0 = A data modeling method that is designed to provide long-term historical storage of data coming in from multiple operational systems Scrum = An agile framework that is used to manage complex product development Sprint = A time-boxed period during which specific work has to be completed and made ready for review Product Owner = The person responsible for maximizing the value of the product and the work of the development team

Product Owner = Maximizes the value of the product and the work of the development team Developers = Responsible for building the technical platform Scrum Master = Responsible for ensuring that Scrum is understood and enacted

Data Vault 2.0 = A data modeling approach that is designed to provide long-term historical storage of data coming in from multiple operational systems Sprint Planning = A meeting where the team decides which items from the product backlog they will work on during the upcoming sprint Sprint Review = A meeting where the team demonstrates the work that they have completed during the sprint Retrospective = A meeting where the team reflects on their work and identifies ways to improve

Data Warehouse = A system used for reporting and data analysis Data Vault = A data modeling method that is designed to provide long-term historical storage of data coming in from multiple operational systems Operational Source System = The system that generates the data that is being analyzed Business Value = The value that a business expects to gain from a particular project or activity

Data Vault 2.0 = A data modeling method that is designed to provide long-term historical storage of data coming in from multiple operational systems Scrum = An agile framework that is used to manage complex product development Software Development = The process of creating software applications Agile Delivery = An approach to project management that is characterized by the division of tasks into short phases of work and frequent reassessment and adaptation of plans

Scrum Board = Used to show direct business value and typically has fewer cards in Data Vault 2.0 projects Sprint Plan = Acts as the blueprint for the information delivery process Retrospective Meeting = A meeting where the team reflects on their work and identifies ways to improve Product Owner = The person responsible for maximizing the value of the product and the work of the development team

Data Vault 2.0 = A model that allows step-by-step extension of the model by new entities Agile methodologies = Often used with Data Vault 2.0, such as Scrum Proof of concept (PoC) = A small initial model that is extended in subsequent iterations Scrum = A methodology that Data Vault 2.0 is based on, but also includes aspects from other methodologies

Scrum Master = Responsible for effort estimation using function point analysis Product Owner = Responsible for creating backlog items Developers = Responsible for implementing new business requirements Dashboard Designer = Responsible for designing the dashboard

Scrum = Basis for the Data Vault 2.0 methodology, but also includes aspects from other methodologies Kanban = Used to show direct business value and typically has fewer cards in Azure DevOps Agile = Often used with Data Vault 2.0 Waterfall = Not mentioned in the text as being used in a Data Vault 2.0 project

Information requirements = More closely related to traditional software requirements Data Vault 2.0 = Model that is often used with Agile methodologies Scrum = Methodology that Data Vault 2.0 is based on Proof of concept (PoC) = Small initial model that is later extended

Sprint plan = Blueprint for the information delivery process in a Data Vault team Backlog items = Created by the Product Owner in Data Vault 2.0 projects Dashboard = Designed by the Dashboard Designer in a Data Vault team Tracer bullet approach = Used in both software development and the Data Vault 2.0 methodology

Scrum/Kanban board = Used to show direct business value and typically has fewer cards in Data Vault 2.0 projects Project management = One of the services provided by Azure DevOps Services Requirements management = One of the services provided by Azure DevOps Services Automated builds = One of the services provided by Azure DevOps Services

Automation engineer = Responsible for automating data processes and tasks Data modeler = Responsible for designing the data model for the Data Vault Tester = Responsible for ensuring the quality of the developed artifacts Dashboard designer = Responsible for designing and developing the dashboard

Sprint plan = Acts as the blueprint for the information delivery process Data provisioning = The addition of source systems to the data lake Business Vault = A layer in the Data Vault that contains the transformed and integrated data Information mart = A layer in the Data Vault that provides data for reporting and analysis

Effort estimation using function point analysis = A responsibility of the project manager in a Data Vault team Retrospective meeting = A meeting where the team discusses and improves the development process Tracer bullet approach = An approach used to validate technical feasibility and reduce project risks Non-functional artifact = An artifact that is not directly related to the main functionality, but adds value to the project

Technical debt = Issues or problems in the code that need to be fixed later Data Vault team = A team that consists of specialized roles instead of a generalized developer role Blueprints and organized production lines = Used by car makers for mass production, in contrast to how many data warehouses and Big Data projects function Sprint type = A specific type of sprint plan that defines the activities related to a specific goal or objective

Project manager = Responsible for managing the project and maintaining sprint plans Scrum master = Not a role in a Data Vault team, as it uses a project manager instead Product owner = Responsible for prioritizing and defining the requirements Developer = A generalized role that is not used in a Data Vault team

User story = A brief and informal description of a feature or functionality Graphical mockup = A visual representation of the user interface or system design Information requirement template = A document that captures the information needs of the organization Deployment of new functionalities into production = An issue that is often optimized over time in Data Vault 2.0 projects

User story = Defines the functionality from the business user’s perspective and should be focused on the business value Information requirement = More closely related to traditional software requirements where all necessary detail is described but focused on one functional requirement Graphical mockup = An Excel spreadsheet with artificial information, a Visio diagram or a screenshot from a legacy report Sprint plan = Acts as the blueprint for the information delivery process

Data lake = The target for data in its rawest form Raw Data Vault = Contains the raw, unprocessed, uncleaned, and untransformed data Hubs = Key business objects Satellites = Contain descriptive attributes of the business objects

Sprint = A time-boxed period during which specific work has to be completed and made ready for review Scrum board = Organized to show direct business value and typically has fewer cards User acceptance test (UAT) = A detailed list of test cases for the user acceptance test Dashboard designer = Responsible for designing and implementing the dashboard

CMMI = A capability maturity model integration for process improvement Scrum = Used to establish the continuous delivery of information assets Kanban = Can be used for the user stories and the requirements management Agile = Another approach used in Data Vault 2.0 projects

Product owner = Responsible for defining and prioritizing the product backlog Developers = Responsible for implementing the functionality Scrum master = Responsible for ensuring the team follows the Scrum process and removing any obstacles that may hinder the team's progress Dashboard designer = Responsible for designing and implementing the dashboard

Data Vault 2.0 = A data modeling methodology that is designed to provide historical, traceable, and auditable data Sprint planning = A meeting where the team determines the product backlog items they will work on during the upcoming sprint Retrospective = A meeting held at the end of the sprint to review what went well, what could be improved, and how to make those improvements User story card = A card where the front could be the introductory user story and the details could be on the back

1-Click Child-Links = A free plug-in available on the Visual Studio Marketplace that allows teams to modify the structure of their sub-tasks in the copy of the work item Sprint plan = The blueprint for the information delivery process in a Data Vault team Retrospective meeting = A meeting conducted in the Data Vault 2.0 methodology, just like in Scrum, to improve the development process Scrum board = Organized to show direct business value and typically has much fewer cards in a Data Vault 2.0 project

Template = Left on the Scrum board for later use when new work items should be created in a Data Vault 2.0 project Sub-tasks = Configured as a backlog item in a Data Vault 2.0 project, using the template with all the required sub-tasks from the sprint plan Sprint type = Requires a different sprint plan and work item template in a Data Vault 2.0 project 1 Business value = The team should focus on producing this on the Scrum board in a Data Vault 2.0 project

Scrum master = Responsible for ensuring that the team is following the Scrum methodology and the Data Vault 2.0 practices Developer = Responsible for implementing the work items on the Scrum board in a Data Vault 2.0 project Product owner = Responsible for prioritizing the work items on the Scrum board in a Data Vault 2.0 project Tester = Responsible for verifying the implemented work items in a Data Vault 2.0 project

Data Vault 2.0 = A data modeling method that is designed to provide long-term historical storage of data from different sources Scrum = An Agile framework for managing work in software development Sprint = A time-boxed period during which a specific task or set of tasks is completed Backlog = A list of tasks that need to be completed in a project

Graphical mockup = A section that includes visual representations of the data model in a Data Vault 2.0 project KPI descriptions = A section that provides a detailed explanation of the key performance indicators used in a Data Vault 2.0 project Data sources = A section that lists all the sources of data used in a Data Vault 2.0 project Test cases = A section that includes the scenarios and steps to be executed to verify the data model in a Data Vault 2.0 project

Sprint planning = A function in Azure DevOps that allows the team to plan the work for the upcoming sprint Sprint review = A function in Azure DevOps that allows the team to present the work done during the sprint to stakeholders Retrospective = A function in Azure DevOps that allows the team to reflect on the previous sprint and identify areas for improvement Scrum board = A function in Azure DevOps that provides a visual representation of the work to be done in the current sprint