Presentation made during the 2017 Gatineau-Ottawa Agile Tour by Nicolas Mercier and Frédéric Paquet.
Portfolio management is a key aspect of organizational performance. The ability to visualize upcoming projects, projects in progress, the process of value creation, the dependencies, the ability to share a common vision and to throttle the work in progress based on organizational capacity are all contributing elements to the effectiveness of an organization.
Unfortunately, the shared vision of a portfolio is too often buried in a tool shared with too few people and does not help the organization build a global and cohesive plan of action.
But when we think about it... Value chain, limiting work in progress, transparency, flow... have you ever thought about using Kanban for portfolio management? Seems like a great idea!
Create alignment around what delivers value to your end-users, use cadence to move forward, help shape a new organizational culture, support innovation, continuous improvement, and leadership and unite people around a shared mission, that is what Kanban at the strategic level can bring.
4. Intro
There must be a better way?
You didn’t even think about asking yourself this question.1
You asked yourself this question but can’t find answers.2
You found the answers.3
6. Once upon a time, the creation
• A sometime epic story
(in the non-agile way of the term)
• Team building (internal & external)
• Define scope, budget and schedule
… of a project
23. Visualize
• Where is what?
• Dependencies?
• Health?
• Issues?
• Whatever!
Let’s see this thing!
24. Visualize - Start with what you do now
Reveal the system!
• See it just the way it is.
• Don’t change it in any way.
• Empower people to own it.
This will generally hurt quite a bit.
30. Limit your WIP - Pull
Pull!
• Create a pull system.
• Value creation will
drive your choices.
Value
31. Limit your WIP – Little’s Law
L = W
L=
W
WIP
=Throughput
Cycle
Time
32. Manage flow
Go with the flow!
• Decentralize decisions.
• Empower and trust your people.
• Support your system:
• Eliminate bottlenecks.
• Puts the spotlight on constraints.
• Set up a cadence.
33. Manage flow - Cadence
• Rythmn of the system.
• Creates alignment and synchronisation.
• Breaks down BIG THINGS into small things.
Move to the beat!
34. Make policies explicit
Know the rules!
• Use Definitions of Done.
• Share and follow the rules.
• Ex: Card templates
38. We still have challenges to come
How does the highest level of
government measure the success of
IT Initiatives?
Evaluating IT initiatives as an
whole vs Individually
VS VS
39. Go from silos to system
WE’RE LUCKY THE HOLE ISN’T ON
OUR SIDE!
The non-performing system
The performing project
40. We still have challenges to come
The fear of auditor or medias is
strong
Transparency vs individual’s
motivations
VS
41. We still have challenges to come
• Your structure will need to change. Sometimes
drastically to support these things:
• Flatten your organization
• Break silos
• Move from project-centric to user-centric
• Make boundaries from roles and responsabilities a little
more blurry
• DevOps
• Understand people will disappear… and reappear in new
form (caterpillar to butterfly)
• Measure the impact of changes is hard on things that last
for months at a time
42. Metrics
• Focus more on outcomes than following the plan
• Use flow metrics and Value to steer your decisions