Product vs Project   Vivek Prahlad
My Background
ThoughtWorker for 8.5 years
Roughly half my time between   Projects and Products
Tech lead
Agile Coach
Project manager
Product manager
Author of Frankenstein
Tech lead of Twist
So
Does agile work for Products?
Yes
Can you conceptualize, build and market Products                 from India?
Yes
Outsourcing should really be a four letter word.
U10g?
Before we begin
A few definitions
Project
Building software in (potentially) multiple releases
Support and evolution
Internal or External customers
Customers represented by Business Analysts,            Domain experts
Goals?
Build something that solves a problem           (or problems)
Secondary goals
Improve skills
Product?
Multiple releases
Functionality with each release
Invariably external users
Customers represented by Product Managers,            Business Analysts
Goals?
Build something useful / valuable
Lines can be blurred
Would building a search engine be a product or                   project?
In my experience
Working on a product is a superset of project                 activities
Development activities roughly similar
Getting started
Business Plan
Inception
Business AND technical risk
Validating the business plan
Market research
Surveys
Analysts
Domain experts
Team composition
Development strategy
Addressing technical debt
Growing estimates?
Stability issues?
Testing strategy
Tests are a valuable asset
Problem:
Test execution time grows linearly
Solution?
Tools like Test load balancer can help split your test                         suite
Documentation?
Best handled as a part of a development
Documentation part of source control
Everything that changes part of source control
Demo scripts
Presentations
Usability testing results
Additional activities
Demos
Support
Feature requests and feedback
Usability testing
Planned capacity for these activities
Gotchas and Pitfalls
‘Role bleed’
Getting the Architecture / Platform wrong
Not responding to feedback fast enough
Thank You!
Q &A
Product vs Project by Vivek Prahlad
Upcoming SlideShare
Loading in...5
×

Product vs Project by Vivek Prahlad

590

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 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
590
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
52
Comments
2
Likes
2
Embeds 0
No embeds

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
  • Product vs Project by Vivek Prahlad

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

      Clipping is a handy way to collect important slides you want to go back to later.

    ×