IT Governance

7th Lecture – Business Agility: Scrum and

DevOps
Agenda

7th Lecture goals

SCRUM

DevOps

Assignments
 7th Lecture goals

• Content Objectives:
• Understand a framework that focuses on assisting companies in achieving their goals for IT governance and
management.

• Language Objectives:
• Be able to contrast and synthetize complex technical readings.
SCRUM
Quotes
 There is a new context

A B

High Changing High

uncertainty conditions complexity
 Manifesto for Agile Software Development
(2001)
We are uncovering better ways of developing software by doing it and helping others
do it.
Through this work we have come to value:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left
more.

Manifesto for Agile Software Development

 The 12 Agile principles

Early and Continuous Embrace Frequent Delivery Business and Developers

Delivery of Valuable Change Together
Software

Motivated Face-to-Face Working Constant Pace

Individuals Conversation Software

Technical Self-
Simplicity Regular
Excellence Organizing
Reflection and
Teams
Adjustment

8
 Common characteristics of agile
methodologies

Customer value Multifunctional

teams

Characteristics

Incremental Small iterations

approach

Continuous improvement
What is Scrum?
• Scrum is one of the most popular
agile methods.
• It is an adaptive, iterative, fast,
flexible and efficient framework
designed to deliver the maximum
value possible quickly throughout
the project.
• Ensures transparency in
communication.
• Creates collective accountability
and progress.
• Scrum framework support al kinds
of projects.
• Proposed by Hirotaka Takeuchi and
Ikujiro Nonaka based on Rugby
strategies in 1986.
 Cynefin framework

Scrum
(empirical
process)

Moving to
the complexity
quadrant

Source: https://www.researchgate.net/
 SCRUM structure
Get astonishing
results Get the right
business value Results
Team that can do Value-based
anything Get business value
prioritization faster
Empirical
Collaboration process
Room for Team and Transparency
Iterative Inspection
Individual Growth development Adaptation
Self organized Principles
Time-boxing

Values

Courage Openess
Focus Commitment Respect
 Phases and processes

Plan & Impleme Review &

Initiate Release
estimate nt retrospect

•Create Project •Create and •Create •Demonstrate •Ship

Vision estimate User Deliverables and Validate Deliverables
•Form Scrum Stories •Conduct Daily •Retrospect •Retrospect
Team •Commit User Standup Sprint Project
•Develop Epics Stories •Groom
•Create •Identify & Prioritized
Prioritized estimate tasks Product Backlog
Product Backlog •Create sprint
backlog

Source: ScrumStudy Body of Knowledge

Source: WinRed.es
Scrum roles
Themes, epics, user stories and tasks

• Theme: group of user stories

that share a common attribute,
and for convenience they are
grouped together. Are usually
broad in scope, lacking in
detail.
• Epic: is a large story that
cannot be completed in a
single sprint.
• User story: is very high-level
definition of the project
requirements. It contains just
enough information to give the
Scrum team proper context as
to what the final product should
be like, and for them to
calculate an estimation for the
completion.
User story criteria

• Are short, simple descriptions written

throughout the agile project.
• Although it is owned by the PO, anyone
can write the user story.
• It is expressed in plain language so the
customer can understand what the final
product is all about.
• It answers the ‘who’, ‘what’ and ‘why’ of
a project in a simple language.
• User stories are the “heart of Scrum”
because they serve as the ‘building
blocks’ of the sprint.
• Should be write accompanied to its
acceptance criteria.
 User story – INVEST criteria

Source: Medium - Scrum: INVEST in Good Stories by Achieving SMART Tasks

User story - examples
 Acceptance Criteria - example

Source: User stories in agile software development - Sandra Svanidzaitė, PhD, CSPO
DevOps
 How do we deal with delivery?

Ope Redes Infra Infosec

Scrum
Master

Daily

Codificar Build Deploy Test Produc.

