| 1. |
How
to weed out losing projects. Prioritize by profit potential. |
| 2. |
How
to share fixed resources (including scarce technical
talent), product platforms, and key components across
projects and teams – for much higher return on engineering
hours invested. |
| 3. |
How
to manage multiple projects, accelerate product
introductions, and spread risk. |
| 4. |
How
to determine the most effective way to organize, deploy and
motivate people for your company’s unique needs. |
| 5. |
How
to use new IT tools to guide bottom-line portfolio and
pipeline decisions. |
| 6. |
How
to implement non-traditional, fast-results methods such as
critical chain, constraints-based portfolio management, and
agile project management |
| 7. |
About the 6 characteristics of an adaptive lifecycle –
mission-focused, component-based, iterative, time-boxed,
risk driven and change tolerant. |
| 8. |
How
to balance flexibility and project predictability |
| 9. |
Whether to centralize or decentralize decision-making |
| 10. |
How
to manage very short cycle times and overlapping shared
resources |
| 11. |
How
to use polarity mapping to balance conflicting requirements |
| 12. |
How
to make difficult tradeoffs and correctly limit the number
of development projects |
| 13. |
How
to load fewer projects into the pipeline and get more into
the market |
| 14. |
How
to use the Internet to facilitate project team communication |
| 15. |
How
to optimize the "closed loop" new product introduction
process |
| 16. |
How
to manage cross-divisional development |
| 17. |
How
to gain organizational buy-in to focus resources on the
highest value activities |
| 18. |
How
to best organize for speed and maximum throughput |
| 19. |
How
to reconcile project versus functional allegiances |
| 20. |
How
to make better allocation decisions |
| 21. |
What kind of information system will help you manage, and
what information should be tracked and shared |
| 22. |
To
anticipate when to shift resources |
| 23. |
To
prepare for new technologies and rapid market changes |
| 24. |
To
resolve conflicts among competing priorities, across
multiple projects |
