0% found this document useful (0 votes)
38 views33 pages

ADV-Agile-Session 1

Agile
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
38 views33 pages

ADV-Agile-Session 1

Agile
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 33

Why Agile?

&
What is Agile?
COURSE: AGILE & DEVOPS (ADV)

SUBBI LAKSHMANAN
Predictive Software Engineering

User Acceptance testing

2 Subbi Lakshmanan
In Predictive Software
Start to Finish Engineering
Issues with Waterfall

Customers or stakeholders
may not be available for
questions

Start
Must have all
Finish
Final testing
requirements up front
Must wait for full and
Estimation is complex complete user
feedback
Must understand
capabilities of all Value not achieved
involved until end

Team must create and Must resist change or document


maintain volumes of change requests (which extends
documentation schedule and budget)

3 Subbi Lakshmanan
Competing in the Age of Software

The problem is not with our organizations realizing


that they need to transform; the problem is that
organizations are using managerial frameworks and
infrastructure models from past revolutions to
manage their businesses in this one.
—Mik Kersten
Linear approach may not work in all
scenarios

5 Subbi Lakshmanan Source: Agile Practice Guide


Feb 2001, Snowbird Ski Resort, Utah
Kent Beck James Grenning Robert C. Martin
Mike Beedle Jim Highsmith Steve Mellor
Arie van Bennekum Andrew Hunt Ken Schwaber
Alistair Cockburn Ron Jeffries Jeff Sutherland
Ward Cunningham Jon Kern Dave Thomas
Martin Fowler Brian Marick

• Seventeen people met to discuss alternatives to


document driven, heavyweight software development
• What emerged was “The Agile Manifesto”

6 Subbi Lakshmanan
7 Subbi Lakshmanan
12 Agile Principles

Welcome changing
Deliver working software
Our highest priority is to requirements, even late
frequently, from a
satisfy the customer in development. Agile
couple of weeks to a
through early and processes harness
couple of months, with a
continuous delivery of change for the
preference to the
valuable software. customer’s competitive
shorter timescale.
advantage.

Build projects around The most efficient and


motivated individuals. effective method of
Business people and
Give them the conveying information
developers must work
environment and to and within a
together daily
support they need, and development team is
throughout the project.
trust them to get the job face-to-face
done. conversation.

8 Subbi Lakshmanan
12 Agile Principles

Agile processes
promote sustainable
development. The Continuous attention to
Working software is the
sponsors, developers, technical excellence
primary measure of
and users should be and good design
progress.
able to maintain a enhances agility.
constant pace
indefinitely.

At regular intervals, the


Simplicity–the art of The best architectures, team reflects on how to
maximizing the amount requirements, and become more effective,
of work not done–is designs emerge from then tunes and adjusts
essential. self-organizing teams. its behavior
accordingly.

9 Subbi Lakshmanan
As illustrated by Dr Ahmed Sidky
defined by guided by manifested through

Crystal

Scrum

FDD
XP
SAFe

Spotify

Kanban

Being agile Doing agile


10 Subbi Lakshmanan Source: Agile practice guide
Mindset towards succeeding when there
is Uncertainty

11 Subbi Lakshmanan
Course: Agile & Devops
Traditional Approach

Agile Approach

12
Agile Value Proposition

13 Subbi Lakshmanan
14 Subbi Lakshmanan
The Big Picture in an Enterprise
Transformation

INCEPTION TRANSITION

15 Course: Agile & Devops Source: Disciplined Agile


Agile approaches plotted by breadth
and detail
Lean SAFe
DSDM Disciplined
Breadth of Lifecycle Coverage

LeSS Agile

Scrum of Agile UP
Scrums Crystal

Scaled
XP Approach
Kanban

FDD Team
Method
Scrum

Depth of guidance detail


16 Course: Agile & Devops Source: Agile practice guide
Companies on the leader board

Deploys new release every 11.6 seconds on average

1000 releases per day

80 deployments a week

Sony Pictures deploys every minute

50 times a day

17 Subbi Lakshmanan
State of Agile Report -
2021

