The document discusses moving from traditional program management to agile program management. Traditional program management focuses on measuring variance against plans rather than performance forecasting. It also views avoiding change as the primary activity. Agile program management provides practices to successfully manage a portfolio of projects through iterative deliverables. It focuses on continuously managing performance variation and control through incremental deliverables. The key principles of agile program management are vision, value, alignment, transparency, and results.

1. Agile
Program
Management
Moving
Away
from
Traditional
Program
Management
Niranjan Nerlige V,
Founder
of
ExelPlus
Services
1

2. About
me
Niranjan Nerlige V, CSM,CSP,PMI-ACP, SPC
Agile Coach and Trainer,
Scrum, Agile, Lean, Leadership and Enterprise
Agility
Founder of Exelplus Services
niranjan@exelplus.com
Skype: niranjan.nv
Twitter: niranjan_nv
2
©Niranjan N V, Exelplus Services

3. Pressure
Today
Reduce
Cost
©Niranjan N V, Exelplus Services
3

4. Order
of
the
day
Deliver
Value
©Niranjan N V, Exelplus Services
4

5. Rapid
&
Unpredictably
Changing
Market
Scenario
Huge
Pressure
on
Product
Managers
&
Operational
Leaders©Niranjan N V, Exelplus Services
5

6. Changing
Business
Scenario
Dynamics
of
Market
and
Rapidly
Changing
Requirements
©Niranjan N V, Exelplus Services
6

7. What
is
Program
Management?
Program
Management
is
a
process
of
the
managing
several
related
projects
or
a
portfolio
of
products
Source:
http://www.kraus-­‐partner.eu/sites/default/files/project_portfolio_management_ii.jpg ©Niranjan N V, Exelplus Services
7

8. The
problem
in
Traditional
Program
Management
©Niranjan N V, Exelplus Services
8

9. Traditional
program
management
Measures
Variance
against
Plans
than
Performance
forecasting
Variance against
Plans
Performance
forecasting
9

10. Traditional
Systems
Measures
work
accomplished
through
Time
and
Schedule
Variance
Source:ttp://thefederalist.com/wp-­‐content/uploads/2015/07/bush_mission_accomplished-­‐jpg1.jpeg
©Niranjan N V, Exelplus Services
10

11. Success
Rates
of
Traditional
Program
Management
The success rates of applying traditional
methods to complex software development
projects over the years have been
underwhelming.Requirements
Technology
©Niranjan N V, Exelplus Services
11

12. IT
Projects
Have
Grown
in
number
and
complexity
©Niranjan N V, Exelplus Services
12

13. In
Traditional
Systems
Avoiding
or
controlling
change
is
primary
activity
Source:
http://www.projmasters.com/images/changecontrol.png
©Niranjan N V, Exelplus Services
13

14. Agile
Program
Management
Provides practices needed to successfully manage
a portfolio of projects, measure their financial and
technical performance through iterative and
incremental deliverables at program level.
©Niranjan N V, Exelplus Services
14

15. Agile
Program
Management
Provides
performance
forecasting
information
cc:
Jogesh
S
-­‐ https://www.flickr.com/photos/75621441@N00
continuously manage performance variation and control
variability through Iterative and Incremental deliverables
©Niranjan N V, Exelplus Services
15

16. Traditional and
Agile
Program
Management
Differences
©Niranjan N V, Exelplus Services
16

17. Agile
Program
Management
There
are
Five
principles
1)Vision: What
will
the
system
going
to
perform
when
it
is
done?
2)Value: How
will
we
recognize
that
our
Investment
has
given
returns?
3)Alignment: Who
are
the
people
to
be
aligned
to
deliver
Program
Features?
4)Transparency: How
can
we
have
building
lasting
relationships
with
customers
based
on
the
trust
5)Results: What
does
done
look
like?
©Niranjan N V, Exelplus Services
17

18. Program
Vision
©Niranjan N V, Exelplus Services
18

19. Vision
cc:
Celestine
Chua
-­‐ https://www.flickr.com/photos/69065182@N00 ©Niranjan N V, Exelplus Services
19

20. Program
Vision
It
expresses the
Strategic
Intention
of
a
Business
An example of a
strategic objective:
“Move back-office
storage to the cloud
application “
©Niranjan N V, Exelplus Services
20

21. Each
Program
Vision
should
answer
4Where
are
we
headed
with
this
solution?
4What
problem
does
it
solve?
4What
features and
benefits does
it
provide?
4For
whom
does
it
provide
it?
4What
performance
(Non-­‐Functional
Requirements)
does
it
deliver?
Agile
Program
Vision
explained………..
Program
Vision
©Niranjan N V, Exelplus Services
21

22. Formats
of
Program
Vision
a)Rolling
Wave
Briefings
b)Vision
Document
c)Preliminary
Data
Sheet
d)Draft
Press
Release
©Niranjan N V, Exelplus Services
22

23. Agile
Roadmap
Vision
is
realized
through
Product
Road
Map©Niranjan N V, Exelplus Services
23

