Categories Corporate
Professional eBook

Agile Product Development

A Product Manager’s Guide - Product vs Project

34
Language:  English
This is a Project Manager’s perspective on what delivery approach can meet current market challenges, and how project management and product development knowledge can be combined to ensure success.
Professional Plus abonnement gratis de første 30 dage, derefter $6.99/per måned
Kniha neobsahuje reklamu
Description
Content

A project is defined by cost, time, and the desired output. That output may or may not become an outcome and increase the profit or the likelihood of achieving the goals. Whilst everyone agrees that greater Agility is essential to adapt the project outcome to changes in requirements, when looking at Agile ‘successes’ we need to accept that Agile comes at a cost, and the cost should justify the benefits, rather than Agile becoming the focus. This book is about combining project management and product development practices to ensure successful delivery.

About the Author

Dan is an experienced Project Manager with over 35 years commercial experience. He started his career as a specialist in Computer Aided Design and Manufacturing (CAD/CAM) following his involvement in research during university studies. After a successful career in research when he also published articles and books on various topics, mainly Computer Aided Design & Manufacturing and Computer Graphics he managed large development teams and then moved to Project Management and is now specialized in Business Transformations Projects.

  • About the author
  • Introduction
  1. Scaling up Projects
    1. Agile delivery, from Team to Organisation
    2. (Agile) Project Manager; what is it and why do we need it
    3. Is “Waterfall” non-Agile?
    4. Product vs Project
  2. Project challenges
    1. All projects are challenged
    2. What can impact a successful delivery
  3. Project Attributes
    1. Business Domain
    2. Size
    3. Complexity
    4. Level of Change introduced
  4. Choosing a delivery strategy
    1. Highest probability of success
    2. Limited impact on organisation
    3. Organization Alignment
  5. Focus on practices
    1. Why not frameworks?
    2. Stay Lean
    3. Become Agile
  6. Case Studies
    1. Taking advantage of Agile
    2. Scaling Agile, Back to Planning
  7. Conclusion
  • End Notes
About the Author
Dan

Dan Stelian Roman