Real-World Data Governance Webinar: Agile and Data Governance - Bridging the Gap

1
Copyright © 2012 Robert S. Seiner – KIK Consulting & Educational Services / TDAN.com
Non-Invasive Data Governance™ is a trademark of Robert S. Seiner & KIK Consulting
Twitter About This Webinar at #RWDG
1
#RWDG
Real-World Data Governance
Agile and Data Governance –
Bridging the Gap
Monthly Webinar Series Hosted by DATAVERSITY
Robert S. Seiner – KIK Consulting / TDAN.com
January 15, 2015 – 2:00 p.m. EST
Robert S. Seiner
KIK Consulting & Educational Services – KIKconsulting.com
The Data Administration Newsletter – TDAN.com

22
#RWDG
2
• Non-Invasive Data Governance:
The Path of Least Resistance and Greatest Success
– ISBN 9781935504856 / Technics Publishing – September 1
• KIKConsulting.com
Home of Non-Invasive Data Governance™
• DATAVERSITY Events
Enterprise Data World 2015
Progressive Topics in Data Governance: Big Data, Agile and the IoT
– Half-Day Tutorial – March 30
Bridging the Gap
Current Events

33
#RWDG
3
• Real-World Data Governance – Monthly Webinar Series
– February 19, 2015 – Data Governance Roles & Responsibilities
– March 19, 2015 – Data Governance Best Practice Criteria
– Third Thursday of Every Month at 2pm EST
– Register On-Line at DATAVERSITY.net or KIKConsulting.com
Bridging the Gap
Upcoming Webinars

44
#RWDG
4
• The concepts of Agile Software Development have been applied in many
ways in many organizations with differing levels of success. Nobody is
surprised that Agile Methods and Data Governance Methods can be at
odds with each other. But still they are doing their best to coexist.
– Can Data Governance be applied to Agile projects?
– Can Data Governance be applied in an Agile way?
– These are two fascinating questions.
Bridging the Gap
Abstract

55
#RWDG
5
• This session focuses on discovering ways to bridge the gap.
• This session will cover:
– Data Governance and Agile Definitions
– Applying Governance to Agile Projects
– Being Agile with our Governance Requirements
– Can the two coexist?
– Selling Agile to Governance People and the other way around
Bridging the Gap
Abstract

66
#RWDG
6
• Data Governance
– Data Governance is the Execution and Enforcement of Authority
Over the Management of Data and Data-Related Resources.
• Data Stewardship
– Data Stewardship is the Formalization of Accountability
Over the Management of Data and Data-Related Resources.
Bridging the Gap
Data Governance Definitions

77
#RWDG
7
• Non-Invasive Data Governance™
– The practice of:
• applying formal accountability & behavior
• through non-invasive roles & responsibilities
• to existing and / or new processes
• to assure that the definition, production & usage of data
• assures regulatory compliance, security, privacy, protection & quality.
– Non-Invasive describes how governance is applied to assure
non-threatening management of valuable data assets.
– The goal is to be
• Transparent
• Supportive
• Collaborative.
Bridging the Gap
Data Governance Definitions

88
#RWDG
8
• Defining the Agile Manifesto – Leading to Good Design
– People / Interaction
– Speed / Effectiveness
– Software / Working Products
– Requirements / Collaboration
– Response / Evolvement
Bridging the Gap
Agile Definitions

99
#RWDG
9
• To follow Agile methods – Good Design includes the definition of
– Themes – Broad way of describing an area of focus (Grouping of Epics)
– Epics – Collection of Functions (Grouping of User Stories)
– User Stories – Basis for defining the functions a business system must provide,
and to facilitate requirements management, often limited in detail by what can
be hand-written on a small paper notecard.
• User Stories – As a ____ I would like to be able to ____ so that I can _____.
• “Agile is dependent on quality definition of User Stories.”
Bridging the Gap
Agile Definitions

