Portfolio management Flashcards
3 fallacies
1) don’t provide executive visibility
2) not compatible with portfolio management
3) no clear finish date
Big challenge in portfolio management with agile
1) Avoid Releasing large quantities of code at once
2) Separating code into independent release streams by using modular, rather than monolithic
Modular design
Modular design also reduces risk in each release because less code is changing with each release. That makes it easier to diagnose and fix problems afterwards.
Overview
1) Share one vision, but embrace diversity
2) Expand agility as your grow
Portfolio success
1) Senior leadership must work in partnership with all teams to build a healthy agile culture
2) portfolio will only be as successful as its weakest team
3) Agile culture is a force multiplier: it naturally scales upward and outward when its core principles are followed and shared
PPM long term vs agile short term
1) both to deliver values
Don’t stifle
1) Executives for stakeholder checkpoint in traditional
2) Don’t need executive checkpoints in agile
Agile story points in PPM
1) Measure of business value
Agile team part time worker
1) Product development (dedicated team)
2) IT - Need part time workers (but possible, collaboration with collocation)
Agile delivering stories, not milestones
1) Progress - how many stories finished
Planned finish date
1) when do we have to finish that
2) Agile do not have baseline but planning is possible
% complete
1) story points accepted / total story points
2) It changes re-estimation happens, value may change
Scope changes
1) Scope changes all the time
2) add /remove stories
Actual cost / budget
1) traditional - number of hours
2) agile - dedicated team - no need to log
3) log towards to project not to individual items
Project health
1) actual vs planned