18 Subbi Lakshmanan
What were the most important reasons for adopting Agile within your team or organization?
*Respondents were able to select multiple responses to this question.

64%

64%
Reasons for adopting Agile
Enhance ability to manage changing priorities

Accelerate software delivery

47% Increase team productivity

47% Improve business and IT alignment

42% Enhance software quality

41% Enhance delivery predictability

40% Improve project visibility

39% Reduce project risk

39% Better respond to volatile market conditions

35% Improve team morale

24% Improve engineering discipline STATE OF AGILE LOOK BACK

The reasons organizations want to


24% Better manage distributed teams
adopt Agile remain unchanged for
several years. However, we have
23% Reduce project cost
seen an increase in their ability to
meet those goals, particularly as
20% Increase software maintainability
DevOps and agile practices expand
across the organization.
5% Other

19 Subbi Lakshmanan Source: 15th annual state of agile report, 2021 by digital.ai
Which areas of your organization have adopted How do y
Agile principles and practices? team cha
*Respondents were able to select multiple responses to this question.

86% Software development

63% IT

29% Operations

17% Marketing

17%
56
Security We’ll be back in the office on a
regular basis but not full time

16% Human Resources

11% Sales/Sales Ops

10% Finance

10% Hardware development

Multiple industry studies h


6% Other This survey indicates that
Remote work isn’t just a t
2% None
3% say they will be back
20 Subbi Lakshmanan Source: 15th annual state of agile report, 2021 by digital.ai
Agile Adoption
How does your organization measure the success of Agile delivery?
Business value delivered 49%
Customer/user satisfaction 49%
Velocity 45%
Planned vs. actual stories per iteration 35%
Team morale 31%
Budget vs. actual cost 30%
Cycle time 29%
Defects into production 28%
Planned vs. actual release dates 26%
Iteration burndown 25%
Defects over time 25%
Burn-up chart 23%
WIP (Work in Progress) 21%
Release burndown 20%
Defect resolution 19% Agile delivery success is focused on
Customer retention 18% external measures, with almost half
Estimation accuracy 15% of respondents focused on business
Revenue sales impact 15% value delivered 49% and customer
Earned value 13% satisfaction 49%. Additionally,
13%
delivery velocity 45% is seen as
Cumulative flow chart
Product utilization 12%
an equally important measure of
Test pass/fail over time 12%
Agile success.
Scope change in a release 11%
Individual hours per iteration/week 9%

igital.ai | 15th State of Agile Report 10


21 Source: 15th annual state of agile report, 2021 by digital.ai
Scaling Agile • Retrospectives 83%, and

Which Agile methodology do you follow most closely at Which framework


• Sprint/iteration 83% your organization follow to
planningdoes
wouldthesayteam level?
that the number one werehelp
used.scale Agile?
llenge facing capital ‘A’ Agile today is
ck of awareness of systems thinking. While a wide range of scaling
d the fact that
Scrum/XP Hybrid
we have all these teams frameworks are in use, the 37% Scaled Agile Framework (SAFe®)
ScrumBan Kanban Scaled Agile Framework (SAFe®) In addition:
d organizations who have adopted agile
continues
Iterativeto be the most popular 9% Scrum@Scale/Scrum of Scrums
d agile frameworks, be it Scrum or SAFe 4% with 37% of respondents • Kanban boards 77%,

tem.” 9% 6% 6%
XP, are doing so in one part of the
1% Extreme
identifying it asProgramming (XP)
the framework
• 6%
Task boards 67%, and Enterprise Scrum
1%
they mostLeanclosely
Startupfollow. SAFe®
significantly outdistances the next
n Leybourn, CEO and Founder Business Spreadsheets 66% are all
• 5% Spotify Model
Otherscaling method, Scrum@
nearest
lity Institute widely used for agile planning.
5% Scale/Scrum of Scrums (9%).
2% Don’t know 3% Agile Portfolio Management (APM)
Over the last several years, there
has been increasing awareness
of both the opportunities and
3% Disciplined Agile (DA)