24. Value
©Niranjan N V, Exelplus Services
24

25. Agile
Roadmap
Demonstrate
Value
Flow
by
delivering
Program
Features
Internal Release 1 Internal Release 2 Internal Release 3
Feature sets
Feature sets
Feature sets
Feature sets
Feature sets
Feature sets
Feature sets
Feature sets
Feature sets
Feature sets
Feature sets
Feature sets
Feature sets
Feature sets
Feature sets
Feature sets
Feature sets
Feature sets
Story
Story
Story
Story
Story
Story
Story
Story
Story
Story
Story
Story
Story Successful
Agile
program
demonstrate
value
flow
by
delivering
the
Program
Features
in
regular
intervals
in
the
form
of
Potential
Shippable
Increments
©Niranjan N V, Exelplus Services
25

26. Accelerate
the
Learning
Successful
agile
programs
have
fast
feedback
cycles
4Smaller
batches
4Less
work
in
process
4Shorter
release
dates
4Faster
feedback
4Releases
defined
by
date,
theme,
planned
feature
set
4Release
date
and
quality
are
fixed
4Scope is
the
variable
©Niranjan N V, Exelplus Services
26

27. Alignment
©Niranjan N V, Exelplus Services
27

28. cc:
Ken
Whytock
-­‐ https://www.flickr.com/photos/7815007@N07 ©Niranjan N V, Exelplus Services
28

29. Shared
Understanding
Perform
Release
Planning
at
least
every
Quarter
Sorce:
http://agileatlas.org/images/uploads/Simplified_Release_Cycle.jpg
“Agile Program Management exhibit strong alignment from Top Senior Executives
to Product managers, Product Owners, Scrum Masters and Scrum Team members”
©Niranjan N V, Exelplus Services
29

30. Agile
teams
frequently
integrate
the
User
Stories
Test
the
System
Increment
Source:http://farm7.staticflickr.com/6013/5979199497_b189247c17_z.jpg
©Niranjan N
V,
Exelplus Services
30

31. Validate
Program
Increment
Agile
teams
adapt
themselves
through
feedback
Agile teams adapt themselves through regular feedback from
all stakeholders for every program increment
©Niranjan N
V,
Exelplus Services
31

32. Transparency
©Niranjan N
V,
Exelplus Services
32

33. cc:
Rene
Mensen
-­‐ https://www.flickr.com/photos/44206268@N07
“Isolated
activities
and
Lack
of
transparency
will
hinder
performance” – Jeff
Sutherland
“Equal
access
to
information
at
all
levels
is
critical” –
Takeuchi
and
Nonaka on
Knowledge
Management
©Niranjan N
V,
Exelplus Services
33

34. Involve
Executives,
Program
Managers
&
Stake
Holders
Agile
Programs
Inspect
and
Adapt
cc:
codyvaldes -­‐ https://www.flickr.com/photos/49174157@N03
©Niranjan N
V,
Exelplus Services
34

35. Agile
Program
Execution
Agile
teams
collaborate
together
to
define
release
scope
,
program
deliverables
and
implement
the
program
increment
at
every
release
boundaries
©Niranjan N
V,
Exelplus Services
35

36. Results
©Niranjan N
V,
Exelplus Services
36

37. Identify
Program
Measures
Evalute
the
Agile
Program
Performance
Program
Performance
Metrics:
Ø #
of
Features
planned
Ø #
of
Features
accepted
Ø #
of
user
stories
planned
Ø #
of
user
stories
accepted
Ø %
Business
Value
Planned
v/s
Achieved
©Niranjan N
V,
Exelplus Services
37

38. Working
Product
Key
for
every
Program
Increment
Release
cc:
hanspetermeyer.ca
-­‐ https://www.flickr.com/photos/9522129@N03
The
“working
product”
is
the
key
in
every
program
increment
release
©Niranjan N
V,
Exelplus Services
38

39. Visibility
of
Results
Program
Backlog
Burn
Down,
Burn
Up
Charts
50
100
150
200
250
300
350
400
450
500
Time
Features
Features Done, Remaining and Total
Program
Backlog
Burn
up
and
Burn
down
indicating
features
remaining
and
total
features
done
©Niranjan N
V,
Exelplus Services
39

40. cc:
Toronto
Public
Library
Special
Collections
-­‐ https://www.flickr.com/photos/43021516@N06
References
1)Agile Program Management-Moving from principles to practice
by Glen B. Alleman, Cutter journal.
2)Scaled Agile Framework by Dean Leffingwell
3)Agile Program Management Best Practices by Peter Beherens
©Niranjan N
V,
Exelplus Services
40

41. cc:
Stuck
in
Customs
-­‐ https://www.flickr.com/photos/95572727@N00
Thank
you
Niranjan N V,
Email: niranjan@exelplus.com
Skype: niranjan.nv
Twitter: niranjan_nv
©Niranjan N
V,
Exelplus Services
41