1010
#RWDG
10
• Waterfall
– A linear and sequential approach to software development, each waterfall stage
is assigned to a separate team to ensure greater project and deadline control,
important for on-time project delivery. A linear approach means a stage by
stage approach for product building, e.g.
1. Analyze and Prioritize Business Requirements / Needs.
2. Design Business Requirements Translated into IT Solution.
3. Processes Defined, Layouts Built, Code Implementation.
4. Evolves into Tested Solution for Implementation
5. Testing for Evaluation by End-User.
6. Evaluation and Maintenance
Bridging the Gap
Agile vs. Waterfall

1111
#RWDG
11
• Repetitive Themes of Agile Principles (and there are many)
– Complete Feature Before Moving On
– Test Early and Often
– Active User participation – Empowerment, Satisfy Customer
– Timing – Deliver Work Quickly, Incrementally
– Requirements at a High Level / Technical Debt to be Paid
– Lightweight & Visual
– Requirements Evolve / Timescale Fixed
– Software as Progress Measure
– Develop Small, Incremental Releases
– Attention to Good Design, Technical Excellence
– Simplicity is Essential
– Maximizing the Amount of Work
– Self Organized & Independent Teams
Bridging the Gap
Agile Principles

1212
#RWDG
12
• How do you begin to bring together approaches that are so far apart?
• Begin by looking at what they have in common
• Strengthen that
• Build on that
• Rinse & Repeat
• Is there a difference
between:
Data People &
Agile People
Bridging the Gap
Look for Common Ground

1313
#RWDG
13
• Repetitive Themes of Agile Principles
– Self Organized and Independent Teams
Bridging the Gap
Things Data People Have No Problem With

1414
#RWDG
14
Bridging the Gap
Things Data People Have No Problem With

1515
#RWDG
15
Bridging the Gap
Apply Governance to Agile

1616
#RWDG
16
• Target these Agile Principles to Bridge the Gap
1. Active User Participation – Empowerment, Satisfy Customer
2. Requirements at a High Level / Technical Debt to be Paid
3. Requirements Evolve / Timescale Fixed
Bridging the Gap

1717
#RWDG
17
1. Active User Participation – Empowerment, Satisfy Customer
‒ Cut from the Same Mold – Uncertain need for improvement!
‒ Data Governance Speaks this Same Language
‒ Essence of being non-invasive is to formalize accountability
‒ Data Governance Bill of “Rights”
 Getting the “Right” People
 Involved at the “Right” Time
 In the “Right” Way
 Using the “Right” Data
 To Make the “Right” Decision
 Leading to the “Right” Solution
 … Most of the Time
Bridging the Gap

1818
#RWDG
18
• Active User Participation – Empowerment, Satisfy Customer
‒ Data Governance is the Execution and Enforcement of Authority
‒ The typical Customer of Data Governance is Leadership
‒ The typical Customer of Agile Development is Leadership
‒ Leadership Requires Support, Sponsorship & Understanding
Bridging the Gap

1919
#RWDG
19
‒ Leadership Requires Satisfaction:
‒ Results from Data Governance & Agile
‒ Metrics from Data Governance & Agile
‒ Value from Data Governance & Agile
‒ Acceptance of Data Governance with Agile and the reverse.
Bridging the Gap

2020
#RWDG
20
‒ Results, Metrics, Value and Acceptance of Improvements in:
Bridging the Gap

2121
#RWDG
21
2. Requirements at a High Level / Technical Debt to be Paid
– This is where there is the greatest potential to bridge the gap.
– Data Management practitioners pride themselves on capturing metadata.
– Data Governance & Metadata Two-Way Street
– Relationship Between Requirements and Metadata
Bridging the Gap
Apply Agile to Governance

2222
#RWDG
22
• Requirements at a High Level / Technical Debt to be Paid
– Agile calls for Requirements through User Stories
• Little impact analysis is completed so “Big Picture” may not be considered.
• Details such as screen prints and report layouts are often provided.
• Requirements can be out of context.
– Waterfall Methodology starts with High-Level Requirements
• Starts with “Big Picture” and drills down to Lower-Level Requirements
• Up-front analysis of impact to organization.
• Requirements take time and agreement; potentially delaying the Project.
– One main reason why Agile advocates says that Waterfall is a thing of the past.
Bridging the Gap