66%
th respect to software development,
challenges offered by scaling
Agile practices across the 3% Large Scale Scrum (LeSS)
Scrum
nk at the team level agile is widely organization. Initially, scaling
cticed It’s the dominant form of
agile was addressed through a 3% Nexus
“Scrum of Scrums” approach.
w teams organize. In many IT teams,
Over the past five surveys, we 2% Lean Management
alignment to business outcomes is
have seen the use of SAFe®
sing.” grow significantly to become the
dominant approach, in use by 1% Recipes for Agile Governance in the Enterprise (RAGE)
e West, CEO at Scrum.org
more than a third of respondents.
al.ai | 15th State of Agile Report 19% Don’t know

8% Other

| 15th State of Agile Report 16


22 Subbi Lakshmanan Source: 15th annual state of agile report, 2021 by digital.ai
Almost nine in 10 respondents use daily standups while over four in ¾ of respondents say they use kanban boards while ⅔ use
five
Brief use
daily retrospectives
event in Agile softwareand sprint/iteration planning.
development taskboards and spreadsheets.

Which of the following Agile techniques and practices Which Agile planning and delivery tools do you
does your organization use? currently use?

Daily standup 87% 77% Kanban Board


67% Taskboard
Retrospectives 83%
66% Spreadsheet
Sprint/Iteration planning 83%
64% Agile Project Management Tool
Sprint/iteration reviews 81% 62% Bug Tracker

Short iterations 63% 62% Wiki


58% Product Roadmapping
Kanban 61%
54% Automated Build Tool
Planning Poker/Team Estimation 58% 54% Unit Test Tool

Dedicated customer/product owner 56% 53% Continuous Integration Tool


51% Wireframes
Release planning 54%
47% Release/Deployment Automation Tool
Product roadmapping 52% 43% Requirements Management Tool
Single team 51% 43% Traditional Product Management Tool
39% Product and Portfolio Management (PPM) Tool
Frequent releases 51%
37% Static Analysis
Story mapping 40%
36% Story Mapping Tool
Agile Portfolio planning 32% 35% Automated Acceptance Test Tool

Common work area 24% 29% Timecards


24% Refactoring Tool
Agile/Lean UX 23%
19% Index Cards
Other 3% 18% Customer Idea Management Tool

l.ai | 15th State of Agile Report


23 Subbi Lakshmanan Source: 15th annual state of agile report, 2021 by digital.ai
Agile practitioners rely on a wide variety of tools to support Agile techniques and practices. However, the survey
indicated that two tools, Atlassian Jira (81%) and Digital.ai Agility (70%), were the most highly recommended to
colleagues by their users.
Based on your experience using agile planning tools, which ones would you recommend to someone else?
*Respondents were able to select multiple responses to this question.

81% Atlassian Jira


70% Digital.ai Agility (formerly VersionOne)
66% Azure DevOps
62% Broadcom Rally (CA Agile Central)
59% Trello
52% Atlassian Jira Align
48% Google Docs STATE OF AGILE LOOK BACK
43% Targetprocess
From the earliest days of the State of Agile
40% LeanKit
survey, tool support has been a key component
39% IBM Rational Team Concert
determining the success of Agile.
38% HP Agile Manager
35% Azure DevOps Server (Microsoft TFS) A varied collection of tools is employed, ranging
from generic planning and management tools
35% Microsoft Project
(e.g., Microsoft Office) to specialized commercial
34% Bugzilla
offerings.
32% Microsoft Excel
31% Pivotal Tracker In the past few years, Atlassian Jira and
Digital.ai Agility have seen the highest
28% HP Quality Center/ALM
percentage of recommendations from their
25% Hansoft
users.
21% Digital.ai TeamForge (CollabNet TeamForge)
20% In-house/home-grown
10% Axosoft

ai | 15th State of Agile Report 17

24 Subbi Lakshmanan Source: 15th annual state of agile report, 2021 by digital.ai
Agile Challenges
Challenges experienced when adopting
What are the most significant barriers to adopting and scaling Agile practices in your current organization?

46% and scaling agile


Inconsistent processes and practices across teams

43% Organizational culture at odds with agile values

42% General organization resistence to change

