Development Strategy for Engineering Going Forward at Pitney Bowes - PowerPoint PPT Presentation

slide1 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Development Strategy for Engineering Going Forward at Pitney Bowes PowerPoint Presentation
Download Presentation
Development Strategy for Engineering Going Forward at Pitney Bowes

play fullscreen
1 / 96
Development Strategy for Engineering Going Forward at Pitney Bowes
137 Views
Download Presentation
lei
Download Presentation

Development Strategy for Engineering Going Forward at Pitney Bowes

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Development Strategy for Engineering Going Forward at Pitney Bowes Sue McKinney Vice President, Engineering Pitney Bowes Incorporation

  2. challenges strategic directions tools summary

  3. successful business?

  4. sustain a competitive advantage • Sustainable • Competitive advantage

  5. consistentlydeliver business value

  6. businesschallenges

  7. delivertheright product • Build Trust?

  8. in the optimalmarket windows

  9. At the lowest cost lowestcost

  10. and …

  11. increase productivity

  12. meet customer’schangingneeds Protect Team Boundaries

  13. developgreatsolutions

  14. innovate! • Leadership Influence

  15. software challenges

  16. business dynamics innovate todifferentiate responsiveness tighter linkage to customers timeto value

  17. operationaldynamics predictabilityofschedules quality betteruse of resources improveproductdevelopmentcycles

  18. Never or Rarely Used: 64% Always or Often Used: 20% Rarely 19% Sometimes 16% Often 13% Never 45% Always 7% Standish Group Study, reported by CEO Jim Johnson, XP2002

  19. Project Statistics Standish Group Study, reported by CEO Jim Johnson, CIO.com, ‘How to Spot a Failing Project’

  20. Improvements due to better… • Tools • Project Managers • Adaptive Methods • Breaking projects into small chunks • Delivering pieces faster for user feedback

  21. too much churn

  22. Lead change Less waste Respond to market changes

  23. split teams & multiple locations multiple time zones interdependent products acquisitions complexity

  24. how?

  25. Trust do more smart stuff

  26. …andless stupid stuff.

  27. process to deal with complexity

  28. tools • coupled with • bestpractices

  29. Self-organizing, self-managing • Do we need leaders? • What kind of Leadership? what aboutagile? whatisthat?

  30. Cost Avoidance (i.e. avoid new expenses) Waste Avoidance (i.e. eliminate current expenses) Productivity Gain (i.e. do things faster) E2Framework elements Provide Capacity Gain 3 atomic elements: Create Market Opportunities Analysis through Value Stream Mapping technique Improve Customer Satisfaction Increase Revenues / Profits Prevent / Reduce Business Costs

  31. Brand W Products Brand T Products Brand W HC/product Brand T HC/product improvingProductdeliveries Products & HC/Product 2004 2005 2006 2007 2008

  32. SWG Average Hc / Product GA 2003 2004 2005 2006 2007 2008 doingMore withLess

  33. improvingBottom line Growth Effectiveness $$ per HC $K / HC SWG Average 2003 2004 2005 2006 2007 2008

  34. takerisks

  35. Get more done by doing less support

  36. theapproach

  37. educate enable empower

  38. Sustainable Competitive advantage focus on business results

  39. layingtheFoundationforMeasurements teamProductivity Quality Stakeholder Satisfaction cost of Development

  40. use Agile and…

  41. vision and strategy

  42. Project Management communication • Focus, Communication, and Expectation Management

  43. empowerment

  44. give and re-enforce ownership

  45. teams figure out how

  46. make better decisions with less churn

  47. Business Value Model Purpose Considerations Costs and Benefits

  48. it’s a conversation

  49. resolve differences

  50. group chunks high – medium - low