Agile Software Development is a well established concept in the developer community. However although it is more 40 years old methodology it has not been widely adopted by enterprises. In several cases organizations use Agile as a buzzword without implementing it in practice. I created a presentation addressing several aspects of introducing Agile Software Delivery such as - Why Agile is good for business - When to use and when not to use agile - Infrastructure and Agile projects - Agile contracting

1. Agile Software Delivery
for Executives
Gabor Schonekker
https://www.linkedin.com/in/gaborschonekker

2.  Introduction to Agile Approach
 SCRUM Agile Methodology Overview
 Agile Contracting
 Infrastructure and Bespoke software components in anAgile project
2

3. 3
Introduction to Agile Approach

4. Every project
starts with a
DREAM

5. Perfect Car Perfect Drink Perfect Dashboard

8. Do you have the
resources to implement
the perfect solution?

9. DeLorean tried to create the
perfect sport car, but failed
due to
- Untested technology
- Quality challenges
- High cost

10. We don’t know where we want to go
We are not sure how to get there
We may not have enough resources to finish the journey
Uncertainty
when creating
something new

11. Software
Project
Uncertain
requirements,
priorities
Uncertain
timelines
Uncertain
costs,
resources
Uncertain
technology
(design)
choices
Software project is
creating something
NEW

12. Traditional Agile

14. Agile
Small, frequent
production (shippable)
deployments with
adjustable
requirements based on
user feedback
Traditional
Long, expensive, fixed
scope project
delivering
requirements specified
at the drawing board
Optimal - project specific - approach
is probably in between
It does NOT
mean that Agile
is not organized

15. 15
SCRUM

16. Source: https://en.wikipedia.org/wiki/Agile_software_development
SCRUM is maybe the
most popular

17. Product Owner
(or customer representative)
DeveloperTeam
SCRUM Master

18. Product Owner
(or customer representative)
• Gather Requirements from all Stakeholders
• Provide clear direction
• Bridge the communication between the
Development team and the Stakeholders
• Status updates to the Stakeholders

19. DeveloperTeam
• Deliver products as per specifications (shippable
increments (PSIs))
• 3-9Team members
• Cross-Functional
• Self Organizing (team accountability)

20. SCRUM Master
• Remove obstacles enabling the team to deliver
• Ensure the team follows the agreed processes
in the Scrum framework
• Facilitate between customer and development
team (“HighTouch”)

21. Prioritized list of
ALL requirements
(User Stories)
Sprint is a basic unit of development:
- Timeboxed effort: the duration is fixed in
advance (1-6 weeks)
- Ongoing Sprint scope is fixed
The deliverable of a Sprint is a
software that can used in a
production environment

23. 23
Agile Contracting

24. Traditional Contracts focus
on Function
Agile Contracts focus
on Framework

25. Traditional Contracts
• Predictable scope
• Fixed Functionality
• Scope changes are
handled via Change Request
procedure
• Fixed price
• Flexible resources allocation
• Single deployment (or fixed
phasing)
• Payment per delivery
Agile Contracts
• Flexible scope
• Fixed Framework
• Scope changes are
part of the framework
• Fixed budget
• Fixed resource allocation
• Multiple deployments
(flexible)
• Payment for resource
usage
Optimal - project specific - approach
is probably in between

29. 29
Infrastructure and
Agile Software Development

31. Rule ofThumb

32. -150
-100
-50
0
50
100
Cost Business Value
-150
-100
-50
0
50
100
Cost Business Value
Infrastructure implementation Bespoke Application implementation
Advantages
- Delivers high business value in a short
period of time
- Lower operational costs
- Apply “best practices” from the market
- New Product Release (version upgrade)
provides quick increase business value
Advantages:
- Business value continue to grow over
longer period of time
- Exact fit to company requirements

33. Infrastructure implementation Bespoke Application implementation
Challenges
- How to select the right product before
actually using it?
- Selecting wrong product is very costly
mistake
- Will version upgrades deliver business value
in the future?
- Product limitations
Challenges
- Business value increase slowly as
development progresses
- Operational costs are higher as Development
team is in-house
- Success of the system heavily depends on the
Development team skills
- Difficult to bring in “best practice” expertise
-150
-100
-50
0
50
100
Cost Business Value
-150
-100
-50
0
50
100
Cost Business Value

34. -150
-100
-50
0
50
100
150
200
Cost Business Value
Hybrid Approach:
Software development depending on
Infrastructure components. Required
Infrastructure characteristics:
- Wide configuration possibilities
- AddOn, customization support
(development friendly environment)
The First Phase (Sprint) is deploying the
standard infrastructure functionality
immediately delivering business value.
Additional requirements are delivered as
configuration/customization.

35. -150
-100
-50
0
50
100
150
200
Cost Business Value
Hybrid Approach:
Advantages:
- High Business value in short time
- Constantly growing business value
Challenges:
- The success still heavily depends on
choosing the right product
- Expensive
- Customizations may make version
upgrades difficult or even impossible

36. Budget In-house experience In-house development team skills
Infrastructure (or standard product) $ X X
Bespoke Development $$$ XXXX XXXX
Hybrid $$ XX XXX*
Note:
* Extensive training will be required on the selected product.

37. WITH InfrastructureWITHOUT Infrastructure

38. 38
BACKUP

39. Source: http://agilemanifesto.org/