42% Lack of skills/experience with agile methods

41% Not enough leadership participation

40% Inadequate management support and sponsership

35% Insufficient training and education

35% Pervasiveness of traditional development methods

31% Lack of business/customer/product

30% Fragmented tooling and project related data/measurements


STATE OF AGILE LOOK BACK

22% Unwilling to admit mistakes and learn from delivery failure Organizational culture and Agile values
are becoming more aligned. A few years
17% Minimal collaboration and knowledge pairing
ago, more than 8 out of 10 respondents
Regulatory compliance or identified culture as a significant barrier to
13% government issue Agile adoption. That number now stands
at slightly more than 4 in 10.
7% Don’t know

5% Other

25 Subbi Lakshmanan Source: 15th annual state of agile report, 2021 by digital.ai
gital.ai | 15th State of Agile Report 12
Course ADV - Overview
& Expectations

26 Subbi Lakshmanan
Sessions

Week Topic Week Topic

Why Agile? What is Agile? 4


1
Course Expectations May Project – Group Presentation
May 2nd
& 3rd 30th and
Scrum 31st

Scrum (Contd.)
2 SaFe Overview
5
Kanban
May 9th Devops Case Analysis – Part 3
June 6th
and 10th
Managing Agile Projects, Story Mapping and 7th
Overview of Devops tools

Test – 1 (MCQ format)


3
Project Planning - Breakout TBD Test – 2 (MCQ format)
May 16th
and 17th
Devops Case Analysis – Part 1 & 2

27 Subbi Lakshmanan
Assessment

• Class Participation/Case Analysis: 20%


• Project Work: 30%
• Test: 50%

28 Subbi Lakshmanan
Devops – Case Analysis

• Case analysis will be on the story narrated in the book


“The Phoenix Project”
• We will analyze the story through classroom discussion
• Part 1&2 of the story will be discussed during week 3 and
Part 3 will be discussed during Week 5
• Your individual participation in the discussion will be
considered for evaluation
• Please start reading today.

29 Subbi Lakshmanan
Project work

• Each group to identify a software product/application


idea.
• This will form the basis for the project work. You can share
your ideas with me by Thursday, May 9th.
• I expect the following information on the product idea
from each group:
• Short Description of the Product idea you have in mind
• Name your Product (you can be at your creative best here)
• Send the above information to [email protected]

30 Subbi Lakshmanan
Project topics – Samples from the earlier
batch
Product name Product description

Paws A web and mobile application for connecting pet owners with veterinarians. This application will
feature a list of doctors from which the users can choose one based on their reviews and their
own preferences and schedule appointments.
Vaanity Fair We plan to design an ecommerce website with a mobile app where we will sell only handicrafts
and authentic local made specialties as our category of products. It will be a b2b and b2c
process, dedicated towards selling products directly from the local artisans to the customer's
doorsteps.
PLANToT We provide an IoT-enabled gardening solution for your home. The device will initiate the watering
of the plant automatically whenever the moisture content in the pot drops below a threshold
value. The device can be operated via a mobile app while you are away from home and it will
also provide analysis about plant health and suggest corrective measures.
PLANToT - We take care of your plants while you are away.
VR4U We plan to develop a platform where consumers can travel the world sitting at their homes. We
will do this by using virtual reality. We plan to create VR videos of famous/historic places such as
the Taj Mahal and upload them on our app/website. The consumer then wears VR headsets, logs
in on our app/website, and gets a feel of real like travel experience.

31 Subbi Lakshmanan
Game Time!
• Form 6 groups. 5 groups with 10 members each and one with 9.
• One member from each group to be identified as the
“Observer”
• Each group will be given a bag of plastic balls
• The objective is to pass as many balls as possible in the given
time through all the team members by following the rules below.
• Each ball must be touched at least once by every team member.
• Each ball must have air-time before it reaches the next team member.
• Balls can't be passed to your direct neighbour to your immediate left or
right.
• Each ball must return to the same person who introduced it into the
system.
32 Course: Agile & Devops
End of Session 1.

Thank you.

33 Subbi Lakshmanan

You might also like