With the right tools and mindset, scaling Agile throughout your IT organization can be a painless process. As the market evolves from post-it notes to whiteboards and beyond, the next frontier is finding the right tools that support Agile not only across teams, but also through various levels of hierarchy. The right tools will support not only team members in flowing work across their Kanban boards, but also will support the executive level as they look for at-a-glance updates on the progress and blockers of key initiatives. From Dev to Ops, all teams within an IT organization should be working towards the same goal -- fast delivery of value to the customer -- and the benefits of Agile can help them get there. But this is not possible with a disconnected toolchain. Agile must impact the whole end-to-end workflow. This webinar discusses how your organization can enable scaled Agile success by: - Aligning team priorities around the common goals of an Agile transformation - Increasing visibility of project status and compliance with cross tool traceability and reporting - Creating and managing an integrated value stream that can scale to hundreds of projects in minutes

1. The Evolution of Agile Portfolio
Management for Scaled Agile Success

2. GoToWebinar Housekeeping
Check your email tomorrow for recording and slides.
If you are having technical problems,
please contact GoToWebinar:
Toll-Free: (855) 202-7959
Long Distance: (805) 617.7049
*United States Numbers
Submit your questions
throughout the
presentation here

3. Trevor Bruner
Product Manager, Tasktop
Meet the presenters
Jasper Sonnevelt
Executive Consultant, LeanKit

4. Poll

5. Agile Portfolio Management

6. Problem: autonomy, entrepreneurship, alignment
How do you align Product Owners & teams to
organizational goals without telling them what
to do?

7. A solution should enable
• Information sharing
• Transparency
• Better discussions and decision making

8. The Portfolio Wall
• Provides visibility of work for the
next 3-12 months
• Creates transparency and focus on
department goals
• Aligns teams and is used to
manage dependencies

9. A breakdown from long term to frequent
Department purpose (multiple years)Long Term
Frequent
Goals (approx. 1 year)
Team purpose (approx. 1 year)
Team goals - KPIs (quarter to 1 year)
Epic (multiple sprints)
Feature (< sprint)
User story (days)
Tasks (hours) Why?
Why?
Why?
Why?

10. A breakdown from long term to frequent
Department purpose (multiple years)
Predictability
filters up
Goals (approx. 1 year)
Team purpose (approx. 1 year)
Team goals - KPIs (quarter to 1 year)
Epic (multiple sprints)
Feature (< sprint)
User story (days)
Tasks (hours)
Control
funnels down

11. Completed portfolio
wall shows even
distribution of tasks
over time

12. Teams or
Organizational
Goals
Time

13. Topics at the Portfolio Marketplace
Should we
change
which teams
work on
work items?
Outcome Output Sourcing
Status of KPI’s
/ Goals
Do we need
to adjust?
These are the
goals we are
trying to achieve
What epics do we
have prioritized to
reach these goals
Do we
expect the
right things
to happen? Are we
delivering
fast
enough?
Should we
redistribute
our capacity?

14. Stickies are nice but....
What about when you’re not co-located?
How can you quickly report on tasks and goals?
Do you have the most accurate view of WIP? etc..

15. Portfolio Management in LeanKit

16. Gathering data is automated

17. Digital boards show real-time status of portfolio

18. Portfolio level
Program level
Team level

19. Poll

20. Let’s re-address the ‘why’ of LeanKit
Information Sharing
Transparency
Better discussions & decision making

21. What happens when your scale grows?
Not just scale in size, but scale in scope?
Different teams in multiple departments with different needs?

22. Why not build a single tool to rule them all?
https://xkcd.com/927/
tools tools

23. There’s no “One Tool to Rule Them All”
Different departments have different needs...and different solutions

24. So what does this look like?
Use the right tool for the right job...and use something else to tie it all together

25. Here’s an example...
Imagine a company using:
● CA PPM for high level Portfolio Management
● ServiceNow for ITSM tickets
● LeanKit for prioritization & feature definition & execution
● HPE ALM for test management
How can they achieve:
● Information sharing
● Transparency
● Better discussions & decisions

26. Communication
It all hinges on communication…
That’s why we had to evolve from sticky notes to LeanKit
But what needs to be communicated?

27. Same same but different
● Status
● Description
● Summary
● Cross-tool traceability
– Location (i.e. URL in other tool)
– Identifier in other tool
● Filtering
● Routing
● Comments / Attachments

28. How does this work in real life?

29. How does this work in real life?
Each integration has it’s own set of rules...

30. How does this work in real life?
Let’s drill into this integration...

32. Pssst- don’t tell anyone...
Cross-team communication (and tool integration)
depends more on team dynamics than tooling
Start slow, get team buy-in on process.
You can win many battles by surrounding hold-outs

33. Can we see some other scenarios?

34. Can we see some other scenarios?

35. Can we see some other scenarios?

36. Can we see some other scenarios?

37. Scaling agile success
The key to scaling agile is communication…
● Between people
● Between teams
● Between departments

38. Questions?

40. www.leankit.com
©2017 LeanKit Inc.
www.leankit.com