we need to change our portfolio level ideation process - Minto style
features take too long to develop
we rarely finish an item successfully #
Process question to relate to Protfolio items
how does a set of requirements make it to us : 🏁
what process was used to define this woork
what value and ROI metrics are designed to measure success
what is the ratio of started to finished work
can we make a graph of the last 2 years
what is the average time spent in anlysis phase of projects
snapshot of kanban in rally
click to edit
is connection to vision and strategy a regular occurance
The analysis phase of the portfolio item developmnet is not used effectively
to many interdependencies within the teams
in Progress meaning analysis is taking place rather implementation steps
work in the nav teams having detailed strategic work done on implementation
~20-30% of features started in a release are completed by the end of the release (over the past 6 releases)
(ie, see each Feature card with the 'x Weeks in this column')
Can also see the details of each feature manually, ie, the following example of when it was moved to a different state
Probably good to get a list of 5 features that did work nicely, and 5 features that didn't, and see how long each of those was in each state
click to edit
Argue 1
Suggested features - KickedOut features
Delta Suggested/Completed
Analysis time yields low ROI if the Development time significantly exceeds Estimated time
click to edit
metric work in IN PROG status for too long
drill down into total user stories in feature and team spread.
We need to focus on less items to be successful in completing them.
click to edit
click to edit
click to edit