Scaling agile beyond small development teams is hard. Larger teams usually fall victim to misaligned chaos and bureaucratic waste. Learn how Surescripts uses their home-grown collaboration approach, "Possible/Valuable/Viable", to ensure the right conversations are happening at the right time with help from integrations between Confluence and JIRA Agile.

1. #atlassian

2. Agile Program Management
Possible/Valuable/Viable
PETER CALLIES • VP, PRODUCT DEVELOPMENT LIFECYCLE • SURESCRIPTS •
@PCALLIES

3. We connect fragmented
healthcare into a
coherent whole.
We operate the network and
build the relationships that
enable vital information to flow
freely and securely to the right
place at the right time.
01
We see American healthcare
as a collection of different
parts, each powerful in its own
way, but whose collective
potential is only beginning
to be tapped.
We believe that healthcare
is inextricably linked to
technology, and if that
technology improves,
healthcare will improve
with it.
We know that people and
organizations working
together, across silos, will
unleash the full potential of
American healthcare—making
it more efficient and more
effective and easier to
navigate.
Surescripts.
04
03
01 02
02
03 04

4. “Agile is not about the
destination as much as the
constant journey”
–Ryan Anderson

6. Planning &
Scaling
First Steps
Operating and
Adapting
Developing
PVV
Before Agile

7. Planning &
Scaling
First Steps
Operating and
Adapting
Developing
PVV
Before Agile

12. Unpredictable
Poor Quality
Long Lead Times

13. Planning &
Scaling
First Steps
Operating and
Adapting
Developing
PVV
Before Agile

15. JIRA Agile Support for Team Agile!

16. Confluence support for Team Agile!

17. First Steps Takeaways!
Working, tested code every two
weeks improved predictability and
quality
Stable teams provide a clear view
of capacity

18. Planning &
Scaling
First Steps
Operating and
Adapting
Developing
PVV
Before Agile

20. Planning!

23. Confluence documents the product
development process!

24. Planning and Scaling Takeaway!
Planning needs to be continuous
with occasional bursts to
synchronize around a specific plan

25. Planning &
Scaling
First Steps
Operating and
Adapting
Developing
PVV
Before Agile

29. Possible
Viable
Valuable

30. Responsible
Accountable
Consulted
Informed
Wikipedia says:
Responsible Those who do the work to achieve the task.
Accountable The one ultimately answerable for the correct and thorough completion of the
deliverable or task, and the one who delegates the work to those responsible. In other
words, an accountable must sign off work that responsible provides. There must be only
one accountable specified for each task or deliverable.
Consulted Those whose opinions are sought, typically subject matter experts; and with whom
there is two-way communication.
Informed Those who are kept up-to-date on progress, often only on completion of the task or
deliverable; and with whom there is just one-way communication.

31. Why not RACI?

39. PVV Takeaway!
Create conversations between people who can
evaluate whether something is possible, valuable,
and viable

40. Planning &
Scaling
First Steps
Operating and
Adapting
Developing
PVV
Before Agile

41. Confluence documents our products’
lifecycles!

42. Roadmap example!
AD-HOC CANVAS PLUGIN

43. Individuals and interactions over
comprehensive documentation
!

44. The journey
continues…

45. Key takeaways:
• Agile is not about the destination as much as the constant journey
• Stable teams provide a clear view of capacity
• Planning needs to be continuous with occasional bursts to
synchronize around a specific plan
• Create conversations between people who can evaluate if
something is possible, valuable, and viable
• One of the keys to Agile program management is appropriately
distributed decision making
#atlassian

46. Thank you!
PETER CALLIES • VP, PRODUCT DEVELOPMENT LIFECYCLE • SURESCRIPTS •
@PCALLIES