2323
#RWDG
23
– Must data requirements include the Logical & Physical Modeling of Data?
• Models require questions … about cardinality, retention, growth, etc.
• Models promote a common understanding
• Requires the participation of a Data Analyst / Data Architect.
– Without detailed requirements – projects create their own understanding
which in turn can result in ambiguity, replication, etc.
– Requirements associated with data:
• Definition – Business Glossary, Data Dictionary, Vocabulary, Taxonomy
• Production – Data Movement, Mapping, Transformation, Legacy, Lineage
• Usage – Business Rules, Protection, Security, Classification, Sharing
Bridging the Gap

2424
#RWDG
24
– Questions for Data People about Requirements:
• Are we asking for too much documentation?
• Are we not gathering enough documentation?
• Do we use it all?
– Consider the specific value you get from your specific metadata.
Bridging the Gap

2525
#RWDG
25
– There is not a perfect answer to the “How much documentation” question.
– Recognize that Data People typically ask for lots of requirements / documentation.
– The question is – Are Data Requirements a good thing? Or a bad thing?
Bridging the Gap

2626
#RWDG
26
– Progression of Questions:
• Can we do without data requirements and still have good data?
• Are requirements the same thing as documentation?
• Requires Resources to Collect the Requirements / Documentation
Bridging the Gap

2727
#RWDG
27
• Whose responsibility is it to collect the requirements / documentation?
– Who defines / decides what is essential
– Who produces what is essential
– Who uses what is essential
• These activities fall outside the scope of Agile Team deliverables.
Bridging the Gap

2828
#RWDG
28
• Is there a point that we are asking for (demanding) too much documentation?
• How much documentation is necessary from:
– Agile Development perspective
– Data Governance perspective
• Requires a negotiation of Common Ground if we are going to Bridge the Gap.
Bridging the Gap

2929
#RWDG
29
– Additional Questions to Consider when Bridging the Gap:
• Can the Data People streamline their way of thinking and limit the
requirements while still being effective?
• Can the Data People provide the tools, techniques, metrics and templates to
become more agile in their approach to gaining the essential requirements and
still keep the enterprise perspective?
Bridging the Gap

3030
#RWDG
30
• Limit Data Demand for Requirements
• Provide Tools to Effectively Capture Essential Requirements
• Provide Resource(s) Focused on the Data / Agile Relationship
• Incrementally Build Governance into Agile
• These are ways to Bridge the Gap.
Bridging the Gap

3131
#RWDG
31
– Requirements that will eventually need to be addressed / Parking Lot List
– Also referred to as design debt or code debt
– Metaphor referring to the eventual consequences of poor system design
The debt can be thought of as work that needs to be done before a particular job
can be considered complete or proper. If the debt is not repaid, then it will keep
on accumulating interest, making it hard to implement changes later on. Wikipedia
– Debt can be accumulated in each step of the methodology – Agile or Waterfall
– This is the biggest reason why Data People are skeptical about Agile.
Bridging the Gap

3232
#RWDG
32
– Reasons why Technical Debt accumulates
• Business pressures - where the business considers getting something released
sooner before all of the necessary changes are complete, builds up technical
debt comprising those uncompleted changes.
• Lack of process or understanding - where businesses are blind to the concept of
technical debt, and make decisions without considering the implications.
• Lack of building loosely coupled components - where functions are not
modular, the software is not flexible enough to adapt to changes in business
needs.
• Lack of test suite - which encourages quick and risky Band-Aids to fix bugs.
• Lack of documentation - where code is created without necessary supporting
documentation. That work to create the supporting documentation represents
a debt that must be paid.
Bridging the Gap

3333
#RWDG
33
– Reasons why Technical Debt accumulates
• Lack of collaboration - where knowledge isn't shared around the organization
and business efficiency suffers, or junior developers are not properly mentored
• Parallel development at the same time on two or more branches - can cause
the buildup of technical debt because of the work that will eventually be
required to merge the changes into a single source base. The more changes that
are done in isolation, the more debt that is piled up.
• Delayed refactoring – As the requirements for a project evolve, it may become
clear that parts of the code have become unwieldy and must be refactored in
order to support future requirements. The longer that refactoring is delayed,
and the more code is written to use the current form, the more debt that piles
up that must be paid at the time the refactoring is finally done.
• Lack of knowledge - when the developer simply doesn't know how to write
elegant
Bridging the Gap

