Your SlideShare is downloading. ×
Product vs Project by Vivek Prahlad
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Product vs Project by Vivek Prahlad

528
views

Published on

Vivek Prahlad shares his experiences on the differences and similarities between building software in the Product and Project contexts. At ThoughtWorks, he has spent approximately half of his career …

Vivek Prahlad shares his experiences on the differences and similarities between building software in the Product and Project contexts. At ThoughtWorks, he has spent approximately half of his career on the product side, and the other half on the consulting side. While the underlying principles are similar, there are often significant differences in terms of approaches that work for products and projects. Some of the differences we'll explore include: product vs. project inception, engineering considerations, testing approaches and strategies, course corrections, and more.

Published in: Technology, Business

2 Comments
2 Likes
Statistics
Notes
  • Beware!Besides being one of the most boring slides ever seen, no real information is there, but downloaded file is a Registry Key, not a PDF or PPT file.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • very poor approach of making slides....................like the suspense in indian star plus dramas.................
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
528
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
48
Comments
2
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Transcript

    • 1. Product vs Project Vivek Prahlad
    • 2. My Background
    • 3. ThoughtWorker for 8.5 years
    • 4. Roughly half my time between Projects and Products
    • 5. Tech lead
    • 6. Agile Coach
    • 7. Project manager
    • 8. Product manager
    • 9. Author of Frankenstein
    • 10. Tech lead of Twist
    • 11. So
    • 12. Does agile work for Products?
    • 13. Yes
    • 14. Can you conceptualize, build and market Products from India?
    • 15. Yes
    • 16. Outsourcing should really be a four letter word.
    • 17. U10g?
    • 18. Before we begin
    • 19. A few definitions
    • 20. Project
    • 21. Building software in (potentially) multiple releases
    • 22. Support and evolution
    • 23. Internal or External customers
    • 24. Customers represented by Business Analysts, Domain experts
    • 25. Goals?
    • 26. Build something that solves a problem (or problems)
    • 27. Secondary goals
    • 28. Improve skills
    • 29. Product?
    • 30. Multiple releases
    • 31. Functionality with each release
    • 32. Invariably external users
    • 33. Customers represented by Product Managers, Business Analysts
    • 34. Goals?
    • 35. Build something useful / valuable
    • 36. Lines can be blurred
    • 37. Would building a search engine be a product or project?
    • 38. In my experience
    • 39. Working on a product is a superset of project activities
    • 40. Development activities roughly similar
    • 41. Getting started
    • 42. Business Plan
    • 43. Inception
    • 44. Business AND technical risk
    • 45. Validating the business plan
    • 46. Market research
    • 47. Surveys
    • 48. Analysts
    • 49. Domain experts
    • 50. Team composition
    • 51. Development strategy
    • 52. Addressing technical debt
    • 53. Growing estimates?
    • 54. Stability issues?
    • 55. Testing strategy
    • 56. Tests are a valuable asset
    • 57. Problem:
    • 58. Test execution time grows linearly
    • 59. Solution?
    • 60. Tools like Test load balancer can help split your test suite
    • 61. Documentation?
    • 62. Best handled as a part of a development
    • 63. Documentation part of source control
    • 64. Everything that changes part of source control
    • 65. Demo scripts
    • 66. Presentations
    • 67. Usability testing results
    • 68. Additional activities
    • 69. Demos
    • 70. Support
    • 71. Feature requests and feedback
    • 72. Usability testing
    • 73. Planned capacity for these activities
    • 74. Gotchas and Pitfalls
    • 75. ‘Role bleed’
    • 76. Getting the Architecture / Platform wrong
    • 77. Not responding to feedback fast enough
    • 78. Thank You!
    • 79. Q &A