Sprint
Product
Owner Planning
Review
Retro

Team

Agility: Scrum
 Do we have different objectives?

• Designing a
What is What is
solution and Dev looking Ops looking
implementing it
•
• Adopting new for? for? Availability and
reliability
technologies
• Efficiency
• Speed in
• Recovery times
implementing
• Monitoring
• Timely
• Minimal security
provisioning.
risks
• Synchronized
• Controlled changes
environments
• Root cause
• Predictability in
access to How is their relationship? corrections
resources
• Suspicious from each other
• Lack of communication
• Late involvement
• Mutual accusations
• Bureaucratic processes with few
incremental improvements
• Shadow IT
 DevOps the component that completes an
agility model

¿What is DevOps?

A cultural and professional movement that emphasizes

communication, collaboration and integration between developers
and IT operations professionals, while automating the processes
of software delivery and infrastructure changes.

In turn, it seeks to establish a culture and environment in which

building, testing and delivery can occur quickly, frequently and
securely.

DevOps Institute
 DevOps benefits

1. Speed of 2. Rapid 3. Less manual 4. Error

release changes. operations. reduction.
delivery.

5. Shared and 6. IT teams with 7. Cost

managed common reduction.
assets. goals.
 Principles of DevOps: The Three Ways

1st way: Increase the flow

from left to right reducing
restrictions and with
systemic vision.

2nd way: Shorten feedback

with visibility and early
involvement.

3rd way: Culture of

continuous exploration,
learning and improvement
(Simian Army, AIOps)
 DevOps is complemented by other practices

• Collaboration
• Feedback
• Small batches
Agile • Frequent delivery
• Measurement
• Working software
• Self-organizing equipment

DevOps
• Change mgmt.
• Release mgmt. • Value Stream
• Configuration • One piece Flow
mgmt. • Kaizen
• Event mgmt. ITSM Lean • Obeya
• Incident & • WIP limits
problema mgmt • Remove waste
(muda)
 What is a deployment pipeline?

The deployment pipeline in DevOps is

the automated manifestation of your
process for getting the software from
version control into the hands of your
users.

Continuous Delivery Book –

Jez Humble & David Farley
 DevOps Practices

6. Monitoring
DevOps
Download Build Unit Test Dev Env. Integration Testing Func. Non-Func QA Deploy
testing Env. testing testing Release

1. Commit Stage
2. Continuous Integration
3. Testing (TDD, BDD, ATDD)
4. Continuous Delivery
5. Continuous Deployment

Repo

Dev
Tester
Ops
CONCLUSIONS

Business agility provides companies with the ability to deliver fast and respond
01 quickly and pivot in an environment of changing market needs.

The agility models have in common the agile manifesto and principles that are a
02 response to traditional cascade methods.

Scrum provides the framework for better delivery and continual with focus on high
03 quality.

DevOps is the combination of cultural philosophies, practices, and tools that brings
04 the development team and operations team together while optimizing the flow of
value from the idea to de final user.
 REFERENCES

• The Agile Samurai by Jonathan Rasmusson

• DevOps for digital leaders.
Assignments
 Assignment for our 8th lecture

• Read the Agile Leadership Journal article according to your last name: A (find it in
Canvas).
• Design a mindmap with the main concepts in your opinion.
• Upload the document in our course site in Canvas.
• Name the file: “IT Governance 2020I - (your student code and lastname) – Session
8“
• Articles:
• Bringing “Leadership Agility” to Agile: Last name from A to E.
• Two Sides of the Same Coin: Using Culture and Structure to Build Agile Organizations: Last
name from F to J.
• Creating Self-Directed Teams: It’s a Question of Space: Last name from K to O.
• The Pedagogy Principle: Teaching Agile Leaders How to Teach: Last name from P to T.
• Climb Every Mountain: Overcoming the Barriers to Enterprise Agility: Last name from U to Z.
GRACIAS
Contenido elaborado en: