The Product Re-architecture:Lessons Learned From the Trenches to Avoid a Product Management Nightmare<br />Tom Evans<br />...
Why Re-Engineer/Re-architect? (1)<br />Business Case<br />Increase Revenue, Reduce Cost, Increase Profit, Improve Competit...
Reliability issues</li></ul>© Copyright 2009 – The Lûcrum Group, Inc.  All Rights Reserved.<br />
WhyRe-Engineer/Re-architect? (2)<br />Doesn’t support new market needs<br />Scalability<br />Integration into new systems/...
Challenges to Re-architect<br />What does it do?<br />Complex Systems – nobody understands everything<br />Current documen...
Steps to a Successful Re-architecture<br />Justify via business case<br />Complete functional analysis (Reverse Engineerin...
Functional Analysis/Reverse Engineering<br />Lack of commitment to this task is major cause for failure!<br />Source:  Nat...
Re-engineering Approaches<br />© Copyright 2009 – The Lûcrum Group, Inc.  All Rights Reserved.<br />
Plan to Maintain Current System<br />Bugs must be fixed<br />New features developed<br />Competitive response, major custo...
Release Plan<br />Some phased approach is required<br />Which features/components are done when?<br />Considerations<br />...
Typical Pitfalls<br />Failure to invest in early analysis<br />Poor engineering estimates<br />Continual slips due to new ...
Final Thoughts<br /><ul><li>Re-architecture is a must
It is always harder and takes longer than expected
Good analysis & planning is a must
Upcoming SlideShare
Loading in …5
×

The Product Re Architecture

1,928 views

Published on

Most efforts to re-architecture/re-engineer products become a nightmare when the development effort delays way beyond the original schedule, clients become disenchanted as the long awaited new features and capabilities don’t arrive and executives start to turn up the heat. This presentation address best practices to achieve success.

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,928
On SlideShare
0
From Embeds
0
Number of Embeds
15
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

The Product Re Architecture

  1. 1. The Product Re-architecture:Lessons Learned From the Trenches to Avoid a Product Management Nightmare<br />Tom Evans<br />Lûcrum Marketing<br />
  2. 2. Why Re-Engineer/Re-architect? (1)<br />Business Case<br />Increase Revenue, Reduce Cost, Increase Profit, Improve Competitiveness, etc.<br />Too expensive to maintain<br />Architecture/technologies are obsolete<br />Platforms, Integration technologies, Programming languages, User Interface<br />Code has lost clear maintainable structure due to accumulation of changes<br /><ul><li>Suppliers out of business
  3. 3. Reliability issues</li></ul>© Copyright 2009 – The Lûcrum Group, Inc. All Rights Reserved.<br />
  4. 4. WhyRe-Engineer/Re-architect? (2)<br />Doesn’t support new market needs<br />Scalability<br />Integration into new systems/new technologies<br />New business models (e.g., Browser, SaaS, etc.)<br />Lacks flexibility/configurability to meet new user needs<br />Security issues<br />Needs of new markets<br />Match competitive capabilities<br />© Copyright 2009 – The Lûcrum Group, Inc. All Rights Reserved.<br />
  5. 5. Challenges to Re-architect<br />What does it do?<br />Complex Systems – nobody understands everything<br />Current documentation – non-existent, out-of-date<br />Understanding functions<br />No longer used or obsolete<br />Thrown in for one customer<br />Customers never liked how it works<br />Business need is unknown<br />Maintain/Update old system while re-architecting<br />Resource constraints<br />Visible progress to customers<br />© Copyright 2009 – The Lûcrum Group, Inc. All Rights Reserved.<br />
  6. 6. Steps to a Successful Re-architecture<br />Justify via business case<br />Complete functional analysis (Reverse Engineering)<br />Determine new market needs that impact old functions<br />Document new system requirements (user stories)<br />Decide Re-engineering approach<br />Engineering estimates<br />Commit a team to re-architect<br />Define plan for maintaining current system<br />Determine release plan & timeline<br />© Copyright 2009 – The Lûcrum Group, Inc. All Rights Reserved.<br />
  7. 7. Functional Analysis/Reverse Engineering<br />Lack of commitment to this task is major cause for failure!<br />Source: National Institute of Standards and Technology<br />© Copyright 2009 – The Lûcrum Group, Inc. All Rights Reserved.<br />
  8. 8. Re-engineering Approaches<br />© Copyright 2009 – The Lûcrum Group, Inc. All Rights Reserved.<br />
  9. 9. Plan to Maintain Current System<br />Bugs must be fixed<br />New features developed<br />Competitive response, major customer needs, customer satisfaction, etc.<br />Define criteria<br />Which bugs to fix<br />When to add new features<br />When to lock down system<br />Dedicated team to do this<br />© Copyright 2009 – The Lûcrum Group, Inc. All Rights Reserved.<br />
  10. 10. Release Plan<br />Some phased approach is required<br />Which features/components are done when?<br />Considerations<br />Which customers are first?<br />Can you segment customers by usage?<br />Which features provide greatest coverage?<br />How fast can you get which new features to market?<br />What are competitive drivers?<br />What strategic initiatives have to be supported?<br />© Copyright 2009 – The Lûcrum Group, Inc. All Rights Reserved.<br />
  11. 11. Typical Pitfalls<br />Failure to invest in early analysis<br />Poor engineering estimates<br />Continual slips due to new discoveries<br />Lack of appreciation to degree of complexity<br />Years of prior development<br />Diverse usage/needs by customers<br />Effort not properly resourced<br />Lack of good project management<br />Shifting resources between maintenance & re-architecture<br />© Copyright 2009 – The Lûcrum Group, Inc. All Rights Reserved.<br />
  12. 12. Final Thoughts<br /><ul><li>Re-architecture is a must
  13. 13. It is always harder and takes longer than expected
  14. 14. Good analysis & planning is a must
  15. 15. Management team must understand and be committed</li></ul>© Copyright 2009 – The Lûcrum Group, Inc. All Rights Reserved.<br />
  16. 16. Acknowledgements<br />Baron Unbehagen, SVP Sales & Marketing, Postilion<br />Rob Reesor, VP Product Development, Planview<br />Software Re-engineering Report (NASA), by Dr. Linda H. Rosenberg - Unisys Federal Systems<br />© Copyright 2009 – The Lûcrum Group, Inc. All Rights Reserved.<br />
  17. 17. Thank You!<br />Tom Evans<br />Lûcrum Marketing<br />tevans@lucrum-marketing.com<br />+1.512.961.5267<br />© Copyright 2009 – The Lûcrum Group, Inc. All Rights Reserved.<br />
  18. 18. Thank You PCA Sponsors!<br />

×