3434
#RWDG
34
3. Requirements Evolve / Timescale Fixed
– This is the biggest challenge when considering ways to Bridge the Gap.
– From both perspectives
• Evolving Requirements
• Fixed Period of Time.
– It’s like shooting at a moving target but being told to keep still.
Bridging the Gap
Working Together

3535
#RWDG
35
• Requirements Evolve / Timescale Fixed
– Requirements evolve means a gradual process in which the requirement
(including data requirements) change into a different and usually more complex
or better form.
– Let’s break this down:
• Gradual process – not all at once – requires constant management
• Changes into something different – requires constant management
• Usually more complex or better form – requires constant management
Bridging the Gap
Working Together

3636
#RWDG
36
– Management of Requirements requires Governance of Requirements.
– Agile is a form of Governance – Just not Data Governance.
– Bottom line with Governance is
The Execution and Enforcement of Authority
Bridging the Gap
Working Together

3737
#RWDG
37
– The challenge is to gather the:
• Most valuable requirements / documentation – and use it effectively
• Most effective requirements – and make them available
• Most available requirements – and make certain essentials are covered
• Most essential requirements – in a short period of time.
Bridging the Gap
Working Together

3838
#RWDG
38
– Three traditional variables of planning:
• Time
• Resources
• Expectations
– Give me two and I can give you the third.
Bridging the Gap
Working Together

3939
#RWDG
39
• Approaches to Bridging the Gap
– Many synergies; Show them.
– Negotiate Levels of Requirements / Documentation
– Leadership Decision through Understanding Relationship
– Software to Data same as Pipes to Water – Agile is Important
– Software is the Engine; Good Luck with that.
Bridging the Gap
Selling Agile to Data People

4040
#RWDG
40
• Approaches to Bridging the Gap
– Many synergies; Show them.
– Negotiate Levels of Requirements / Documentation
– Leadership Decision through Understanding Relationship
– Software to Data same as Pipes to Water – Governance is Important
– Data as an Asset; Good Luck with that.
Bridging the Gap
Selling Governance to Agile People

4141
#RWDG
41
• Alignment of Data Management and Software Development
• Information Technology = “Information” + “Technology”
– Are they together only in the name?
– Who has responsibility for the Information? Data?
– Who has the accountability for the Technology? Software?
– Are these the people that need to co-exist?
– Can Data Governance adjust for Agile Projects?
– Can We Control the Volume of Data Requirements?
Bridging the Gap
Can the Two Co-Exist?

4242
#RWDG
42
• Data People
– Agile Development is here to stay.
– Agile is a strong methodology that, when followed, is very effective.
– The goals of being agile align with what is expected from management.
– We need to find a way to work in conjunction with the Agile People.
• Agile People
– Data Governance is here to stay.
– Data is what flows through the pipeline of what you are developing.
– Without quality data, the systems are less than valuable.
– You need to find a way to work in conjunction with the Data People.
Bridging the Gap
For all you …

4343
#RWDG
43
• This session covered:
– Data Governance and Agile Definitions
– Applying Governance to Agile Projects
– Being Agile with our Governance Requirements
– Can the two coexist?
– Selling Agile to Governance People and the other way around
• Questions & Answers
Bridging the Gap
Summary

4444
#RWDG
44
• Robert S. Seiner
KIK Consulting & Educational Services – KIKconsulting.com
The Data Administration Newsletter – TDAN.com
Post Office Box 112571, Upper St. Clair, Pennsylvania 15241
412.220.9643, 412.220.9644 (Fax)
rseiner@kikconsulting.com
rseiner@tdan.com
@RSeiner
Bridging the Gap
Contact Information

Real-World Data Governance Webinar: Agile and Data Governance - Bridging the Gap

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie Real-World Data Governance Webinar: Agile and Data Governance - Bridging the Gap

Ähnlich wie Real-World Data Governance Webinar: Agile and Data Governance - Bridging the Gap (20)

Mehr von DATAVERSITY

Mehr von DATAVERSITY (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Real-World Data Governance Webinar: Agile and Data Governance - Bridging the Gap